I am using the 4.05 client/server, with VS2005 SP1.
Basically if I start a brand new solution and add a few projects (steps described below), and then go to "Change Vault Bindings", several of the bindings are listed as "invalid". I noticed this when converting some VS2003 plug-in projects to the VS2005 plug in, but then discovered I can reproduce when starting a brand new solution with the VS2005 plug-in.
Here are the steps:
root working folder $/ is c:\gear
Create a new Windows C# Class Library project called "DLL" with solution named MyApp, with "create directory for solution" checked.
solution is in $/MyApp
with working folder c:\gear\MyApp
and the library will be in
$/MyApp/DLL
with working folder c:\gear\MyApp\DLL
and then add a "web site" type project to the solution (ASP.NET web site)
with location "file system" using folder c:\gear\MyApp\UI
$/MyApp/UI
and then add a "web site" type project to the solution (ASP.NET web service)
with location "file system" using folder c:\gear\MyApp\WS
$/MyApp/WS
If I then check in all the files in the solution, everything looks OK in solution explorer (lock icons), but then if I go to File menu, "change vault bindings" the "web site" project bindings are listed as "Invalid". If I rebind it then says "valid" but then re-opening the dialog it says invalid again. Rebinding each one individually yields the same result.
Any ideas?
Invalid Bindings with 4.05 client/server
Moderator: SourceGear