Visual Studio.Net and Subversion?

["Ayres, David" <DA...@lear.com>]

I read here
http://subversion.tigris.org/servlets/SearchList?list=users&searchText=visua
l+studio&defaultField=subject&Search=Search
<http://subversion.tigris.org/servlets/SearchList?list=users&searchText=visu
al+studio&defaultField=subject&Search=Search>  that there's a problem with
Subversion using a "." before the svn directory for Visual Studio.Net users.
Is this still a problem, has it been resolved?  Why can't the creators of
this software just NOT use the "." before the directory name?  What's the
point in having the "." there?  This obviously causes a lot of problems with
Visual Studio.Net.  I guess that the "." is needed for some other purpose?
Please forgive my ignorance, my teammate and I are just trying to figure
this out.

It's too bad because your product, when I can use in conjunction with my
programming tool, is really great.  It's better than great, it's awesome!
But this small issue causes some headaches.

Thanks,

David



**********************
** LEGAL DISCLAIMER **
**********************

This E-mail message and any attachments may contain 
legally privileged, confidential or proprietary 
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of 
this message to the intended recipient(s), you are 
hereby notified that any dissemination, distribution 
or copying of this E-mail message is strictly 
prohibited. If you have received this message in 
error, please immediately notify the sender and 
delete this E-mail message from your computer.

Re: Visual Studio.Net and Subversion?

[John Peacock <jp...@rowman.com>]

Ayres, David wrote:

> that there's a problem with Subversion using a "." before the svn 
> directory for Visual Studio.Net users.  Is this still a problem, has it 
> been resolved?  Why can't the creators of this software just NOT use the 
> "." before the directory name?  What's the point in having the "." 
> there?  This obviously causes a lot of problems with Visual Studio.Net.  

The problem is that Visual Studio.Net has arbitrary problems with directory 
names with only an extension; it ultimately comes from M$oft's use of the file 
extension to denote file type.  The fault is with M$loth, but no one is 
expecting them to fix it.

The problem has a few work-arounds, but none were judged worth holding up 1.0.0 
for, since it only affects Win32 users and then only those using VS.NET. 
Notwithstanding M$oft's marketing efforts, .NET is not the only development 
platform.

FYI, a leading '.' on a file/directory name makes it hidden under Unix.  Win32 
uses a flag in the filesystem to hide files/directories.  By having a consistent 
naming convention, it is possible to copy a working copy from Unix to Win32 (a 
feature I personally find to be of little practical use).

I expect that this particular difficulty will be fixed sooner, rather than 
later, probably as part of 1.1.0 (but don't quote me!  I'm just a user not a 
developer ;~).

HTH

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org