SourceGear Support

It looks like this may be a known issue with Visual Basic using source code control. Please view the following KB article and let me know if this doesn't resolve your problem.

http://support.microsoft.com/default.as ... -us;183728

Tonya Nunn
SourceGear Support

Thanks for the details.

I was able to reproduce this problem but I'm afraid this is a Visual Studio .Net issue. The same problem exists using other Source Code Control applications such as VSS.

Tonya Nunn
SourceGear Support

Where are you seeing this information from? The Vault server log file or the Vault IDE client log?

This may be related to the binding issues that you have been experiencing.

Tonya Nunn
SourceGear Support

Is it possible that the MSSCCPRJ file is located in a different subdirectory? Whenever I add or open a solution from source code control the MSSCCPRJ file is always created. So I have been unable to reproduce this issue. We have also previously not had any other reports of this file not being create...

How are you attempting to open the project from within VS.Net? The MSSCCPRJ file should always be created when adding or opening a project from scc. What you are attempt to do should work as long as the MSSCCPRJ file is somehow saved. But right now it sounds like because the MSSCCPRJ file isn't bein...

If your solution is no longer complex and set up as a normal solution would be, then I no longer need to view it. Have you had a chance to test one of my earlier suggestions? "My suggestion is to either make your automated build not delete the MSSCCPRJ.SCC file or make a backup copy of the file...

You will probably need to upgrade your VSS version to 6.0d. This pinning issue is probably related to the API for VSS 6.0a that you are currently using. Upgrading should take care of the problem, please let me know if it doesn't.

Thanks.

Tonya Nunn
SourceGear Support

My first suggestion is to upgrade your SOS Server and all of your Clients to 4.1. Using mismatched versions as you are, could result in unexpected behavior.

Let me know if upgrading doesn't resolve the problem.

Tonya Nunn
SourceGear Support

Could you e-mail me a screen shot of how one of your solutions is set up? I would like to see a solution from Solution Explorer in VS.Net and then from the SOS Client. Once I get an idea of how your solutions and projects are configured, I may be able to give you some more suggestions on how to make...

If you are recreating the MSSCCPRJ.SCC file correctly (the exact same way it appeared before it was deleted) then there should be no problems. I followed the exact steps that you are taking but instead of recreating the MSSCCPRJ.SCC file in C#, I created it using Notepad. Before I deleted all of the...

Do you have more than 50 network bound protocols? Please read the following Microsoft KB article regarding the error message that you are receiving in your SOS log file and let me know if this resolves the problem. http://support.microsoft.com/default.aspx?scid=kb;en-us;826757 Overall, it appears to...

I was able to successfully complete the process that you reported by recreating the MSSCCPRJ.SCC file in Notepad. There may be some sort of timing issue involved from when the file is created in C# and when VS.Net actually needs the file. My suggestion is to either make your automated build not dele...

How are you recreating the MSSCCPRJ.SCC file before opening the solution?

Have you attempted to enable the "Connect Automatically" option found in the SOS "Connect to Server" dialog? If this option is enabled and the "Remember my password" in the SOS login dialog is also enabled, then no SOS dialogs should appear when the solution is being op...

Thanks for the detailed log files. Without there being any sort of binding issues, I am uncertain as to why this problem is happening. Dan, who originally helped you with this issue, will be in on Monday and I will discuss this matter with him to see if he has any more suggestions. Tonya Nunn Source...