On Sun, Jan 1, 2012 at 10:26, Targumon (Amnon Sadeh) <targumon_at_gmail.com> wrote:
> Just to let you know, I weighed my alternatives and finally chose to stay
> with 1.7 :-)
> Having said that and for the record - I never worked with Visual Studio. I
> used _svn folders because I COULD (i.e. tsvn allowed me to).
> Of course if there's a TECHNICAL reason to refrain from it, I'd love to hear
> it.
> But deciding for me that I SHOULDN'T is condescending and reminds me of how
> some software corporate we all know behaves.
> Thank you for your consideration!
It's a hack to support decade-old software which almost no one uses
anymore. It was probably removed because the effort to maintain it
(and answer support questions) exceeded its usefulness. It was only
meant for a small set of use cases (as evinced by the name of the
environment variable, svn_asp_dot_net_hack) and you didn't even fit
into that use case.
Just because you *can* do something doesn't mean that you *should*. In
your case, you didn't need to, so you shouldn't have.
Lots of software has been crippled by the "need" to maintain 20+ years
of backwards-compatibility. Breaking things off allows everyone to
move forward in a better way.
> On Mon, Dec 26, 2011 at 2:47 PM, Andy Levy <andy.levy_at_gmail.com> wrote:
>>
>> On Mon, Dec 26, 2011 at 05:29, Kurt Pruenner <leak_at_gmx.at> wrote:
>> >
>> > On 26.12.2011 03:38, Dale McCoy wrote:
>> > > On Sun, Dec 25, 2011 at 09:50, Targumon (Amnon Sadeh)
>> > > <targumon_at_gmail.com> wrote:
>> > > > In TSVN 1.6.x there was an option (in the general settings section)
>> > > > to use
>> > > > "_svn" instead of ".svn" directories.
>> > > > Can't find it in 1.7.x - where did it go?
>> > >
>> > > That setting is gone.
>> >
>> > But the environment variable it toggled is still there:
>> >
>> > http://subversion.apache.org/docs/release-notes/1.3.html#_svn-hack
>> >
>> > And I'm still using it - I'm not sure I agree with the assumption Stefan
>> > made that noone is "still seriously using VS.Net" - what else would I
>> > use to work on legacy .NET 1.1 apps?
>>
>> Use MSBee? http://msbee.codeplex.com/
>>
>> > I sure as heck don't want to port any app that I have to make a small
>> > change on to .NET 4
>>
>> Newer releases of Visual Studio can still target older versions of the
>> Framework. That said, eventually you *do* have to move forward. MS
>> allows you to get away with running really old software but that
>> doesn't mean it's always advisable to do so.
>>
>> > - and there's still that abomination called the "SAP
>> > .Net Connector" *spit* that requires both Visual Studio 2003 *AND* Java
>> > to be able to use it's designer part as it was never updated for
>> > anything beyond VS2003... :(
>>
>> Here's what SAP says about working with Visual Studio 2005:
>>
>> http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/92333e6b-0b01-0010-9cbf-fecd62d6c895?QuickLink=index&overridelayout=true
>>
>> Or it may be worthwhile to look at other ways to connect to the
>> back-end like http://www.theobald-software.com/en/products/erpconnect.htm
>>
>> Or you can migrate your SAP back-end to their SOA architecture (see
>> http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14331 ). You'll
>> have to do it eventually, I imagine.
>>
>> ------------------------------------------------------
>>
>> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2900185
>>
>>
>> To unsubscribe from this discussion, e-mail:
>> [users-unsubscribe_at_tortoisesvn.tigris.org].
>
>
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2903473
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-01-01 17:08:52 CET