Disappearing User Controls

[Oddball]

How on earth do I convince VS.net to keep stop removing my user controls from the
design view!

I've created my very own listbox and now I go to put in into the form - which works - I
wonder off to do some other stuff, come back and VS just deletes it. It leaves the
definition and the addition to the Controls collection of the containing control. But it
doesn't leave the bloody control.

*frets*


------------------------------------

Another unchecked rambeling brought to you by:

Oddball
joshua@bf#N0SP4M#wd.co.uk

 

[Phil Wright]

Sounds like the designer is having trouble serializing the contents of the
control or has a problem knowning that is still a valid component. Make sure
that you copying the assembly that has the new control into the project that
is being designed.

Phil Wright
Follow my startup microISV at...
http://componentfactory.blogspot.com

 

[cody]

Look into the tasklist when opening the desiogn view. Is there an error that
an exception occured when creating a control or a message that vs cannot
find a assembly?
If the first is the case try to debug vs with vs (atach the debugger of
another instance of vs to the running instance), if the latter is the case
make sure you included all project references to all needed dll's and
everything is freshly rebuilt.

 

[Frans Bouma [C# MVP]]

How on earth do I convince VS.net to keep stop removing my user
controls from the design view!

I've created my very own listbox and now I go to put in into the form
- which works - I wonder off to do some other stuff, come back and VS
just deletes it. It leaves the definition and the addition to the
Controls collection of the containing control. But it doesn't leave
the bloody control.

*frets*

Call MS Support (PSS) and ask for fix of KB: 842706 - fixes nested
controls from different assemblies as long as both assemblies aren't in
the same solution when compiled.

FB

--