RE: [Nant-users] Building by solution task - complete solution file verses building by exec program - devenv task

Kevin, I've had a quick look, and you're right: our behaviour differs from that of VS.NET (but I don't think it does any harm). If I recall correctly, we needed to recursively reference assemblies because of some issue with vbc (we do not need to do this for csc). I'll have a closer look later to

RE: [Nant-users] Building by solution task - complete solution file verses building by exec program - devenv task

Kevin, Can you send me a repro for the issue you described ? Thanks ! Gert > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Read, Kevin > Sent: donderdag 17 november 2005 22:27 > To: nant-users@lists.sourceforge.net > Subject: RE: [Nant-users]

RE: [Nant-users] Building by solution task - complete solution file verses building by exec program - devenv task

Hi Tim, We have also had dramas with the solution task producing incorrect results. In our case, the assemblies were compiling, but when we had a chain of dependencies (Assembly A calls B calls C) it would include the C dependency in the A metadata. We still use the solution task for most of ou

RE: [Nant-users] Building by solution task - complete solution file verses building by exec program - devenv task

Tim, The best thing you can do is package up a small repro, and submit a bug report. Gert > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Tim Mayert > Sent: donderdag 17 november 2005 19:59 > To: nant-users@lists.sourceforge.net > Subject: [Na

RE: [Nant-users] Building by solution task - complete solution file verses building by exec program - devenv task

Hello Tim! We have had a somewhat bumpy road to build solutions containing C++ projects. Most our projects are C#, but a few (less than ten) is C++. Two of those have caused problems when building with Nant. Both time we needed to perform some magic with the task before calling the task. In vi

[Nant-users] Building by solution task - complete solution file verses building by exec program - devenv task

Okay I have running out of ideas here on calling the solution task to build a full solution file. This just do not seem to work correctly! First, the build order does not be the same as I see it if I build from the exec program - devenv task Second, some project files something get completely mis

RE: [Nant-users] Calling Solution target to build complete solution

I'll try and get a small sample output when I can. But I seem to run into lots of issues with calling the solution files. The order always seems different than that is indicated in the solution file itself, projects don't always build or they fail to build, but build fine in the IDE. I am curren

Re: [Nant-users] Problem with readonly attribute on property

Rod Ayers wrote: ... A related question: I'd like to check and see if the property named in property.name exists. All the "valid" properties have already been assigned default values. If property.name exists, I will override with the value in property.value, and set to readonly="true". Otherwi

Re: [Nant-users] Nant Response file

Rod Ayers wrote: What is the format of the NAnt response file? Something like this, using a file called NAnt.Response -buildfile:NAnt.build -l:My.log -D:app.file.buildfile=My.build -D:app.file.properties=My.properties invoked like: NAnt @NAnt.Response yep - thats exactly right. Ian

[Nant-users] Nant Response file

What is the format of the NAnt response file?  Something like this, using a file called NAnt.Response   -buildfile:NAnt.build -l:My.log -D:app.file.buildfile=My.build -D:app.file.properties=My.properties   invoked like:   NAnt @NAnt.Response     Thanks, Rod

RE: [Nant-users] Problem with readonly attribute on property

Hi, Gert I'm presently using 0.85-rc3. My next shot to work on it is Friday, and I will download the latest Nant and NantContrib nightly builds. A related question: I'd like to check and see if the property named in property.name exists. All the "valid" properties have already been assigned