Nightmare in VS2003

[R-D-C]

Hi,

VS2003 has gone totally mad on me and I haven't a clue why!

I have an application that displays different user controls according to
what menu option you click. Within these usercontrols are other
usercontrols to control individual input boxes and structured items such as
three textboxes in a specific format.

Everything was working ok until this morning. I rebuilt the project this
morning with only minor changes to the code. Now every form containing a
user control has had it removed. I get a whole host of errors telling me
that the type for each control cannot be found and to check the assembly
containing containing the user control is referenced (everything is in one
assembly), and that the variables that used to be controls on forms / other
controls are either undeclared or never assigned.

I returned to my back-up but adding a line of code here and there causes the
same thing to happen.

Currently I have lost several week's work, can anybody PLEEEEAAAAASSEE
help???

 

[news.microsoft.com]

Try using Visual SourceSafe then you wouldnt lose a weeks work

 

[Sunil TG]

Yes thats right. when doing development, you should really
use some kind of source control mechanism

 

[Dmitriy Lapshin [C# / .NET MVP]]

Hi,

It seems to be an IDE bug which I have seen reported by many posters and
experienced myself in VS .NET 2002. The only solution I know is:

a) Avoid opening user controls and forms in the designer.
b) NEVER open a user control or a form in the designer when another control
this one depends on has been modified (or if the assembly containing that
control couldn't be built successfully).
c) Avoid using the Localizable property. This one seems to be able to kill a
form at once.

 

[R-D-C]

Thanks for the info.

I am amazed that in a second release product that this still exists. Bad
form by Mickysoft.

Hi,

It seems to be an IDE bug which I have seen reported by many posters and
experienced myself in VS .NET 2002. The only solution I know is:

a) Avoid opening user controls and forms in the designer.
b) NEVER open a user control or a form in the designer when another control
this one depends on has been modified (or if the assembly containing that
control couldn't be built successfully).
c) Avoid using the Localizable property. This one seems to be able to kill a
form at once.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Hi,

VS2003 has gone totally mad on me and I haven't a clue why!

I have an application that displays different user controls according to
what menu option you click. Within these usercontrols are other
usercontrols to control individual input boxes and structured items such as
three textboxes in a specific format.

Everything was working ok until this morning. I rebuilt the project this
morning with only minor changes to the code. Now every form containing a
user control has had it removed. I get a whole host of errors telling me
that the type for each control cannot be found and to check the assembly
containing containing the user control is referenced (everything is in one
assembly), and that the variables that used to be controls on forms / other
controls are either undeclared or never assigned.

I returned to my back-up but adding a line of code here and there causes the
same thing to happen.

Currently I have lost several week's work, can anybody PLEEEEAAAAASSEE
help???

 

[Dmitriy Lapshin [C# / .NET MVP]]

I think if this problem'd had a stable repro, it would have been fixed
already. I have seen several threads where Microsoft people asked the
posters to provide them with a repro, but it seems it is quite hard to
invoke this faulty behavior on purpose - at least on a small demo project.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Thanks for the info.

I am amazed that in a second release product that this still exists. Bad
form by Mickysoft.

Hi,

It seems to be an IDE bug which I have seen reported by many posters and
experienced myself in VS .NET 2002. The only solution I know is:

a) Avoid opening user controls and forms in the designer.
b) NEVER open a user control or a form in the designer when another control
this one depends on has been modified (or if the assembly containing that
control couldn't be built successfully).
c) Avoid using the Localizable property. This one seems to be able to

kill

a
form at once.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Hi,

VS2003 has gone totally mad on me and I haven't a clue why!

I have an application that displays different user controls according to
what menu option you click. Within these usercontrols are other
usercontrols to control individual input boxes and structured items

such
as

three textboxes in a specific format.

Everything was working ok until this morning. I rebuilt the project this
morning with only minor changes to the code. Now every form

containing

a causes
the

 

[Miha Markic]

Hi,

I saw this happening when there were errors in form's/usercontrol's
constructor code (it is executed at design time!).

Miha

I think if this problem'd had a stable repro, it would have been fixed
already. I have seen several threads where Microsoft people asked the
posters to provide them with a repro, but it seems it is quite hard to
invoke this faulty behavior on purpose - at least on a small demo project.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Thanks for the info.

I am amazed that in a second release product that this still exists. Bad
form by Mickysoft.

in message news:%234FfKW%[email protected]...

Hi,

It seems to be an IDE bug which I have seen reported by many posters and
experienced myself in VS .NET 2002. The only solution I know is:

a) Avoid opening user controls and forms in the designer.
b) NEVER open a user control or a form in the designer when another control
this one depends on has been modified (or if the assembly containing that
control couldn't be built successfully).
c) Avoid using the Localizable property. This one seems to be able to

kill

