What about adding it first with "assumes VS.NET installed" and then
fixing it with checked-in modules. If you did that, maybe make
not process vdproj files by default, but require an extra
parameter to turn it on, so as not to break for users who
have vdproj files on servers that don't have VS.NE
I was just thinking that we could craft our own merge modules which
mimic what the vs.net wid files do.
It would probably make sense to have the NAntContrib build script
build these. That would keep the source distribution size down a
little. A minor problem is discovering where these generated
rrent solutions which also contains setup projects.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Geurts
Sent: Thursday, March 31, 2005 6:14 AM
To: Gert Driesen
Cc: nant-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: Re: [Nant-users] RE: RE: vdpro
Jim Geurts wrote:
...
I suppose the user could specify where the wid files are located, via
a parameter on the solution task. Either that or we could create
similar merge modules that represent the dialogs from the vs.net
install. Those merge modules could be checked into NAntContrib and
then a V
I was thinking about this as I started working on the VDProjConverter
program again... btw, the link to download it
(http://software.biasecurities.com/Software/VDProjConverter/VDProjConverter.zip)
is working again.
I'm starting to think that integrating this into the task
might not be a good idea
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