VS 2008 solution file get checked out automatically

[nalwi]

I am using VS 2008 with vault enhanced client V 4.1.3 (18336). I 've got VS2008 solution with several projects under it.
Every time when I open the .sln file from VS2008 the .sln file get checkout. but no modications made by the client.
Any ideas what is causing this behavior?
Thanks!

[ian_sg]

If you save the file and check it back in, does the behavior persist?

[nalwi]

If save the solution file and checked back in it will not be checked out automatically. This issue (auto checkout of the .sln file ) only happens when I open the solution is VS2008 or when I double click the solution file to open in vs2008. We upgraded from previous vault with vs2005 to new vault version with vs2008.
we did not exprienced this issue with previous version.

[ian_sg]

Did checking in the solution file make the problem go away for good, or just during that Visual Studio session?

Can you tell what in the solution file changed with this most recent checkin?

[nalwi]

The checkin holds only for the current Visual Studio session. when you open vs2008 it always get checked out.
Nothing has changed in the .sln file between auto checkout and manual chekin.

[nalwi]

I've attached a vs2008 solution here. This is a standard solution structure created by Microsoft Smart client software factory which is a
valid source safe folder structure. Hope this helps.

[ian_sg]

I was able to duplicate the behavior you describe. I'll be back when I know more.

[ian_sg]

We've determined that it's the ExtensibilityGlobals section of the solution file that causes this behavior. In the sample solution you sent us, it was this:

Code: Select all

GlobalSection(ExtensibilityGlobals) = postSolution
  ShellProjectGuid = 98be037a-2567-485b-abc0-699f3844fd17
  CommonProjectGuid = 905911a8-840f-423b-a589-8fb949eed9b1
  RootNamespace = SmartClientDevelopmentSolution1
 EndGlobalSection

When a solution includes this section, Visual Studio tells us it wants to edit the solution file, and we dutifully check it out. I've confirmed that MSSCCI clients (VSS or Vault), however, do not exhibit this behavior. We're working with Microsoft to determine how the MSSCCI code knows to ignore this edit request, as it doesn't appear special in any way.

[nalwi]

This section in the .sln file is mandatory for smart cleint reciepts to work within vs2008.So we cannot remove it.
Please let me know when you worked out a fix for this issue.
Thanks!

[JustinAtAspen]

Has anyone found a solution for this problem?

[lbauer]

We don't have a solution as yet, but this issue is slated to be fixed in Vault 5.0, due out later this year. It is logged as bug 13813.

This is a problem for you in the meantime, you could try using the Vault Classic Client integration. You would need to unbind it and and rebind it with the Classic Client to do this.