Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

PROBLEM / BUG: Visual C++ .NET "Properties View (F4)"

1 view
Skip to first unread message

syrus

unread,
May 17, 2003, 2:44:54 PM5/17/03
to
Visual C++ .NET Standard's "Properties View (F4) " has a
problem on my machine. It worked correctly for a few
weeks. The problem is that the view does not render any
information. I get a blank gray region as if the selected
object does not have any properties. I looked absolutely
everywhere to find a way to prevent it from failing.
After a lot of debugging I found out that I could get it
to work temporarily if:
1- I delete C:\Documents and Settings\syrusm\Application
Data\Microsoft\VisualStudio\7.0 folder
2- I launch VS through the Icon on the start menu. (NOTE:
will not work if I launch VS by clicking on an existing
project or if I right click on say an HTML file and "Edit
with visual studio")

After exiting visual studio and reentering VS, the
properties view will not work unless I repeat the
procedure above.

Some additional information:
This problem is not specific to a single project.
This problem is not specific to a single user. If I log
on as a different user, I still have the same problem.
This Problem is not specific to certain type of
object/component

To test the properties window, I made an empty HTML file
and dragged and dropped an Edit field. If I select the
edit field in the "Design View" and press F4 I get a
blank gray window for the properties view. The same is
the case if I open an HTML file and press F4. When the
properties view stops working, I cannot view the
properties of any thing that uses the Properties View
(F4) in .net.

I have also tried to reinstall visual studio. I have
tested every possibly related key/value in the windows
registry under
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\VISUAL STUDIO\7.0


Has any one come across this problem, or have a
suggestion?

syrus

unread,
May 19, 2003, 12:34:52 PM5/19/03
to

Just wanted to post an update. The problem was a side-
effect of the W32.Pinfi virus. I hope no one else has to
go through this; It was the most clever virus I have ever
seen.
Regards, Syrus

>.
>

0 new messages