Anyone else get this:

I open a solution in VS.Net (2003). If I right click on a project and select properties, I get a pop-up box that says "There are no property pages for the selection." The caption says "MarshalByRefObject Property Pages". My only option is to click OK or Cancel.

It only does this the first time. The next time I try it, it works the way it is supposed to. This isn't isolated to one computer. [u]Every</u> computer that I install Visual Studio on does this. It is very annoying...

J

Anyone...Hello... [Tap...Tap...] is this thing on????

No one is having this same problem that I seem to have on every installation of Visual Studio???

I have not seen this problem. How quickly after you load the project(s) do you hit the properties? I can't imagine why this would happen.

Looks like someone's had this problem in Korea:
http://www.dotnetguru.co.kr/Body/Boa...pe03_List.aspx

-Peter

Thanks for the reply Peter. I think I figured out what is causing it, I just don't know why. First, I will have to (sheepishly) scratch what is in my first post about it happening to every computer...

I installed VS on my laptop and tried to look at the properties of project - I didn't get the error. So I start thinking to myself, what's different between my other workstations (at home and work) and the laptop. One thing I could see was that the workstations were Dual AMDs and the laptop was a Pentium 4. The only other thing was the video.

I didn't think it could be the processor because I assume that I am not the only one running AMD processors and I would have seen more posts about this.

So I looked at the video. On both my workstations (at home and work) I have dual monitors setup. In my VS layout, I undocked about five of the dockable windows (one is the properties window) and moved them to the 2nd monitor so I would have more room for viewing code.

This seems to be what is causing this behavior. As soon as I redocked the windows I didn't have the problem anymore.

Obviously if nobody knows why this does this or a way to avoid it I will just live with it because the inconvenience of it is outweighed by the ability to view the code full screen and still have all the tools visible.

Thanks for any input.

Also, to answer your question: It doesn't matter when I do it after the solution is loaded - it could be right after or 20 minutes later, it just does it the first time and then it works.

J

Interesting problem.

I don't find that I need to access the toolboxes enough to need them visible all the time so I just unpin them and mouse over their windowshade tabs when I need them. You can change some settings in VS so that they pop out faster than the default settings.

-Peter

Thanks. Maybe I'll try that.

I get the same error. It's highly annoying. It happens to me in the same fashion, when I am in dual montor mode. Did you ever get an answer to this?

Thanks
JP