Re: Re: [NAnt-users] Differentiating .NET 2003 / 2005 solution

or asp.net 2.0 projects, which don't have *proj files anymore. Marc Towersap Sr. SCM Engineer - Original Message From: Gary Feldman <[EMAIL PROTECTED]> To: nant-users@lists.sourceforge.net Sent: Monday, January 30, 2006 14:37:16 Subject: Re: Re: [NAnt-users] Differentiatin

Re: Re: [NAnt-users] Differentiating .NET 2003 / 2005 solution

Scott Willeke wrote: Since those are valid xml files, anothe way might be via xmlpeek . No, this is about solution files (.sln), which are not XML. The various project files (.csproj, .vcproj, etc.) are XML, and that shou

Re: [NAnt-users] Differentiating .NET 2003 / 2005 solution

29, 2006 6:36 AM To: nant-users@lists.sourceforge.net Subject: [NAnt-users] Differentiating .NET 2003 / 2005 solution   Anyone knows an easy and fast way to differentiate betwene a .NET 2003 and a .NET 2005 solution file? I want to run a switch over our build task to move into a separate buil

RE: [NAnt-users] Differentiating .NET 2003 / 2005 solution

so you may need to work on it a little.                   Noel From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Tomiczek Sent: Sunday, January 29, 2006 6:36 AM To: nant-users@lists.sourceforge.net Subject: [NAnt-users] Differentiating .NET

[NAnt-users] Differentiating .NET 2003 / 2005 solution

Title: Differentiating .NET 2003 / 2005 solution Anyone knows an easy and fast way to differentiate betwene a .NET 2003 and a .NET 2005 solution file? I want to run a switch over our build task to move into a separate build setup based on whether a .sln is for VS.NET 2003 or 2005. Naturally