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:
> 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:
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.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-12-26 13:48:05 CET