Open from Fortress option when using VS 2005 Client

dist0rti0n · Post by **dist0rti0n** » Sat Jun 02, 2007 6:40 pm

Whenever I try to open a solution using the File --> Open from Fortress option it never opens successfully. The solution file will open but Visual Studio tells me that it cannot open any of the projects.

I installed Fortress using my previous Vault and Dragnet DBs.

I deleted all of my working folders and completely uninstalled the vault client before installing fortress.

If I use the 2003 compatible client then I can do File --> Source Control --> Open from Source Control with no problems.

Am I doing something wrong?

Thanks,

Zack

Post by **jeremy_sg** » Sat Jun 02, 2007 7:20 pm

Zack,

Turn on Vault client logging for the Visual Studio 2005 client (edit the devenv.exe.config file) and try it again. Attach your log file to a mail to fortress-support at sourcegear.com We'll get this sorted out.

egli · Post by **egli** » Sat Jun 02, 2007 7:43 pm

I'm guessing that since the existing solution was originally bound using the 2003 compatible client, that's the only client that can open it. It will probably be a matter of Unbinding the solution and then Binding it again using the 2005 client.

dist0rti0n · Post by **dist0rti0n** » Sat Jun 02, 2007 8:10 pm

Log file sent.

jeremy_sg wrote:Zack,

Turn on Vault client logging for the Visual Studio 2005 client (edit the devenv.exe.config file) and try it again. Attach your log file to a mail to fortress-support at sourcegear.com We'll get this sorted out.

dist0rti0n · Post by **dist0rti0n** » Sat Jun 02, 2007 8:11 pm

I could try that, but man that will be a pain if its the case. Imagine having to re-bind 20-30 projects

egli wrote:I'm guessing that since the existing solution was originally bound using the 2003 compatible client, that's the only client that can open it. It will probably be a matter of Unbinding the solution and then Binding it again using the 2005 client.

egli · Post by **egli** » Mon Jun 04, 2007 3:26 pm

Please try out the steps listed on this new KB article and let us know how it turns out:

http://support.sourcegear.com/viewtopic.php?t=7937

dist0rti0n · Post by **dist0rti0n** » Mon Jun 04, 2007 9:32 pm

Yup, that works!

egli wrote:Please try out the steps listed on this new KB article and let us know how it turns out:

http://support.sourcegear.com/viewtopic.php?t=7937

gmagana · Post by **gmagana** » Sat Jun 09, 2007 6:11 pm

Can this somehow be automated? Like when you open the solution/project from source control it could detect 2003-style binding parameters and do these steps automatically? If not, going through all the projects/solutions will be a PITA...

Also, there seems to be a problem (or at least troubling behavior) if you have a bunch of solutions using a shared library... The first solution you convert with this method goes alright... But the following solutions that you try to convert give you a bunch of scary errors, that in the end really do not have visible (to me anyway) consecuence. The problem is that the shared library has already been converted to 2005-style bindings, so when you open the solution using the 2003-style interface, it hits the fan, since it is trying to load a project with 2005-style bindings. If you just dismiss all the errors that come up and proceed to unbind everything and re-bind everything, then all - seems to be - fine.

Anyway, it would be really cool to have the conversion from 2003-to-2005 binding style automated, specially if it would hide these errors from becoming visible...

gmagana · Post by **gmagana** » Sat Jun 09, 2007 7:47 pm

NOTE: This method does not work for "Web Site" projects, there is no entry for "Bind" after you select the VS2005 Fortress interface... I'm guessing that's becuase there is no solution file to VS2005 Web Sites...

Post by **jeremy_sg** » Sat Jun 09, 2007 8:04 pm

we're working on an automated solution, and it seems like it will be feasible. It will be a small utility that will edit solution files and project files outside of Visual Studio. I don't yet have a timeline for the release of it, but we will make sure to tell people about it.