Re: [WiX-users] Beginning Question
You're doing it too late indeed. During msbuild (BeforeCompile?) grasp the build version and write it to a (new?) wxs file. Then add that wxs file to your Compile itemgroup to get it compiled (and linked) to an msi. Although wix and msbuild/nant follow a declarative style of getting things done, this doesn't mean they understand each other. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 10:10 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Beginning Question Well I think how it works is the version number is stored somewhere so we need to check it out to modify it, and then check it back in so it becomes part of the install. Is there an AfterCompile attribute instead of InstallFiles? Maybe I'm doing that too late. Or is it just not possible to do these things with wix and I have to do them with MSBuild or Nant Brian Poploskie wrote: It looks like you have some Nant tags in there. I'm not really sure what you're trying to do. Unless you're doing a TFS checkout/checkin as part of your install I'm confused by what you're trying to do. You're describing things that happen at install time, not at build time, in your WiX files. To build use MSBuild or Nant or the build tool of your choice. I'd suggest starting the tutorial at the beginning and going all the way through. The tags you have in there aren't valid children in the WiX Schema. You're missing the dllentry parameter in your CustomActions required to do the type 1 custom action and execute a method from a DLL. The ID in your Binary is just an identifier. Brian Poploskie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 3:34 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Beginning Question Looked at the tutorial and reworked some of the code. I'm still not sure what to do with the Import Project, or if I even need it but here's what I have now. Binary Id=MSBuild.Community.Tasks.AssemblyInfo SourceFile=MSBuild.Community.Tasks.dll / Binary Id=MSBuild.Community.Tasks.Math.Add SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=MSBuild.Community.Tasks.Zip SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=Sedodream.MSBuild.Tasks.GetAssemblyVersion SourceFile=Sedodream.MSBuild.Tasks.dll/ CustomAction Id=UpdateAssembly BinaryKey=Sedodream.MSBuild.Tasks.GetAssemblyVersion Return=ignore / CustomAction Id=AddRevision BinaryKey=MSBuild.Community.Tasks.Math.Add Return=ignore / CustomAction Id=Assemble BinaryKey=MSBuild.Community.Tasks.AssemblyInfo Return=ignore / InstallExecuteSequence Custom Action=UpdateAssembly After=InstallFiles GetAssemblyVersion AssemblyPath=$(OutDir)\ChannelBox.exe Output TaskParameter=Major PropertyName=Major / Output TaskParameter=Minor PropertyName=Minor / Output TaskParameter=Build PropertyName=Build / Output TaskParameter=Revision PropertyName=CurrentRevision / /GetAssemblyVersion /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=AddRevision After=UpdateAssembly Add Numbers=$(CurrentRevision);1 Output TaskParameter=Result PropertyName=NewRevision / /Add Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkout $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=Assmeble After=AddRevision AssemblyInfo AssemblyCompany=company AssemblyCopyright=Copyright AssemblyFileVersion=$(Major).$(Minor).$(Build).$(NewRevision) AssemblyProduct=product AssemblyTitle=title AssemblyVersion=$(Major).$(Minor).$(Build).$(NewRevision) CodeLanguage=CSharp OutputFile=$(AssemblyInfoFilePath) / Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkin /comment:quot;Auto-Build: Version Updatequot; /noprompt /override:quot;Auto-Build:Version Updatequot; $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12022732 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com
[WiX-users] Beginning Question
That link should help you : http://weblogs.asp.net/bradleyb/archive/2005/12/02/432150.aspx Regards Matthieu 2007/8/7, Schrieken, Rene [EMAIL PROTECTED]: You're doing it too late indeed. During msbuild (BeforeCompile?) grasp the build version and write it to a (new?) wxs file. Then add that wxs file to your Compile itemgroup to get it compiled (and linked) to an msi. Although wix and msbuild/nant follow a declarative style of getting things done, this doesn't mean they understand each other. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 10:10 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Beginning Question Well I think how it works is the version number is stored somewhere so we need to check it out to modify it, and then check it back in so it becomes part of the install. Is there an AfterCompile attribute instead of InstallFiles? Maybe I'm doing that too late. Or is it just not possible to do these things with wix and I have to do them with MSBuild or Nant Brian Poploskie wrote: It looks like you have some Nant tags in there. I'm not really sure what you're trying to do. Unless you're doing a TFS checkout/checkin as part of your install I'm confused by what you're trying to do. You're describing things that happen at install time, not at build time, in your WiX files. To build use MSBuild or Nant or the build tool of your choice. I'd suggest starting the tutorial at the beginning and going all the way through. The tags you have in there aren't valid children in the WiX Schema. You're missing the dllentry parameter in your CustomActions required to do the type 1 custom action and execute a method from a DLL. The ID in your Binary is just an identifier. Brian Poploskie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 3:34 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Beginning Question Looked at the tutorial and reworked some of the code. I'm still not sure what to do with the Import Project, or if I even need it but here's what I have now. Binary Id=MSBuild.Community.Tasks.AssemblyInfo SourceFile=MSBuild.Community.Tasks.dll / Binary Id=MSBuild.Community.Tasks.Math.Add SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=MSBuild.Community.Tasks.Zip SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=Sedodream.MSBuild.Tasks.GetAssemblyVersion SourceFile=Sedodream.MSBuild.Tasks.dll/ CustomAction Id=UpdateAssembly BinaryKey=Sedodream.MSBuild.Tasks.GetAssemblyVersion Return=ignore / CustomAction Id=AddRevision BinaryKey=MSBuild.Community.Tasks.Math.Add Return=ignore / CustomAction Id=Assemble BinaryKey=MSBuild.Community.Tasks.AssemblyInfo Return=ignore / InstallExecuteSequence Custom Action=UpdateAssembly After=InstallFiles GetAssemblyVersion AssemblyPath=$(OutDir)\ChannelBox.exe Output TaskParameter=Major PropertyName=Major / Output TaskParameter=Minor PropertyName=Minor / Output TaskParameter=Build PropertyName=Build / Output TaskParameter=Revision PropertyName=CurrentRevision / /GetAssemblyVersion /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=AddRevision After=UpdateAssembly Add Numbers=$(CurrentRevision);1 Output TaskParameter=Result PropertyName=NewRevision / /Add Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkout $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=Assmeble After=AddRevision AssemblyInfo AssemblyCompany=company AssemblyCopyright=Copyright AssemblyFileVersion=$(Major).$(Minor).$(Build).$(NewRevision) AssemblyProduct=product AssemblyTitle=title AssemblyVersion=$(Major).$(Minor).$(Build).$(NewRevision) CodeLanguage=CSharp OutputFile=$(AssemblyInfoFilePath) / Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkin /comment:quot;Auto-Build: Version Updatequot; /noprompt /override:quot;Auto-Build:Version Updatequot; $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12022732 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still
Re: [WiX-users] Beginning Question
You're doing it too late indeed. During msbuild (BeforeCompile?) grasp the build version and write it to a (new?) wxs file. Then add that wxs file to your Compile itemgroup to get it compiled (and linked) to an msi. An easier way is to create a custom MSBuild task to get the version number and pass it in as a pre-processor variable: Target Name=BeforeBuild MyGetVersionTask Output TaskParameter=Version PropertyName=MyVersion / /MyGetVersionTask CreateProperty Value=Version=$(MyVersion);$(DefineConstants) Output TaskParameter=Value PropertyName=DefineConstants / /CreateProperty /Target This will pass in your version into candle as a pre-processor variable, which you can access with $(var.Version). Regards, John - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Beginning Question
Thanks all, I was a little confused I was thinking that Wix and MSBuild did basically the same thing and you could use one or the other. Sorry Bob Arnson-6 wrote: jcafaro10 wrote: Well I think how it works is the version number is stored somewhere so we need to check it out to modify it, and then check it back in so it becomes part of the install. Is there an AfterCompile attribute instead of InstallFiles? Maybe I'm doing that too late. Or is it just not possible to do these things with wix and I have to do them with MSBuild or Nant Custom actions are for install time behavior. You want compile-time behavior, so yes, your build scripts are the right place. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12034462 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Beginning Question
In our MSBuild proj we have several UsingTask lines that link to some assemblies. I'd like to use some of this functionality in my Wix Installer but unfortunately, copying all of the UsingTask lines didn't work because UsingTask isn't a child of something or other. Any way to get this to work? -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12019080 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Beginning Question
If I understand the question correctly you want to call some methods within assemblies during installation? If that's the case you'll want to take a look at the CustomAction tag for a type 1 custom action. To schedule CustomActions after you've created them use the InstallExecuteSequence tag and Custom tags underneath that. The after and before params point to a step in the sequence. So you could have a custom action that came After=InstallFiles or Before=StartServices. Brian Poploskie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 12:06 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Beginning Question In our MSBuild proj we have several UsingTask lines that link to some assemblies. I'd like to use some of this functionality in my Wix Installer but unfortunately, copying all of the UsingTask lines didn't work because UsingTask isn't a child of something or other. Any way to get this to work? -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12019080 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Beginning Question
Well here's what I have right but still not quite sure about several things. What is the wix equivalent of the UsingTask line so it knows to look in those dll's? In MSBuild: UsingTask TaskName=MSBuild.Community.Tasks.AssemblyInfo AssemblyFile=MSBuild.Community.Tasks.dll / UsingTask TaskName=MSBuild.Community.Tasks.Math.Add AssemblyFile=MSBuild.Community.Tasks.dll/ UsingTask TaskName=MSBuild.Community.Tasks.Zip AssemblyFile=MSBuild.Community.Tasks.dll/ UsingTask TaskName=Sedodream.MSBuild.Tasks.GetAssemblyVersion AssemblyFile=Sedodream.MSBuild.Tasks.dll/ So far in Wix: CustomAction Id=UpdateAssmebly FileKey=not sure what to put here Return=ignore / InstallExecuteSequence Custom Action=UpdateAssmebly After=InstallFiles GetAssemblyVersion AssemblyPath=path to exe Output TaskParameter=Major PropertyName=Major / Output TaskParameter=Minor PropertyName=Minor / Output TaskParameter=Build PropertyName=Build / Output TaskParameter=Revision PropertyName=CurrentRevision / /GetAssemblyVersion !-- Bump up revision number -- Add Numbers=$(CurrentRevision);1 Output TaskParameter=Result PropertyName=NewRevision / /Add !-- Checkout AssemblyInfo file in preparation for version increment -- Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkout $(AssemblyInfoFilePath) / !-- Generate new AssemblyInfo file with new version -- AssemblyInfo AssemblyCompany=company AssemblyCopyright=Copyright AssemblyFileVersion=$(Major).$(Minor).$(Build).$(NewRevision) AssemblyProduct=product AssemblyTitle=title AssemblyVersion=$(Major).$(Minor).$(Build).$(NewRevision) CodeLanguage=CSharp OutputFile=$(AssemblyInfoFilePath) / !-- Checkin AssemblyInfo file to preserve version increment -- Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkin /comment:quot;Auto-Build: Version Updatequot; /noprompt /override:quot;Auto-Build:Version Updatequot; $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence Brian Poploskie wrote: If I understand the question correctly you want to call some methods within assemblies during installation? If that's the case you'll want to take a look at the CustomAction tag for a type 1 custom action. To schedule CustomActions after you've created them use the InstallExecuteSequence tag and Custom tags underneath that. The after and before params point to a step in the sequence. So you could have a custom action that came After=InstallFiles or Before=StartServices. Brian Poploskie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 12:06 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Beginning Question In our MSBuild proj we have several UsingTask lines that link to some assemblies. I'd like to use some of this functionality in my Wix Installer but unfortunately, copying all of the UsingTask lines didn't work because UsingTask isn't a child of something or other. Any way to get this to work? -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12019080 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12021902 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com
Re: [WiX-users] Beginning Question
Here's a quick example of how you would use a foo.dll method called foobar. Binary Id=FooDll SourceFile=.\foo.dll / CustomAction Id=DoFooAction BinaryKey=FooDll DllEntry=foobar InstallExecuteSequence Custom Action=DoFooAction After=InstallFiles/ /InstallExecuteSequence http://www.tramontana.co.hu/wix/ That tutorial is a very good place to start messing around with WiX. http://www.tramontana.co.hu/wix/lesson3.php#3.3 That section in particular deals with custom actions using dlls. Brian Poploskie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 2:40 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Beginning Question Well here's what I have right but still not quite sure about several things. What is the wix equivalent of the UsingTask line so it knows to look in those dll's? In MSBuild: UsingTask TaskName=MSBuild.Community.Tasks.AssemblyInfo AssemblyFile=MSBuild.Community.Tasks.dll / UsingTask TaskName=MSBuild.Community.Tasks.Math.Add AssemblyFile=MSBuild.Community.Tasks.dll/ UsingTask TaskName=MSBuild.Community.Tasks.Zip AssemblyFile=MSBuild.Community.Tasks.dll/ UsingTask TaskName=Sedodream.MSBuild.Tasks.GetAssemblyVersion AssemblyFile=Sedodream.MSBuild.Tasks.dll/ So far in Wix: CustomAction Id=UpdateAssmebly FileKey=not sure what to put here Return=ignore / InstallExecuteSequence Custom Action=UpdateAssmebly After=InstallFiles GetAssemblyVersion AssemblyPath=path to exe Output TaskParameter=Major PropertyName=Major / Output TaskParameter=Minor PropertyName=Minor / Output TaskParameter=Build PropertyName=Build / Output TaskParameter=Revision PropertyName=CurrentRevision / /GetAssemblyVersion !-- Bump up revision number -- Add Numbers=$(CurrentRevision);1 Output TaskParameter=Result PropertyName=NewRevision / /Add !-- Checkout AssemblyInfo file in preparation for version increment -- Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkout $(AssemblyInfoFilePath) / !-- Generate new AssemblyInfo file with new version -- AssemblyInfo AssemblyCompany=company AssemblyCopyright=Copyright AssemblyFileVersion=$(Major).$(Minor).$(Build).$(NewRevision) AssemblyProduct=product AssemblyTitle=title AssemblyVersion=$(Major).$(Minor).$(Build).$(NewRevision) CodeLanguage=CSharp OutputFile=$(AssemblyInfoFilePath) / !-- Checkin AssemblyInfo file to preserve version increment -- Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkin /comment:quot;Auto-Build: Version Updatequot; /noprompt /override:quot;Auto-Build:Version Updatequot; $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence Brian Poploskie wrote: If I understand the question correctly you want to call some methods within assemblies during installation? If that's the case you'll want to take a look at the CustomAction tag for a type 1 custom action. To schedule CustomActions after you've created them use the InstallExecuteSequence tag and Custom tags underneath that. The after and before params point to a step in the sequence. So you could have a custom action that came After=InstallFiles or Before=StartServices. Brian Poploskie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 12:06 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Beginning Question In our MSBuild proj we have several UsingTask lines that link to some assemblies. I'd like to use some of this functionality in my Wix Installer but unfortunately, copying all of the UsingTask lines didn't work because UsingTask isn't a child of something or other. Any way to get this to work? -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12019080 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX
Re: [WiX-users] Beginning Question
Looked at the tutorial and reworked some of the code. I'm still not sure what to do with the Import Project, or if I even need it but here's what I have now. Binary Id=MSBuild.Community.Tasks.AssemblyInfo SourceFile=MSBuild.Community.Tasks.dll / Binary Id=MSBuild.Community.Tasks.Math.Add SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=MSBuild.Community.Tasks.Zip SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=Sedodream.MSBuild.Tasks.GetAssemblyVersion SourceFile=Sedodream.MSBuild.Tasks.dll/ CustomAction Id=UpdateAssembly BinaryKey=Sedodream.MSBuild.Tasks.GetAssemblyVersion Return=ignore / CustomAction Id=AddRevision BinaryKey=MSBuild.Community.Tasks.Math.Add Return=ignore / CustomAction Id=Assemble BinaryKey=MSBuild.Community.Tasks.AssemblyInfo Return=ignore / InstallExecuteSequence Custom Action=UpdateAssembly After=InstallFiles GetAssemblyVersion AssemblyPath=$(OutDir)\ChannelBox.exe Output TaskParameter=Major PropertyName=Major / Output TaskParameter=Minor PropertyName=Minor / Output TaskParameter=Build PropertyName=Build / Output TaskParameter=Revision PropertyName=CurrentRevision / /GetAssemblyVersion /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=AddRevision After=UpdateAssembly Add Numbers=$(CurrentRevision);1 Output TaskParameter=Result PropertyName=NewRevision / /Add Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkout $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=Assmeble After=AddRevision AssemblyInfo AssemblyCompany=company AssemblyCopyright=Copyright AssemblyFileVersion=$(Major).$(Minor).$(Build).$(NewRevision) AssemblyProduct=product AssemblyTitle=title AssemblyVersion=$(Major).$(Minor).$(Build).$(NewRevision) CodeLanguage=CSharp OutputFile=$(AssemblyInfoFilePath) / Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkin /comment:quot;Auto-Build: Version Updatequot; /noprompt /override:quot;Auto-Build:Version Updatequot; $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12022732 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Beginning Question
It looks like you have some Nant tags in there. I'm not really sure what you're trying to do. Unless you're doing a TFS checkout/checkin as part of your install I'm confused by what you're trying to do. You're describing things that happen at install time, not at build time, in your WiX files. To build use MSBuild or Nant or the build tool of your choice. I'd suggest starting the tutorial at the beginning and going all the way through. The tags you have in there aren't valid children in the WiX Schema. You're missing the dllentry parameter in your CustomActions required to do the type 1 custom action and execute a method from a DLL. The ID in your Binary is just an identifier. Brian Poploskie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 3:34 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Beginning Question Looked at the tutorial and reworked some of the code. I'm still not sure what to do with the Import Project, or if I even need it but here's what I have now. Binary Id=MSBuild.Community.Tasks.AssemblyInfo SourceFile=MSBuild.Community.Tasks.dll / Binary Id=MSBuild.Community.Tasks.Math.Add SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=MSBuild.Community.Tasks.Zip SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=Sedodream.MSBuild.Tasks.GetAssemblyVersion SourceFile=Sedodream.MSBuild.Tasks.dll/ CustomAction Id=UpdateAssembly BinaryKey=Sedodream.MSBuild.Tasks.GetAssemblyVersion Return=ignore / CustomAction Id=AddRevision BinaryKey=MSBuild.Community.Tasks.Math.Add Return=ignore / CustomAction Id=Assemble BinaryKey=MSBuild.Community.Tasks.AssemblyInfo Return=ignore / InstallExecuteSequence Custom Action=UpdateAssembly After=InstallFiles GetAssemblyVersion AssemblyPath=$(OutDir)\ChannelBox.exe Output TaskParameter=Major PropertyName=Major / Output TaskParameter=Minor PropertyName=Minor / Output TaskParameter=Build PropertyName=Build / Output TaskParameter=Revision PropertyName=CurrentRevision / /GetAssemblyVersion /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=AddRevision After=UpdateAssembly Add Numbers=$(CurrentRevision);1 Output TaskParameter=Result PropertyName=NewRevision / /Add Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkout $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=Assmeble After=AddRevision AssemblyInfo AssemblyCompany=company AssemblyCopyright=Copyright AssemblyFileVersion=$(Major).$(Minor).$(Build).$(NewRevision) AssemblyProduct=product AssemblyTitle=title AssemblyVersion=$(Major).$(Minor).$(Build).$(NewRevision) CodeLanguage=CSharp OutputFile=$(AssemblyInfoFilePath) / Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkin /comment:quot;Auto-Build: Version Updatequot; /noprompt /override:quot;Auto-Build:Version Updatequot; $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12022732 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Beginning Question
Well I think how it works is the version number is stored somewhere so we need to check it out to modify it, and then check it back in so it becomes part of the install. Is there an AfterCompile attribute instead of InstallFiles? Maybe I'm doing that too late. Or is it just not possible to do these things with wix and I have to do them with MSBuild or Nant Brian Poploskie wrote: It looks like you have some Nant tags in there. I'm not really sure what you're trying to do. Unless you're doing a TFS checkout/checkin as part of your install I'm confused by what you're trying to do. You're describing things that happen at install time, not at build time, in your WiX files. To build use MSBuild or Nant or the build tool of your choice. I'd suggest starting the tutorial at the beginning and going all the way through. The tags you have in there aren't valid children in the WiX Schema. You're missing the dllentry parameter in your CustomActions required to do the type 1 custom action and execute a method from a DLL. The ID in your Binary is just an identifier. Brian Poploskie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jcafaro10 Sent: Monday, August 06, 2007 3:34 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Beginning Question Looked at the tutorial and reworked some of the code. I'm still not sure what to do with the Import Project, or if I even need it but here's what I have now. Binary Id=MSBuild.Community.Tasks.AssemblyInfo SourceFile=MSBuild.Community.Tasks.dll / Binary Id=MSBuild.Community.Tasks.Math.Add SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=MSBuild.Community.Tasks.Zip SourceFile=MSBuild.Community.Tasks.dll/ Binary Id=Sedodream.MSBuild.Tasks.GetAssemblyVersion SourceFile=Sedodream.MSBuild.Tasks.dll/ CustomAction Id=UpdateAssembly BinaryKey=Sedodream.MSBuild.Tasks.GetAssemblyVersion Return=ignore / CustomAction Id=AddRevision BinaryKey=MSBuild.Community.Tasks.Math.Add Return=ignore / CustomAction Id=Assemble BinaryKey=MSBuild.Community.Tasks.AssemblyInfo Return=ignore / InstallExecuteSequence Custom Action=UpdateAssembly After=InstallFiles GetAssemblyVersion AssemblyPath=$(OutDir)\ChannelBox.exe Output TaskParameter=Major PropertyName=Major / Output TaskParameter=Minor PropertyName=Minor / Output TaskParameter=Build PropertyName=Build / Output TaskParameter=Revision PropertyName=CurrentRevision / /GetAssemblyVersion /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=AddRevision After=UpdateAssembly Add Numbers=$(CurrentRevision);1 Output TaskParameter=Result PropertyName=NewRevision / /Add Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkout $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence InstallExecuteSequence Custom Action=Assmeble After=AddRevision AssemblyInfo AssemblyCompany=company AssemblyCopyright=Copyright AssemblyFileVersion=$(Major).$(Minor).$(Build).$(NewRevision) AssemblyProduct=product AssemblyTitle=title AssemblyVersion=$(Major).$(Minor).$(Build).$(NewRevision) CodeLanguage=CSharp OutputFile=$(AssemblyInfoFilePath) / Exec Command=quot;$(TeamBuildRefPath)\..\tf.exequot; checkin /comment:quot;Auto-Build: Version Updatequot; /noprompt /override:quot;Auto-Build:Version Updatequot; $(AssemblyInfoFilePath) / /Custom /InstallExecuteSequence -- View this message in context: http://www.nabble.com/Beginning-Question-tf4225049.html#a12022732 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https
Re: [WiX-users] Beginning Question
jcafaro10 wrote: Well I think how it works is the version number is stored somewhere so we need to check it out to modify it, and then check it back in so it becomes part of the install. Is there an AfterCompile attribute instead of InstallFiles? Maybe I'm doing that too late. Or is it just not possible to do these things with wix and I have to do them with MSBuild or Nant Custom actions are for install time behavior. You want compile-time behavior, so yes, your build scripts are the right place. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
