epresent the dialogs from the vs.net
> install. Those merge modules could be checked into NAntContrib and
> then a VS.Net install wouldn't be required at all...
>
> What do you guys think? I personally lean towards checking in merge
> modules that represent common dialogs.
&g
Thanks guys!
I was able to get exec to devenv working as a stopgap. That will hold
me until Jim can get the vdproj functionality into the msi task.
Jeff
>
> --__--__--
>
> Message: 1
> Subject: RE: [Nant-users] vdproj and solution task in NAnt
> Date: Mon, 28 Mar 2005 08:13:43 -0500
> From: "Fo
If you ever get this error:
"An error occurred while parsing EntityName."
Check your .build file for a '&' literal that is not correctly escaped
out like this:
&
If you can't find one in your build file and you are using the
task, it might be inside a project file, as discussed here:
http://w
I have a VS 2003 solution that contains a C# project and a (setup)
vdproj. I'd like to use the solution task to build both projects in
the solution. I know that building vdproj projects isn't directly
supported.
I've noticed that there are a couple of possible routes build my
vdproj from NAnt, nam
I'm just starting with NANT and have a problem that appears on both
0.84 and 0.85-rc2. I've done a fair amount of googling and searching
the nant-users archive, but I don't have a solid answer yet.
So, in my csc task, I have a resources section:
that cranks through several files succ
