Open From Source Control webprojects fails in VS.NET 2003

ERodriguez · Post by **ERodriguez** » Thu Mar 31, 2005 3:00 pm

Evaluating Vault and ran into the following error while opening a web project from source control.

This user reports the same error http://support.sourcegear.com/viewtopic ... ose+reopen
but there was no reply or resolution to his problem.

I did notice the KB about Vault and Sharepoint not playing well on the same server. I performed the install of Vault after reading this KB, however. Is the error I am getting related to the Sharepoint problem?

My solution contains 4 projects. 3 are non-web and import fine. Its the webproject that consistently fails. Re-opening the solution from source control does not work.

Please advise. Thanks!

dan · Post by **dan** » Thu Mar 31, 2005 4:04 pm

We'll need more details on the steps you have taken to get everything into Vault, and the error message you are getting. If you imported the projects, did you unbind the project before the import? That often helps when switching over from VSS.

Also, you might want to turn on client logging, which may help us isolate the problem. Start here: http://support.sourcegear.com/viewtopic.php?t=2898 for how to set that up.

ERodriguez · Post by **ERodriguez** » Fri Apr 01, 2005 7:49 am

Hi Dan, thanks for the reply, I will post request info shortly.

I did not unbind the projects prior to re-opening... but when I was prompted to change bindings I started getting odd behavior - the non-webprojects did not like the specified server, yet the webproject DID. Not sure why.

I then unbound all the projects and attempted to open from source control, when the errors occurred. Recreating the virtual directory did not work either.

As a side note, the vdir is not located under the default web root. Not sure if this is important or not.

ERodriguez · Post by **ERodriguez** » Fri Apr 01, 2005 8:39 am

Find the log attached. I am not sure if it will provide anything useful since it doesnt appear the log even contains the information related to my web project.

Heres what I have done so far:
- Eliminated my local working project completely
- Attempted an open from Source Control
- Pointed the web project to my virtual directory (I have recreated this directory a number of times now)
- Greeted with the failure error
- VS continues to load the remaining projects, bound to source control, with the web project unavailable.

The only thing created in the web directory when the source control binding fails is the .webinfo project.

ERodriguez · Post by **ERodriguez** » Fri Apr 01, 2005 8:58 am

One last thing (sorry for them multiple posts) -

The Vault server is in a different domain than the computer I am working off of. The domains are in a full trust relationship.

dan · Post by **dan** » Fri Apr 01, 2005 9:06 am

This is a long shot, but if you've changed the location of the web project, trying deleting the Visual Studio web cache. It should be in Docs & Settings/[username]/VSWebCache. It might be that VS is continuing to think the web project is in the old location.

The actual location of the virtual folder and the different domains should not be an issue.

I think VS tries to automatically set the web project to be within inetpub, but if you have already manually created the virtual folder, I think you can provide VS with the URL and it should make the connections.

ERodriguez · Post by **ERodriguez** » Fri Apr 01, 2005 9:34 am

dan wrote:This is a long shot, but if you've changed the location of the web project, trying deleting the Visual Studio web cache. It should be in Docs & Settings/[username]/VSWebCache. It might be that VS is continuing to think the web project is in the old location.

The actual location of the virtual folder and the different domains should not be an issue.

I think VS tries to automatically set the web project to be within inetpub, but if you have already manually created the virtual folder, I think you can provide VS with the URL and it should make the connections.

that didnt work. I havent changed the location of the web project - its in the same location as it was while under VSS control.

I had a co-worker perform the source control change, and everything worked as expected. The only difference was I had him unbind the project prior to rebinding to Vault source control.

Any other thoughts? Thanks for your help!

dan · Post by **dan** » Fri Apr 01, 2005 9:49 am

ERodriguez wrote: I had a co-worker perform the source control change, and everything worked as expected. The only difference was I had him unbind the project prior to rebinding to Vault source control.

Can you try that?

ERodriguez · Post by **ERodriguez** » Fri Apr 01, 2005 9:58 am

lol - I DID! Didnt work.

I notice that when I browse to the explicit location of the web directory, it is not recognized as a valid virtual directory (dialog box pops up telling me that I need to specify a valid HTTP web).

Its there, however (I can browse to localhost/myweb). However, I cant set server extentions on it and create it as a true subweb, which I believe might be the source of all my issues.

dan · Post by **dan** » Fri Apr 01, 2005 10:03 am

Ah, yes, that might be it. But how to figure out what the problem is?

Can you try creating a different name for the Virtual Folder and seeing if that works? Your app might not work if it needs the specific name, but that might verify that it is something about the virtual folder.

Also, you might try deleting it and trying it in inetpub, which IIS or VS might like better.

ERodriguez · Post by **ERodriguez** » Fri Apr 01, 2005 10:37 am

I'm trying to avoid deleting and recreating under the wwwroot directory. It doesnt match the folder structure of the other developers.

VSS still recognizes this as a valid virtual directory though. If I rebind to VSS, everything works as expected. So I'm back to figuring out why IIS isnt behaving.

Thank you for your help...

ERodriguez · Post by **ERodriguez** » Fri Apr 01, 2005 11:01 am

OK, I FINALLY got this working. I had to bind the solution back to VSS, and unbind, then re-bind to Vault.

The problem was that with my recreations of the web directory, server extensions were not configured for it. So I Googled and turns out that the Server Extention configuration option in IIS Manager does not show up unless you restart the IIS manager. Go figure

Once I did this I was able to set server extensions. Vault still didnt like the location though. So I went through the rebind/unbind/rebind operation once more, and all is working.

Many thanks to Dan for his quick and helpful support.