Thanks for reply James,
Following is my .build file, It try to start VS.NET first time use install (not sure
for what reason),
I've CABARC.EXE and MSITaskTemplate.MSI in bin folder.
Am I missing something? Why it try to start VS.NET install?
----
<project name="testmsi" default="createmsi" description="test project">
<property name="nant.settings.currentframework" value="net-1.1"/>
<property name="nant.vsnet.dialog.dir" value="C:\Program Files\Microsoft Visual
Studio .NET 2003\Common7\Tools\Deployment\VsdDialogs" />
<target name="createmsi" >
<msi output="Setup1.msi"
sourcedir="C:\nant-0.84\examples\TestNantWinApp\WindowsApplication1\obj\Debug"
template="${nant.location}/MSITaskTemplate.msi">
<properties>
<property name="ProductCode" value="{04F505B2-D113-404C-AF6E-9837C0766F91}" />
<property name="PackageCode" value="{EAAB1E53-2BBD-451A-A56A-86BAA75619D5}" />
<property name="ProductLanguage" value="1033" />
<property name="ProductName" value="Setup1" />
<property name="UpgradeCode" value="{2665171F-A813-45D3-B814-094DC401D3AA}" />
<property name="ARPCONTACT" value="Default Company Name" />
<property name="Manufacturer" value="Default Company Name" />
<property name="ProductVersion" value="1.0.0" />
</properties>
<!--<directories/>-->
<components>
<component name="_E00B576168BE4A87B7607ACFDB93C1D1"
id="{29EFDB5B-EEB4-4521-B714-C4DF0BF42208}" attr="2" directory="TARGETDIR"
feature="DefaultFeature">
<key file="WindowsApplication1.exe" />
<fileset
basedir="C:\nant-0.84\examples\TestNantWinApp\WindowsApplication1\obj\Debug">
<include name="WindowsApplication1.exe" />
</fileset>
<forceid file="WindowsApplication1.exe" id="_1C8DE64E3A23479BBC181ED6C9B02896"
attr="512" checkinterop="false" />
</component>
</components>
<!--<launchconditions>
<launchcondition name=".NET Framework" condition="1">
<description>[VSDNETMSG]</description>
</launchcondition>
</launchconditions>-->
<features>
<feature name="DefaultFeature" title="DefaultFeature" display="1" typical="true" />
</features>
<mergemodules>
<merge feature="DefaultFeature">
<modules>
<includes name="${nant.vsnet.dialog.dir}/1033//VsdAdminFinishedDlg.wid" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdAdminProgressDlg.wid" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdFinishedDlg.wid" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdUserInterface.wim" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdWelcomeDlg.wid" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdConfirmDlg.wid" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdFolderDlg.wid" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdAdminWelcomeDlg.wid" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdAdminConfirmDlg.wid" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdAdminFolderDlg.wid" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdBasicDialogs.wim" />
<includes name="${nant.vsnet.dialog.dir}/1033//VsdProgressDlg.wid" />
</modules>
<configurationitems>
<configurationitem module="VsdAdminProgressDlg.wid" name="ShowProgress"
value="1" />
<configurationitem module="VsdFinishedDlg.wid" name="UpdateText" value="#1258"
/>
<configurationitem module="VsdWelcomeDlg.wid" name="Welcome" value="#1203" />
<configurationitem module="VsdWelcomeDlg.wid" name="CopyrightWarning"
value="#1202" />
<configurationitem module="VsdAdminWelcomeDlg.wid" name="Welcome"
value="#1203" />
<configurationitem module="VsdAdminWelcomeDlg.wid" name="CopyrightWarning"
value="#1202" />
<configurationitem module="VsdProgressDlg.wid" name="ShowProgress" value="1" />
</configurationitems>
</merge>
</mergemodules>
</msi>
</target>
</project>
-----Original Message-----
From: James Geurts [mailto:[EMAIL PROTECTED]
Sent: Friday, October 08, 2004 10:43 AM
To: Manish Jain
Cc: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [NAntC-Dev] VDProjConverter and MSI task
The alternative to using the wid and wim files (merge modules) is to hand
code the dialog information by yourself... I perosnally think that is a bit
tedious and would opt to just copy the wid and wim files to the build
machine. As far as the component structures that vdprojconvert creates...
it *should* create valid elements, but of course you can clean them up
(combine related components) to utilize NAnt's fileset support. Also, don't
expect any updates to the vcprojconverter project, as I wont be getting my
primary development machine until November sometime.
Jim
> Hi All,
>
> I would be interested to know if anybody is successfully using
> VDProjConverter to convert their .vdproj files to MSI taks I'm trying
> to use it but facing few issues, like it try to invoke VS.NET
> components so not sure script will work on build machine as well as do
> you using wid files for dialogs, is there any alternative to that? In
> that case i need to copy all wid files to build machine?
>
> Thanks
> Manish
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
> ITManagersJournal Use IT products in your business? Tell us what you
> think of them. Give us Your Opinions, Get Free ThinkGeek Gift
> Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> NAntContrib-Developer mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
NAntContrib-Developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
