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 <solution> task might not be a good idea. When I convert the vdproj to the xml markup for the NAntContrib tasks, I expect that visual studio is installed on the box. This is because visual studio uses .wid files as merge modules representing the common dialogs to be used in an install. 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 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. Jim On Mon, 28 Mar 2005 15:58:44 -0500, Jeff Hoover <[EMAIL PROTECTED]> wrote: > 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: "Foster, Richard - PAL" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]>, > > <[email protected]> > > > > Jeff, > > > > I have used the exec to devenv option. It works well, but as you > > mentioned there are licensing issues. > > > > I have also tried the NantContrib MSI tasks, and MSI2XML. I would not > > now choose either of them, and I am in the process of converting the > > installation creation tasks to use WiX (see http://wix.sourceforge.net). > > > > Alas, apart from the Devenv option, you probably will have to throw away > > your initial setup project, however at least with WiX, you can decompile > > the MSI and/or MSM file(s) to use as a starting point. > > > > Hope this helps, > > Regards, > > Richard=20 > > > > > > Message: 2 > > Date: Mon, 28 Mar 2005 08:29:57 -0600 > > From: Jim Geurts <[EMAIL PROTECTED]> > > Reply-To: Jim Geurts <[EMAIL PROTECTED]> > > To: "Foster, Richard - PAL" <[EMAIL PROTECTED]> > > Subject: Re: [Nant-users] vdproj and solution task in NAnt > > Cc: [EMAIL PROTECTED], [email protected] > > > > Hey guys... > > > > I wrote the vdprojconverter project. It does not require WiX. I > > added "support" to convert vdproj files to wix syntax, along the way.=20 > > The original point of the converter was to convert to the NAntContrib > > msi/msm task xml. > > > > so... At this point, the NAntContrib msi/msm tasks now support > > everything that is possible (and more) from a vdproj. I'll look at > > updating that code base to fully support vdproj files and generate > > 100% valid xml. > > > > ------------------------------------------------------- > This SF.net email is sponsored by Demarc: > A global provider of Threat Management Solutions. > Download our HomeAdmin security software for free today! > http://www.demarc.com/Info/Sentarus/hamr30 > _______________________________________________ > Nant-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nant-users > ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/Info/Sentarus/hamr30 _______________________________________________ Nant-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-users