a
form at once.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Hi,

VS2003 has gone totally mad on me and I haven't a clue why!

I have an application that displays different user controls

according

to containing telling
me in
one

 

[R-D-C]

I kept a copy of the damaged files if anybody from Microsoft is interested.

I think if this problem'd had a stable repro, it would have been fixed
already. I have seen several threads where Microsoft people asked the
posters to provide them with a repro, but it seems it is quite hard to
invoke this faulty behavior on purpose - at least on a small demo project.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Thanks for the info.

I am amazed that in a second release product that this still exists. Bad
form by Mickysoft.

in message news:%234FfKW%[email protected]...

Hi,

It seems to be an IDE bug which I have seen reported by many posters and
experienced myself in VS .NET 2002. The only solution I know is:

a) Avoid opening user controls and forms in the designer.
b) NEVER open a user control or a form in the designer when another control
this one depends on has been modified (or if the assembly containing that
control couldn't be built successfully).
c) Avoid using the Localizable property. This one seems to be able to

kill

a
form at once.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Hi,

VS2003 has gone totally mad on me and I haven't a clue why!

I have an application that displays different user controls

according

to containing telling
me in
one

 

[R-D-C]

Guess not then

I kept a copy of the damaged files if anybody from Microsoft is interested.

I think if this problem'd had a stable repro, it would have been fixed
already. I have seen several threads where Microsoft people asked the
posters to provide them with a repro, but it seems it is quite hard to
invoke this faulty behavior on purpose - at least on a small demo project.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Thanks for the info.

I am amazed that in a second release product that this still exists. Bad
form by Mickysoft.

in message Hi,

It seems to be an IDE bug which I have seen reported by many posters and
experienced myself in VS .NET 2002. The only solution I know is:

a) Avoid opening user controls and forms in the designer.
b) NEVER open a user control or a form in the designer when another
control
this one depends on has been modified (or if the assembly containing that
control couldn't be built successfully).
c) Avoid using the Localizable property. This one seems to be able

to
kill

a
form at once.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Hi,

VS2003 has gone totally mad on me and I haven't a clue why!

I have an application that displays different user controls

according

to
what menu option you click. Within these usercontrols are other
usercontrols to control individual input boxes and structured

items
such

as
three textboxes in a specific format.

Everything was working ok until this morning. I rebuilt the project
this
morning with only minor changes to the code. Now every form containing
a
user control has had it removed. I get a whole host of errors telling
me
that the type for each control cannot be found and to check the assembly
containing containing the user control is referenced (everything

is

in

forms

/

 

[Jason Dorie]

Try using Visual SourceSafe then you wouldnt lose a weeks work

You've obviously never actually USED SourceSafe for a large project. Losing
a weeks work is relatively common with that pile o' poo.

Jason

 

[Miha Markic]

Hi Jason,

You've obviously never actually USED SourceSafe for a large project. Losing
a weeks work is relatively common with that pile o' poo.

I use it on a solution with 15 projects. I did never ever loose a single bit
;-)

 

[Miha Markic]

Its called backups.

No, it is called VSS.

 

[Guest]

Its called backups.

Hi Jason,



I use it on a solution with 15 projects. I did never ever loose a single bit
;-)

 

[R-D-C]

I have to agree.

I have seen VSS go tits up on several occasions. I now insist that projects
are backed up externally to VSS as well as within it. I also hate the
"sneaking death" that sourcesafe sometimes does when individual files start
to die before the database goes completely. Fantastic news when the
database finally packs up and your backups are of a partially damaged
project - not.

 

[Jason Dorie]

I've used it on many small code-only projects and had no major issues with
it, but once you start getting serious (IE hundreds of source files, binary
data, more than a couple meg of source, etc) you realize that VSS just
doesn't cut it anymore. It uses the file system to handle locking, instead
of a server, doesn't allow atomic changes, the database is slightly unstable
at best, and it gets worse as you add more users and data. Backups are an
obvious necessity, but it's like addressing OS stability problems by making
it reboot faster. Try Perforce and you'll never go back. I doubt
they'd admit it, it's what M$ uses in-house.

Jason

 

[Miha Markic]

Hi,

I've used it on many small code-only projects and had no major issues with
it, but once you start getting serious (IE hundreds of source files, binary
data, more than a couple meg of source, etc) you realize that VSS just
doesn't cut it anymore. It uses the file system to handle locking, instead
of a server, doesn't allow atomic changes, the database is slightly unstable
at best, and it gets worse as you add more users and data. Backups are an
obvious necessity, but it's like addressing OS stability problems by making
it reboot faster. Try Perforce and you'll never go back. I doubt
they'd admit it, it's what M$ uses in-house.

I've never said that I like that much VSS
However, it works for me currently.
Let's see what MS will cook for Whidbey.