I have been working with Vault for a while now and have had this problem off and on, but now it has come back and won't go away. After numerous problems in simply adding a vault controlled project, I created a new project, added the existing files, and added the project to Vault through VS.NET 2003. The project adds fine every time, and the files are in Vault; however, they all show to be new files in VS.NET immediately. All check-ins fail after that (I get no error messages or status indicators, just nothing). I then close VS.NET and reopen it, and try to change source control. It shows the binding as invalid, and all attempts to rebind the project are invalid as well. I cannot get any projects to bind to Vault anymore. I don't think this is a server problem, as another PC connecting to the same server can bind without a problem.
Any help will be greatly appreciated!
Invalid status for VS.NET project
Moderator: SourceGear
I am going to need to get some additional information from you. Below you stated that you create a new project and then add existing files.
What files are you adding? Files that already exist under source code control or are they new files? How do you attempt to add them?
What do you mean by they all show up to be new files in VS.Net immediately?
Are the files automatically checked out or are you checking them out successfully and they just won't check in?
When you close VS.Net and reopen it, how are you attempting to open the project?
Thanks.
Tonya Nunn
SourceGear Support
What files are you adding? Files that already exist under source code control or are they new files? How do you attempt to add them?
What do you mean by they all show up to be new files in VS.Net immediately?
Are the files automatically checked out or are you checking them out successfully and they just won't check in?
When you close VS.Net and reopen it, how are you attempting to open the project?
Thanks.
Tonya Nunn
SourceGear Support
-
Guest
The project is an existing web project that I had added to Vault previously. The files I mention are simply the files and folders within the project (web pages, and folders). Before I recreated the project (it was already unbound from Vault), I deleted it from Vault and started from scratch each time I tried it. When I add them, I add them from VS.NET itself. To create the project, I create it through VS.NET itself as well by choosing the Add Project to Source Control menu item from the Source Control menu. I don't actually do anything with the files, they are added as part of the project (sorry about that confusion).
As soon as I add the project, all files appear as though I have just created them in VS.NET. They show up with a red checkmark by them which usually signifies that you have created a file in VS.NET, but haven't checked it in to source control yet. This is what I meant by the show up to be new files; however, if I run the Vault client, they show the same checkmark, so they must be added?? (I've never seen this before, so I dont' know why it is happening)
After that, I cannot check the files in with VS.NET at all. They appear to be controlled by Vault, but that's about it. I then proceeded to close VS.NET and reopened the solution that contained the project (through normal VS.NET Open Solution). It then complains that the project is a VS 6 project and will have to be disconnected. I have no choice but to click OK, so I go in to Change Source Control, and try to rebind the project (not the solution). It then opens the vault repository, etc. without a problem, I click on the project, choose OK, and then it goes back to the Change Source Control window, but states that it is invalid, and won't let me bind it.
As soon as I add the project, all files appear as though I have just created them in VS.NET. They show up with a red checkmark by them which usually signifies that you have created a file in VS.NET, but haven't checked it in to source control yet. This is what I meant by the show up to be new files; however, if I run the Vault client, they show the same checkmark, so they must be added?? (I've never seen this before, so I dont' know why it is happening)
After that, I cannot check the files in with VS.NET at all. They appear to be controlled by Vault, but that's about it. I then proceeded to close VS.NET and reopened the solution that contained the project (through normal VS.NET Open Solution). It then complains that the project is a VS 6 project and will have to be disconnected. I have no choice but to click OK, so I go in to Change Source Control, and try to rebind the project (not the solution). It then opens the vault repository, etc. without a problem, I click on the project, choose OK, and then it goes back to the Change Source Control window, but states that it is invalid, and won't let me bind it.
Would you mind to give me the exact steps that you are taking to produce this problem? Start off creating a new project and send me some screen shots (both from VS.Net and the Vault Client) as you go along so that I can see exactly how your projects are configured.
If there is any important information listed in the Source Code dialog from with VS.Net, you may also want to include this.
It would also be helpful to see the log file created using the IDE. Please reivew the following KB article to set this up appropriately.
http://support.sourcegear.com/viewtopic ... ht=ide+log
Tonya Nunn
SourceGear Support
If there is any important information listed in the Source Code dialog from with VS.Net, you may also want to include this.
It would also be helpful to see the log file created using the IDE. Please reivew the following KB article to set this up appropriately.
http://support.sourcegear.com/viewtopic ... ht=ide+log
Tonya Nunn
SourceGear Support