Invalid Status for Visual Studio .NET 2003 project

[Uwe Laemmle]

I saw a problem on having a solution including a couple a projects connected to SourceGear Vault (3.0.6). After working disconnected and reconnecting to SourceGear Vault, one project was marked as status invalid, there was no chance to correct the status of this project. Other projects in the same solution have been in status valid.

I found a solution to the problem, but if this is the only way, oh oh oh ....

step1: backup the local working folders
step2: delete all local working folders
step3: open the Visual Studio .NET 2003
step4: "open from source control", get the latest version of the solution
step5: close visual studio
step6: copy from the backup folders all data excluding _sgbak and the *.vspscc, mssccprj.scc and vssver.scc files
step7: open visual studio, the status of all projects are valid and the bindings are ok

I worked for a longer time with a connection to SourceGear Vault, but without updating changes to the repository!
My local working folders are organized on a local virtual drive (by SUBST command).

Can you give me an idea about the real problem?!

Thanks and regards

[dan]

There's no way to know what the issue was, but often when there are failures, they get output to the Output window in Visual Studio. Do you remember seeing anything there? Also, we now have a log file output that you can turn on when you have problems with the IDE - Check the knowledge base for how to set that up if this happens again.

[Uwe Laemmle]

Hm, the Visual Studio output window didn't show any failure, the actions and transactions have been shown there, everything seemed to be ok. I have attached the log file by SourceGear Vault (I added the registry entry to create log files).

[dan]

Are you still have problems with the bindings being invalid?

[Uwe Laemmle]

after the steps descriped in my initial message, no!