Visual Studio 2005 -- Add website give invalid handle error
Moderator: SourceGear
Visual Studio 2005 -- Add website give invalid handle error
When I File->Source Control->Add Web Site to Source Control after going through the project 2003->2005 conversion, I get an invalid handle error from the Vault plugin. The only way to close vs2005 is to kill the process.
After killing VS2005, restarting and reloading the solution, I can add it to source control.
I am using Vault 3.1.5 (3546). Any ideas?
Thanks,
Timothy
After killing VS2005, restarting and reloading the solution, I can add it to source control.
I am using Vault 3.1.5 (3546). Any ideas?
Thanks,
Timothy
Symptoms
The exact error message is "Invalid Handle" with an OK button. It only seems to happen with web projects -- and only seems to happen when trying to add the Web Site to source control directly after running the vs2005 conversion wizard on a solution.
Thanks,
Timothy
<a href="http://www.anatone.net">http://www.anatone.net</a>
Thanks,
Timothy
<a href="http://www.anatone.net">http://www.anatone.net</a>
I am currently working on reproducing this issue, we have had no other reports of this problem. I have to create the same scenario as yours and as of right now I only have a machine with VS.Net 2005 installed, not VS.Net 2003.
Until then, could you let me know if this problem only exists if you run the conversion program to convert your solution from VS.Net 2003 - 2005?
Thanks,
Tonya
Until then, could you let me know if this problem only exists if you run the conversion program to convert your solution from VS.Net 2003 - 2005?
Thanks,
Tonya
2003-2005 conversion
Yes, it only happens with converted projects.
If I create a new project and add Web Site to source control, it works fine.
Thanks,
Timothy
If I create a new project and add Web Site to source control, it works fine.
Thanks,
Timothy
Confirmation
I can confirm this issue. I had the same problem after converting two web sites in a solution. My machine has both VS.NET 2003 and VS 2005 installed. I am not entirely sure which Vault version I was using at that time, but it was likely 3.1.2
Workaround
Tonya,
Thanks for looking into it. That is how I got around it also.
Timothy
Thanks for looking into it. That is how I got around it also.
Timothy