Hi,
I have used a solution found at : http://dotnetjunkies.com/WebLog/mjordan ... /5033.aspx in order to get around XP's single website limitation.
However, this seems to be causing me problems now that I am adding a solution (containing an asp.net project) to source control that exists on a new site created in this manner.
I can add to the solution/project to source control succesfully, and am able to check-in and check-out files as usual. However, when I close and reopen the solution in visual studio, I get the error 'The source control binding information has been removed for project .[asp.net project]. The project will be opened without source control'. The other (non asp.net projects) in the solution open fine.
The VS.net / Vault error message isn't very helpful in diagnosing the cause of the problem. It's a long-shot but any ideas??
Multiple web-site solution and vault
Moderator: SourceGear
I don't quite follow. Does your soluton contain projects from multiple Vault repositories? If so, that isn't yet supported in Vault.
Last edited by dan on Wed Jun 15, 2005 8:18 am, edited 1 time in total.
No, there is just a single asp.net / web project in the solution.
I do have other websites, but not within this solution, and not that I'm trying to add to source vault. The 'solution' (in the literal sense) I was referring to previously was just a way to create new websites on the same IIS server in XP (i.e. more than just the 'Default Web Site').. there is no functionality in XP Pro that allow you to do that with IIS, and I use this method to bypass that.
The asp.net project that I am adding to Souce Vault exists on such a IIS website, but Source Vault doesn't like something about it.. I really don't know what. I appreciate it is a tricky problem as the setup is non-standard.
I do have other websites, but not within this solution, and not that I'm trying to add to source vault. The 'solution' (in the literal sense) I was referring to previously was just a way to create new websites on the same IIS server in XP (i.e. more than just the 'Default Web Site').. there is no functionality in XP Pro that allow you to do that with IIS, and I use this method to bypass that.
The asp.net project that I am adding to Souce Vault exists on such a IIS website, but Source Vault doesn't like something about it.. I really don't know what. I appreciate it is a tricky problem as the setup is non-standard.
It may be that Visual Studio expects web projects to be loaded to 'localhost', so if this web project is loading to a differently named website, it might get confused?
You could turn on IDE logging and see whether any useful info is logged. See http://support.sourcegear.com/viewtopic.php?t=2898 for more info.
You could turn on IDE logging and see whether any useful info is logged. See http://support.sourcegear.com/viewtopic.php?t=2898 for more info.
The domain is still localhost - http://localhost/default.aspx maps to something like c:\inetpub\wwwroot\mysite\default.aspx.
I'll take a look at the logs as you suggest to see if anything turns up.
I'll take a look at the logs as you suggest to see if anything turns up.
It may be that you need to delete your vswebcache directory.
http://blog.devstone.com/aaron/archive/ ... 2/159.aspx
http://blog.devstone.com/aaron/archive/ ... 2/159.aspx