On Monday, March 8, 2004 SteveKing wrote:
> Adal Chiriliuc wrote:
>> Visual Studio 6.0 was released in 1998. It still is the predominant VC
>> version out there. The Service Pack 5 update for this is one of the most
>> downloaded items from Microsoft site.
> [snip]
>> If you care about Win32/Visual Studio you should "fix" this.
> But VS6 doesn't have *any* problem at all with those .svn folders! Only
> VS.NET, and _only_ if you use it with web projects and IIS6. So you just
> proofed yourself wrong - it's not a very big userbase which has this
> problem. And those still using VS6 will sometime update to VS.NET, but
> if they do they will update to the most current version (which will then
> be whidbey which doesn't have this bug anymore).
This problem does not affect me in any way and I never stated
otherwise. I do not use ASP.NET and I don't plan to use it either.
What makes you so sure they will upgrade to Whidbey? Visual Studio
.NET 2003 already has pretty high system requirements. God knows what
Whidbey will ask for.
Question: Why is the Win32 version of SVN compiled with Visual Studio 6?
Because everybody has it. The same thing will happen with Visual
Studio .NET 2003, which is the logical upgrade. After people upgrade
to this it will take a long time to upgrade to the next version.
The fact that right now it doesn't have a big userbase it's not
relevant. What wories me is that word starts to spread that SVN
doesn't work well with Visual Studio .NET. How many users do you think
will actually study what the real problem is?
If somebody skims over this list it gets the following picture:
We're hardcore Linux users and don't give a f**k about Visual Studio
bugs. Fix it yourself or shut the f**k up.
This is bad for business.
Adal Chiriliuc
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 8 23:44:06 2004