Re: .svn vs _svn on VS.NET (ASP.NET)

While I do not merit a vote on this issue, I think the idea of a runtime
configuration option, perhaps in the 1.1 time frame, might be the best
solution, especially if Whidbey winds up not addressing this problem. I
have not seen any guarantees that it does.

That being said, reading the various posts, it seems like the do nothing
option is the correct short term option. I still think the issue could be
solved, perhaps permanently, with a good FAQ explanation of the problem and
workarounds, and a link to a "blessed" build where the folder name has been
changed using the documented patch. If the same people that provide a
VS.NET SCC provider, or add-in, also provided an official SVN build with
this workaround in place, I think that would be acceptable. I think the
biggest issue for VS.NET users would just be doing the build themselves.

The FAQ would hopefully minimize the mailing list disruptions.

Thanks

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 10 01:14:52 2004