View Designer ??

  • Thread starter Thread starter Wapiti
  • Start date Start date
W

Wapiti

This new ide is killing me. Maybe its just the CF side of it, as I've not
used any non-cf components of vs.net yet....

First, is it just me, or is the Designer view a killer of system resources?
Sometimes I wait a full minute before the designer of my form refreshes
itself (that is, when coming back from Code View).

But to my main question ... I just installed VS.net onto a new machine
hoping to get better performance. But now, when I load the same project,
under the solution explorer, it shows all my project forms - but only one
has the icon noting that its actually a form!

Only on that one form can I actually go into the Designer View. The others,
I am only allowed to go into Code View.

Huh??????

Any suggestions would be appreciated

-Mike
 
Well, I figured it out and glad to know its not my doing... the ide has
some problems doesn't it? Kind of reminds me of the old VB days before the
source was ascii based.

I excluded one of the forms from the project, and then reincluded it - all
forms showed the right icons and allowed for designer view.

I am seeing so many positives in .net development, but yet its still so, so,
so, microsoft. Delivery before its ready for primetime - just get
marketshare and the developers will be stuck into the rut and have to
follow. Ok, rant over. Back to development.

-m
 
I have seen this when developing for VB.NET (but not for C#). Here is what I
found to work to get the ability to run the forms designer:

1) Open the Solution Explorer window if it is not open (View->Solution
Explorer)
2) Expand the items in the "References" folder
3) Remove the references to System.Data and System.XML (right-click, select
"Remove")
4) Add back references to System.Data and System.XML (right-click on
"References", select "Add Reference..." In the ".NET" tab, double-click on
System.Data and System.XML. Click OK.

This is definitely a weird Designer bug.
--
My Best,
Paul Yao

Microsoft eMVP
co-author, .NET Compact Framework Programming with C#
co-author, .NET Compact Framework Programming with VB.NET
http://www.paulyao.com
 
Wapiti said:
This new ide is killing me. Maybe its just the CF side of it, as I've not
used any non-cf components of vs.net yet....

First, is it just me, or is the Designer view a killer of system resources?
Sometimes I wait a full minute before the designer of my form refreshes
itself (that is, when coming back from Code View).

But to my main question ... I just installed VS.net onto a new machine
hoping to get better performance. But now, when I load the same project,
under the solution explorer, it shows all my project forms - but only one
has the icon noting that its actually a form!

Only on that one form can I actually go into the Designer View. The others,
I am only allowed to go into Code View.

Huh??????

Any suggestions would be appreciated

-Mike
Click to expand...

I get this ALL the time, usually when changing from one solution to another
without first closing the IDE. It happens frequently when I am navigating
through a large multi-solution application of ours, as I tweak things or
look for something.

One of the first clues is when the IDE asks you to save the solution, and
you know you didn't change anything. Well, it did! Usually one or more
forms have lost their form icons in solution explorer. The .csproj or
..vbproj files will have the wrong SubType entries. In a pinch, you can
manually change this back to Form if you have to.

Out of desperation, I started adding DesignerCategory("Form") to all my
forms, and this helped a bit. It usually will find its way back to a
correct state with these hints. My best avoidance technique to date is to
always close the IDE before opening another solution. It definitely
minimizes the aggravation, but is expensive if the solution has many
projects - particularly if they access VSS over a VPN connection!

The upshot, from everything that I've read on news groups, is that MS still
can't reproduce it. They must not be using the IDE when they develop their
own .NET applications. :-)

Best Regards,

Andy
 
Hey, I see this a LOT, Its easy to fix!

Just right-click the assembly where it happens and click "refresh" ....or
was it rebuild? not sure, anyway, that takes care of it (until it happens
again) :)

It doesn't bother me much because it's so easy to mend. You guys seem to be
going to a lot of trouble to fix it.
 
Robert said:
Hey, I see this a LOT, Its easy to fix!

Just right-click the assembly where it happens and click "refresh" ....or
was it rebuild? not sure, anyway, that takes care of it (until it happens
again) :)

It doesn't bother me much because it's so easy to mend. You guys seem to be
going to a lot of trouble to fix it.
Click to expand...

I sure am. Just a Rebuild from solution explorer, eh? I'll try it.
Thanks!

Best Regards,

Andy
 
Back
Top