I down loaded the new MSSCI provider and insntalled it on a computer that has both VS2005 and VS2003.
I opened our 19 project VS2003 solution and tried to add it to source control. I was prompted for the TFS server. Then after several messages in the output window, The following repeated several times.
---- Operation started at time 11:21:34 AM ----
---- Operation completed successfully at time 11:21:35 AM ----
The system the then appears to be saving information into the solution, but I get the following message.
The solution file 'c:\dge\Dev\Srver\Srver.sln' was not written successfully. Check that the location is available, the file is writable and there is enough room on the disk.
I am not sure what is ment by the location is "available", but the path exists. the file exists is writable, and there is plenty of room on the disk.
I can successfully create a new (simple) solution and add it to source control without issue.
Error using MSSCCI provider. <file>.sln not successfully written. ...
cplusplus1
Michal and I have tracked down the problem. The issue is that VS2003 creates a "hidden" hint file, <solution name>.vsscc, if your solution and its projects are not single-rooted. For instance, if you do not check "Create directory for solution" when you are creating the solution and you add additional projects without changing the default path then you will end up in this situation.
Because the hint file is hidden, TFS fails to pend an Add for it (the TFS object model does not permit pending adds on hidden files) and subsequently fails to check it in. This is all taking place as part of the eventing during the save of the solution. Therefore, an error is reported back via the eventing and VS 2003 reports that the save of the solution failed. In point of fact, the solution file is fine; it is the hint file that is the issue.
The bad news is that trying to attrib the .vsscc file to be non-hidden does not work. VS 2003 simply re-attribs it back to hidden prior to attempting the pend Add and CheckIn.
I have verified the following WORKAROUNDS:
1) Make your solution single-rooted
-or-
2) Use Team Explorer to add the files to SCC and use VS 2003 to bind the solution. i.e.
a) Use Source Control Explorer in VS 2005 Team Explorer to create SCC mappings for the solution and project folders
b) Use Source Control Explorer in VS 2005 Team Explorer to Add Folders (via toolbutton) and create pending adds for all files concerned. Then CheckIn from the Source Control Explorer or Pending Changes toolwindow.
c) Open solution from disk in VS 2003 and use File->Source Control->Change Source Control to bind the solution and project roots. CheckIn all changes and you are done.
We have filed a bug internally to resolve the issue with the .vsscc file and hope to roll out a fix in the next drop of the TFS MSSCCI provider.
Thanks for your feedback!
--Ben Ryan
r3n
I was able to find a way to add my solution to TFS manually. It was very convoluted so I assum there must be a better way.
After adding the solution to TFS manually, I was able to "Change Source Control" and bind them. During the process it aske me to check out everything. I clicked "OK" and got the same "... not successfully written" error message.
Now I cannot go back to "Change Source Control" without getting this error message.
If I try to close the solution I get the "... not successfully written" messate. If I cancel I get "Unspecified error".
When I Open the solution, I then get "XBUtil appears to be missing som required source control information..." eror message. After I click OK. I get prompted to connect to TFS several times.
At this point I am able to get to Change Source control. Everything is bound and valid except the solution which ins Not Controlled.
When I bind the solution. I successfully binds. All the projects and the solution have red checks so I attempted to check in all pending changes. ONly the Solution .vssscc needs to be added. I clicked Check-in
After adding that .vssscc file I got another prompt to check-in all the other .vspscc files need to be checked in (add). I clicked Check-in.
After adding the .vspscc files, I got another prompt to check-in the solution file (edit) I clicked check-in.
After checking-in the edited the solution file, Igot another prompt to check in the .csproj files (edit). I clicked Check-in.
Then I got a message. "Some of the items you attempted to add to source control do not exist on disk and could not be added. If these items are user-specific, such as build outputs, you should exclude them from source control."
Everything appeared to be checked in except one file (probably the one referred to in the last message. Manually checking in that file resulted in the same message.)
I attempted to remove that file (which is no longer needed for our build process.) but couldn't because the project was under source control and not checked out. But when I tried to check out the project I got the "some of the items..." error message and the project was not checked out.
All the other project appear to be working properly!!! Yay.
I closed the solution and reopened it. All the projects loade with out any prompts, but I still had that non-existant file. This time I was able to check out the project and remove the file.
All is working for us now. I provide the above details should you find it useful in your debugging process.
LSStudio
Thanks Ben.
Our solution is already single-rooted. What is "odd" about our solution is that one of its projects is under source control (Source Offsite/VSS) but the solution is not. I attempted to remove the Source control information manually from these files but was unsuccessful. It still gave me the same message. I was either unable to find all the source control references or that is not the cause of the issue.
We are new to TFS so please bear with me, but I was unable to add folders to a Team Project, the toolbar button is not enabled. It becomes enabled when I select an existing solution folder, but I don't want to add my new solution under an existing one. How do I add a folder directly under a Team Project
pdurbha
We have just reproduced this problem locally and are investigating.
I will post again as soon as I have some more information.
--Ben Ryan