Thank you for this link but there is nothing that explains how to sign MSI from VisualStudio. All I can see is that I need to run MsBuild script but that is as good (or as bad) as trying to invoke signing utility in postbuild event. Not something that can be considered native to WiX.
Thank you anyway Marek -----Original Message----- From: Carter Young [mailto:ecyo...@grandecom.net] Sent: Wednesday, April 09, 2014 11:29 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] path to framework SDK $(FrameworkSDKDir) See: http://stackoverflow.com/questions/20381525/wix-digitally-sign-bootstrapper-project Carter Quoting Marek Mielcarek <mmielca...@actuate.com>: > Thank you for all the answers. The thing I try to do is signing MSI > after it is fully cooked by WiX. To do so, I have a post-build event > that uses signtool utility which seats in $(FrameworkSDKDir) folder. > > I understand and respect all the remarks about "WiX is not .net". > However, in my humble opinion, not recognizing/supporting the fact > that Visual Studio is first and foremost used for .net development is > kind of self-denial. Interestingly, couple posts ago Phill Hogland > said that $(FrameworkSDKDir) works in WiX toolset 3.8, so maybe it is > supported in the end ? > > > Anyway, provided that using .net utility inside Visual Studio WiX > project is bad practice, here is the question: > > What is the best way to sign MSI with a certificate ? is there a using > WiX/native solution for that ? > > Thank you > > Marek > > > > > > > > > > -----Original Message----- > From: Carter Young [mailto:ecyo...@grandecom.net] > Sent: Tuesday, April 08, 2014 4:55 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] path to framework SDK $(FrameworkSDKDir) > > To add to this: > > The only time the .NET Frameworks are ever targeted in a WiX Project > is usually 1 of 2 reasons: > 1. An install condition is Tested to ensure the target machine has the > Required Version installed for your application. > 2. If not installed, the Burn Bootstrap Engine will install it before > installing your application. > > If you need post install work done using a tool in the Framework, you > need to use a Custom Action. When the custom action occurs the > version of the SDK is a moot point, because you tested for an install > condition and installed the proper framework, using one of the two > methods above, therefore you are guaranteed to have the proper > runtime. If the tool you need is part of the runtime, this method > will work. If the tool is part of the SDK, then I must echo Michael's > reply. > > Carter > > Quoting Michael Turner <mcturner...@gmail.com>: > >> I'm not sure what you are expecting $(FrameworkSDKDir) to point to in >> a .wixproj. Which version of the framework? There is no clear >> answer to this question within the context of a WiX project, because >> WiX projects do not target .NET Framework versions and do not use the >> .NET Framework SDK. >> Rather, they use the WiX toolset. >> >> If you are looking for a .NET Framework SDK path, I would recommend >> looking in a project type that uses the .NET Framework, such as a C# >> project. >> >> Also, if you are trying to use a tool from the $(FrameworkSDKDir) >> path on the output of a WiX project, you are probably on the wrong >> track, because the output of a WiX project will be either a Windows >> Installer database (.msi or .msm) or a WiX library (.wixlib), not a >> .NET assembly. Perhaps your post-build event would make more sense >> elsewhere? >> >> Regards, >> Mike >> >> >> > > > > ---------------------------------------------------------------------- > -------- > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration Continuously > Automate Build, Test & Deployment Start a new project now. Try Jenkins > in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ---------------------------------------------------------------------- > -------- > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration Continuously > Automate Build, Test & Deployment Start a new project now. Try Jenkins > in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
