Controls mysteriously going missing in designer

[Simon Verona]

I don't know if this is the correct group to ask the question, but I'll ask
it here anyways!

I have a solution, written in vb.net 2003 (using Visual Studio 2003
Professional) which has multiple projects.

What I find is that from time to time (once every couple of days) that when
I go to run the solution (which compiles all the projects) that the compile
fails because a control is missing. The control in question is always a
usercontrol that is contained in one project and added onto a form in
another project.

Sometimes I find that simply rebuilding the project solves the problem...
Other times I have to manually go back and add the control to the form in
question - the form is always missing on the designer, but if I try to add
it and rename back to it's original name then it says that the name is
invalid (because it already exists - there are references to it in the
initalisation code).

The only other information that I can add is that it's nearly always the
same controls that go missing - there are about 4 in total that keep
disappearing. What is particularly strange is that the forms in question
are never ones that have been updated or are even opened since the last
compile and run.

Is this a known issue with vs2003? Is there a fix/workaround?

Thanks in advance
Simon

 

[Guest]

In your user control's assembly.vb, you might try changing the line for the
assembly autonumbering by replacing the * with a number so the build always
use the same assembly number. This seemed to work for me so far but it just
could be a coidence that it's now workin ok.

 

[Simon Verona]

Interesting! I'll give it a go

Thanks
Simon

In your user control's assembly.vb, you might try changing the line for
the
assembly autonumbering by replacing the * with a number so the build
always
use the same assembly number. This seemed to work for me so far but it
just
could be a coidence that it's now workin ok.