You have to change them back to web applications instead of class
libraries, vs2005 will fail to convert the project. Thankfully I
could find the commit where I changed it and reverting that was
sufficient to change it back. with vs 2005 though, it works fine with
.svn directories.
The new VSS is in my opinion worthless. It doesn't address branching
or most of the other issues I had with VSS such as database
corruption. You'd have to use the completely new team system studio
solution they have for that which I viewed as pricey for a new
solution on the market that was unproven.
- Jody
On 2/9/06, Peter Imburg <peter_imburg@benefitstreet.com> wrote:
> I converted some VS.Net 2003 web projects to regular class libraries for reasons already covered on the list.
>
> I am pondering an upgrade to VS.Net 2005 and was wondering... how do class libraries do as web applications in VS.Net 2005? Has anyone made this migration? Do you have any suggestions for how the projects should be structured to play nice with subversion and take best advantage of VS 2005 features?
>
> Finally, I know that VSS has been pretty substandard for a long time (which is why we like subversion). However, with VS 2005 there is apparently a fairly substantial VSS overhaul. Does anyone have thoughts on how the new VSS compares to Subversion and the relative advantages of the two.
>
> I recognize that these are not necessarily "Tortoise" questions, but I thought this would be a good list for discussing these issues.
>
> Thanks,
> Peter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Feb 10 06:42:09 2006