Re: [NAnt-users] NAnt copy command failingwithSystem.IO.PathTooLongException

Yes, I think so. Don't have time to look it up right now, but will do it later. - Original Message - From: "Bob Archer" <[EMAIL PROTECTED]> To: "Gert Driesen" <[EMAIL PROTECTED]>; "Tim Mayert" <[EMAIL PROTECTED]>; Sent: Thursday, November 08, 2007 5:26 PM Subject: RE: [NAnt-users] NAnt

Re: [NAnt-users] NAnt copy command failingwithSystem.IO.PathTooLongException

A while ago I read a blog post of one of the Windows developers/architects while explains a way to support paths of more than 260 characters. If I recall correctly if we using a special character as prefix. I'll need to look it up again. Either we encourage users to use that prefix or we implic

Re: [NAnt-users] NAnt copy command failing withSystem.IO.PathTooLongException

Instead of using the tag you may just try using exec tag and doing an xcopy. BOb From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Mayert Sent: Thursday, November 08, 2007 10:52 AM To: nant-users@lists.sourceforge.net Subject: [NAnt-us

Re: [NAnt-users] [Bulk] Re: VS.Net 2005 and NAnt 0.85 - I'm going insanewiththis!!!!

Just out of curiosity, why are you using for the msbuild, and not just ? _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Hartell Sent: Thursday, November 08, 2007 10:59 To: Bob Archer; nant-users@lists.sourceforge.net Subject: [Bulk] Re: [NAnt-users] VS.Net 2005

Re: [NAnt-users] VS.Net 2005 and NAnt 0.85 - I'm going insane withthis!!!!

Yes, I tried using verbose to confirm the command line and now I'm using it with msbuild... I did try msbuild like this... and that seems to work, well at least for one of the three solutions I am trying to get to work... at least it is a step closer. Thanks for everyone's help

[NAnt-users] NAnt copy command failing with System.IO.PathTooLongException

During my NAnt build I have our product installs generated. Once the build is complete I use the copy task to copy the output install folders to out network testing folder. One of the installs is in a CD Image format and it is built in uncompressed mode, meaning that the full directory structure is

Re: [NAnt-users] [Junk released by Allow List] Re: VS.Net 2005 and NAnt 0.85 - I'm going insane withthis!!!!

At this point, I would use Process Monitor from SysInternals to verify that the correct .sln file is being loaded. -- Bill Arnette www.starwitness.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Hartel

Re: [NAnt-users] VS.Net 2005 and NAnt 0.85 - I'm going insane with this!!!!

Thanks for the suggestion. I tried it... But I get the same problem that has been sending me crazy all day... :-( I've checked maybe 1000 times now that the command line and working directory etc is correct, and it is. Nothing has changed other than the VS

Re: [NAnt-users] VS.Net 2005 and NAnt 0.85 - I'm going insane withthis!!!!

Wayne Hartell <[EMAIL PROTECTED]> wrote: > Hi All, > > We have beem using NAnt-0.85-rc3 for quite some time with Visual > Studio 2003.NET. In our build files we have been executing builds > like this: > > If I may make a suggestion: don't use devenv for VS 2005 projects, use MSBuild instead

Re: [NAnt-users] [Bulk] Re: VS.Net 2005 and NAnt 0.85 - I'm going insane with this!!!!

We're not calling the exec directly, but using It works fine this way (the task for vs2003 didn't work for us and we did what you did for it, but for vs2005 msbuild seems to be the way to go). Eric T. _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Markus Ewa

Re: [NAnt-users] VS.Net 2005 and NAnt 0.85 - I'm going insane with this!!!!

Wayne Hartell wrote: Hi All, We have beem using NAnt-0.85-rc3 for quite some time with Visual Studio 2003.NET. In our build files we have been executing builds like this: program="${devenvPath}" workingdir="..\Development\" commandline="/r

[NAnt-users] VS.Net 2005 and NAnt 0.85 - I'm going insane with this!!!!

Hi All, We have beem using NAnt-0.85-rc3 for quite some time with Visual Studio 2003.NET. In our build files we have been executing builds like this: Now, we are upgrading to VS.Net 2005, so I have made the following changes... 1. Updated to NAnt-0.85 2. Changed to 3. And