[WiX-users] How to handle restarts in burn required by dependencies? - Please
I just wanted to put this out there again as an unanswered question. I am sure there is a very busy person somewhere that knows the answer and I would be most grateful if they could share. I have two restart situations that do not work. 1) - On Windows 7, .NET framework requires a reboot. (Interestingly it does not on XP.) I must do that reboot, because I have managed code that is used later in the install sequence to check if one of the dependencies is installed. I have set the ExePackage/@Protocol to netfx4 as suggest by Rob in a response to someone else about restarts, but when say yes to the reboot question in the .net framework installer, Win 7 will not shut down because the Burn produced bootstrapper is preventing the shutdown. A cancel of the shutdown results in an Error in the bootstrapper. A manual reboot works at this point, but the bootstrapper does not auto restart. 2) - Installing Installer 4.5 on Windows XP. The installer requests a restart and somehow, the bootstrapper prevents it from running and restarts the install segment, which proceeds until SQL says, it cannot continue until the system restarts. Answering that restart as yes, forces an error back to the bootstrapper, but again does not restart the system. All chained ExePackage dependencies are marked as PerMachine=yes The PackageGroup for the .NET framework is below. PackageGroup Id=Netfx4Full ExePackage Id=Netfx4Full Protocol=netfx4 Cache=no Compressed=no PerMachine=yes Permanent=yes Vital=yes SourceFile=C:\EntireOne\Bootstrapper\Packages\DotNetFX40\dotNetFx40_Ful l_x86_x64.exe DownloadUrl=http://go.microsoft.com/fwlink/?LinkId=164193; DetectCondition=Netfx4FullVersion AND (NOT VersionNT64 OR Netfx4x64FullVersion) / /PackageGroup -- Roy Chastain -- 10 Tips for Better Server Consolidation Server virtualization is being driven by many needs. But none more important than the need to reduce IT complexity while improving strategic productivity. Learn More! http://www.accelacomm.com/jaw/sdnl/114/51507609/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to handle restarts in burn required by dependencies?
I have two restart situations that do not work. 1) - On Windows 7, .NET framework requires a reboot. (Interestingly it does not on XP.) I must do that reboot, because I have managed code that is used later in the install sequence to check if one of the dependencies is installed. I have set the ExePackage/@Protocol to netfx4 as suggest by Rob in a response to someone else about restarts, but when say yes to the reboot question in the .net framework installer, Win 7 will not shut down because the Burn produced bootstrapper is preventing the shutdown. A cancel of the shutdown results in an Error in the bootstrapper. A manual reboot works at this point, but the bootstrapper does not auto restart. 2) - Installing Installer 4.5 on Windows XP. The installer requests a restart and somehow, the bootstrapper prevents it from running and restarts the install segment, which proceeds until SQL says, it cannot continue until the system restarts. Answering that restart as yes, forces an error back to the bootstrapper, but again does not restart the system. All chained ExePackage dependencies are marked as PerMachine=yes The PackageGroup for the .NET framework is below. PackageGroup Id=Netfx4Full ExePackage Id=Netfx4Full Protocol=netfx4 Cache=no Compressed=no PerMachine=yes Permanent=yes Vital=yes SourceFile=C:\EntireOne\Bootstrapper\Packages\DotNetFX40\dotNetFx40_Ful l_x86_x64.exe DownloadUrl=http://go.microsoft.com/fwlink/?LinkId=164193; DetectCondition=Netfx4FullVersion AND (NOT VersionNT64 OR Netfx4x64FullVersion) / /PackageGroup -- Roy Chastain -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn, ManagedBootstrapperApplication, SQL and Custom Detection
I need to detect a specific version (2008 R2) and a specific instance of SQL Express as a dependency. According to some blog I found a few days ago, the correct way to do this type of detection is via WMI. As it turns out, the detection code in .NET if very simple and clean. My employer is adamant that we do not write this detection code in C++. Of course, we cannot use the MS provided bootstrapper to run the check if .NET Framework has not be installed. I even went so far as to create 2 bootstrappers and chain them together. Utter failure. Looks like 3 might do things correctly, but at this point, I am not sure. :-( This problem became an excuse to learn about ManagedBootstrapperApplicaions in Burn 3.6. I have spent the day uncovering the documentation in Burn etc., and think I have handle on this problem except for ONE BIG ISSUE. Is there a mechanism to employ a custom detection in the Burn ManagedBootstrapperApplication that would affect the install/no install status of an ExePackage? Of course if anyone wants to chime in on a reliable method of detecting a specific version and instance of SQL that does not require WMI, I am listening. Currently our rule is as follows. If there is no SQL installed install the instance or if there is a SQL 2008 R2 installed but not the correct instance, install the instance. The idea of mixing versions of SQL or forcing an upgrade on the user is being deferred till latter. -- Roy Chastain -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Action Doubts
As stated, Wix 3.5 does support IIS 7. Also, I see that you have the CA marked immediate. If it is running during the UI phase, it will fail because you must be elevated to talk to IIS 7 and the UI phase is not elevated unless you jump through hoops to start it that way. -- Roy Chastain -- FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Populating a ListBox At Runtime - VB.NET Custom Action
Matt: I just posted some code to do what you currently want to do. It also has code to do what you are wanting to do next. :-) I have just posted the custom action code (C# - not VB sorry). I also have dialogs and a complete WiX based UI to go with it, should you want to use it. This code checks for all the web sites that are available in IIS and populates a combo box with the information. Allows the user to select the site, the Virtual Directory name etc. The real trick that complicates the code is that the CA is only called if the current install is adding a feature that requires the web site. (Also, note that you must run the msi as elevated on Window Vista and up to enumerate the websites.) https://skydrive.live.com/?cid=6372e0958f1d1d72sc=documentsid=6372E095 8F1D1D72%21184# -- Roy Chastain -- uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Some help with WiXLib files with bound files - Internals Question
I have been trying to determine why my WiXlibs do not provide the files for the consuming project. I have been poking around in the WiXlibs and explored them some with the Library and WixEnumerateCab classes. I have discovered that the files in the cab within a library are named 0-n. I have not found how a file within a fragment with a full path name is translated in to 0-n file name to be found in the cab. Please, anyone with the knowledge of WiX internals, shed some light (no pun intended) on how the files in the Sections relate back to the files in the cab portion of the WixLib. -- Roy Chastain -- BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos much more. Register early save! http://p.sf.net/sfu/rim-blackberry-1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Lit and -bf option - What does it really do?
-dUnmanagedInterfaceNoCrypto.TargetName=KMSTransMC -dUnmanagedInterfaceNoCrypto.TargetPath=C:\KMS.Net2.0\KMSYSTransport\Rel ease\NoCrypto\KMSTransMC.dll -dUnmanagedInterfaceWithCrypto.Configuration=Release -dUnmanagedInterfaceWithCrypto.FullConfiguration=Release|Win32 -dUnmanagedInterfaceWithCrypto.Platform=Win32 -dUnmanagedInterfaceWithCrypto.ProjectDir=C:\KMS.Net2.0\KMSYSTransport\U nmanagedInterfaceWithCrypto\ -dUnmanagedInterfaceWithCrypto.ProjectExt=.vcxproj -dUnmanagedInterfaceWithCrypto.ProjectFileName=UnmanagedInterfaceWithCry pto.vcxproj -dUnmanagedInterfaceWithCrypto.ProjectName=UnmanagedInterfaceWithCrypto -dUnmanagedInterfaceWithCrypto.ProjectPath=C:\KMS.Net2.0\KMSYSTransport\ UnmanagedInterfaceWithCrypto\UnmanagedInterfaceWithCrypto.vcxproj -dUnmanagedInterfaceWithCrypto.TargetDir=C:\KMS.Net2.0\KMSYSTransport\Re lease\WithCrypto\ -dUnmanagedInterfaceWithCrypto.TargetExt=.dll -dUnmanagedInterfaceWithCrypto.TargetFileName=KMSTransMC.dll -dUnmanagedInterfaceWithCrypto.TargetName=KMSTransMC -dUnmanagedInterfaceWithCrypto.TargetPath=C:\KMS.Net2.0\KMSYSTransport\R elease\WithCrypto\KMSTransMC.dll -dManagedTransportNoCrypto.Configuration=Release -dManagedTransportNoCrypto.FullConfiguration=Release|AnyCPU -dManagedTransportNoCrypto.Platform=AnyCPU -dManagedTransportNoCrypto.ProjectDir=C:\KMS.Net2.0\KMSYSTransport\Manag edTransportNoCrypto\ -dManagedTransportNoCrypto.ProjectExt=.csproj -dManagedTransportNoCrypto.ProjectFileName=ManagedTransportNoCrypto.cspr oj -dManagedTransportNoCrypto.ProjectName=ManagedTransportNoCrypto -dManagedTransportNoCrypto.ProjectPath=C:\KMS.Net2.0\KMSYSTransport\Mana gedTransportNoCrypto\ManagedTransportNoCrypto.csproj -dManagedTransportNoCrypto.TargetDir=C:\KMS.Net2.0\KMSYSTransport\Manage dTransportNoCrypto\bin\release\ -dManagedTransportNoCrypto.TargetExt=.dll -dManagedTransportNoCrypto.TargetFileName=KMSYSTransportNoCrypto.dll -dManagedTransportNoCrypto.TargetName=KMSYSTransportNoCrypto -dManagedTransportNoCrypto.TargetPath=C:\KMS.Net2.0\KMSYSTransport\Manag edTransportNoCrypto\bin\release\KMSYSTransportNoCrypto.dll -dManagedTransportWithCrypto.Configuration=Release -dManagedTransportWithCrypto.FullConfiguration=Release|AnyCPU -dManagedTransportWithCrypto.Platform=AnyCPU -dManagedTransportWithCrypto.ProjectDir=C:\KMS.Net2.0\KMSYSTransport\Man agedTransportWithCrypto\ -dManagedTransportWithCrypto.ProjectExt=.csproj -dManagedTransportWithCrypto.ProjectFileName=ManagedTransportWithCrypto. csproj -dManagedTransportWithCrypto.ProjectName=ManagedTransportWithCrypto -dManagedTransportWithCrypto.ProjectPath=C:\KMS.Net2.0\KMSYSTransport\Ma nagedTransportWithCrypto\ManagedTransportWithCrypto.csproj -dManagedTransportWithCrypto.TargetDir=C:\KMS.Net2.0\KMSYSTransport\Mana gedTransportWithCrypto\bin\release\ -dManagedTransportWithCrypto.TargetExt=.dll -dManagedTransportWithCrypto.TargetFileName=KMSYSTransportWithCrypto.dll -dManagedTransportWithCrypto.TargetName=KMSYSTransportWithCrypto -dManagedTransportWithCrypto.TargetPath=C:\KMS.Net2.0\KMSYSTransport\Man agedTransportWithCrypto\bin\release\KMSYSTransportWithCrypto.dll -dETEMT272.Configuration=Release -dETEMT272.FullConfiguration=Release|Win32 -dETEMT272.Platform=Win32 -dETEMT272.ProjectDir=C:\KMS.Net2.0\KMSYSTransport\ETEMT27\ -dETEMT272.ProjectExt=.vcxproj -dETEMT272.ProjectFileName=ETEMT272.vcxproj -dETEMT272.ProjectName=ETEMT272 -dETEMT272.ProjectPath=C:\KMS.Net2.0\KMSYSTransport\ETEMT27\ETEMT272.vcx proj -dETEMT272.TargetDir=C:\KMS.Net2.0\KMSYSTransport\ETEMT27\Release\ -dETEMT272.TargetExt=.dll -dETEMT272.TargetFileName=ETEMT272.dll -dETEMT272.TargetName=ETEMT272 -dETEMT272.TargetPath=C:\KMS.Net2.0\KMSYSTransport\ETEMT27\Release\ETEMT 272.dll -out obj\Release\ -arch x86 -ext C:\Program Files (x86)\Windows Installer XML v3.5\bin\\WixUIExtension.dll -ext C:\Program Files (x86)\Windows Installer XML v3.5\bin\\WixNetFxExtension.dll KMSYSTransportLib.wxs 3 Microsoft (R) Windows Installer Xml Compiler version 3.5.2519.0 3 Copyright (C) Microsoft Corporation. All rights reserved. 3 KMSYSTransportLib.wxs 3 C:\Program Files (x86)\Windows Installer XML v3.5\bin\lit.exe -out C:\KMS.Net2.0\KMSYSTransport\Release\WixLibKMSYSTransport.wixlib -bf -ext C:\Program Files (x86)\Windows Installer XML v3.5\bin\\WixUIExtension.dll -ext C:\Program Files (x86)\Windows Installer XML v3.5\bin\\WixNetFxExtension.dll obj\Release\KMSYSTransportLib.wixobj ..\..\CoreLibrary\bin\release\WixLibMSVC_90_30729.5570-Private.wixlib 3 Microsoft (R) Windows Installer Xml Library Tool version 3.5.2519.0 3 Copyright (C) Microsoft Corporation. All rights reserved. == Build: 3 succeeded, 0 failed, 5 up-to-date, 0 skipped == -- Roy Chastain -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask
[WiX-users] Is there a WiXlib viewer/decompiler?
Did I miss the info in the documentation about there being any program that could view/list/extract the contents of a WiXlib? In particular exactly what files (timestamp etc) that are bound into it. I realize that a lot of the file is just XML, but looking at the information in VS or NotePad is somewhat challenging. -- Roy Chastain -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Lit and -bf option - What does it really do?
I had, apparently foolishly, assumed that the -bf option placed the binary files into the WiXlib. My assumption was supported by the fact that with the option the lib was about the size of the compressed content and without the -bf, it was very small. I further assumed that I could then take that lib file to another system and use it as input into a WiX build. However, I have discovered that all the files that are bound into the lib need to be present at the same path on the other system. So, what is the real purpose of the -bf option and is there no way to build reusable libraries that are not dependent on the input binaries? -- Roy Chastain -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Lit and -bf option - What does it really do?
I am getting the message The system cannot file the file 'file name with full path' with type 'WixFile'. The line number of the error points to the source .wxs of the library project. Any file missing from the path given when the library was built results in that message, but I only get one such message per build. My final .msi build has 3 libs referenced and this occurs with all three. I have checked the output of the build of the lib and Lit is called with the -bf as expected. One of the WiXObj file is 32KB and the corresponding WiXLib is 958KB. So, it is including the binaries, but does not use them at reference time. Is there a media statement or such that I might me missing for the lib build? This is happening with both 3.5 release and current build of 3.6. VS 2010 SP1 Windows Vista SP2 x64 -- Roy Chastain -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] What is the purpose of the auto start that is created when Wix is installed?
I think the title says it all. Thanks -- Roy Chastain -- Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using a localization file in a WiXlib
I created some new dialogs and created a .wxl for my new strings. I have these dialogs in a WiXLib with the XXX_en-us.wxl included in the project. The library project is marked to Bind files into library. I build the library without a language specification. When I use the WiXLib, I specify the language of en-us. My questions are about the following. 1) - Why must I include the XXX_en-us.wxl in the project that references this WiXLib? 2) - Why must I specify a language in the project that references this WiXLib, when I do not have to specify a language to use the built-in dialogs? In other words, there is more to localization than I understand. -- Roy Chastain -- Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Manifest for Burn Bootstrapper
The goal is very much that a Bootstrapper Application is never elevated. Rob, I would very much like for you to rethink that goal. Granted BAs should not write to the system, but there are some compelling reasons for allowing the BA to run elevated. 1) - Allows a user without elevation privileges to bother someone with them one time and one time only at the very beginning of the process 2) - IIS as you said is a mess. I have a Custom Action in my MSI that needs to read IIS configuration to present info to the user. Therefore my .MSI must run elevated during the UI phase. Since the user will never get it right to run the .MSI elevated, the answer became imbed the .MSI in a BA that forced the elevation via a manifest. Do not ship the .MSI separately because again the user will try to run it instead of the .exe 3) - I am sure that more than just IIS is going to be causing problems with .MSIs and/or BAs needing to run elevated. Please consider this as you respond to the feature suggestion about elevating the BA. I believe that a simple switch to create the BA with an elevated vs. as invoker manifest is a reasonable answer. Currently we can do this by a custom build event step to add our own manifest to the BA after it is built, but that just become more complicated and is subject to failure if you add/change things in Burn's manifest. -- Roy Chastain -- 5 Ways to Improve Secure Unified Communications Unified Communications promises greater efficiencies for business. UC can improve internal communications as well as offer faster, more efficient ways to interact with customers and streamline customer service. Learn more! http://www.accelacomm.com/jaw/sfnl/114/51426253/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Should Burn download an exe package that is not needed
The WixStdba currently prompts before downloading from internet. That was very useful for testing some cases but the default is planned to change to just do it... smile/ The point of the question was that it asked AND DOWNLOADED an exe that was not used. (Did not need to be installed.) Should it do that? As far as asking is concerned, that is not necessarily a bad idea. It should become an optional setting. -- Roy Chastain -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn using an old copy of an embedded msi
Hmm, sounds like Burn did not fully rollback the Bundle when your MSI failed. In that case, you might want to uninstall the previous Bundle before trying the new one. Also, the Burn log file should show you (during Detect) whether a package was already cached or not. Yes, the log indicates that it is cached. Should it be? Do I need to file a bug about files remaining cached when the install errors? To further expand on the topic of the Burn application being installed and cached files. I am confused about the following scenario. Without Burn, I would create a new MSI with a new product code and release that to my customers. That would run and take care of upgrading to the new version of the product. How does that work with Burn and cached files? Since (at least in the erring case) Burn does not seem to realize that my embedded (attached container) file is new, it runs the old one. Currently I have the InstallCondition for the .MSI set to 1 to always force it to run regardless of whether Burn thinks it is installed or not. I guess another way to ask the question is, what would make Burn realize that a file, msi, exe etc - not just an embedded one - is actually different from the one that is cached? The Package @Compress and @Cache attributes are completely independent. Understood, but again, intuitively. attached containers should not be cached as a default. Since my file was cached and I did not specify, I assume the default for Cache is Yes. -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] What is the usage of Name and SourceFIle on
Well, the peanut gallery is back. Wow, no faith from the peanut gallery. If the file is signed (something else we calculate during build when referencing the file) we will use the signature of the file not the hash. If the signature on the file changed in between the point that you built and the user downloaded the actual file, chances are the user has a file you don't want them installing. smile/ I understand your reasoning and even agree with it for the most part; however, I just checked my Bootstrapper directory and indeed there is not a file for the DotNet 3.5SP1 or Client installs (amongst others). I do see that the product.xml file has PublicKey listed for each PackageFile. That seems to be MUCH desirable to having to have a local copy of the file on the system that builds the BA. As you think about this issue, please consider that it would be beyond wonderful if WiX could use the same input (to define a file and its download) that the GenerateBootstrapper action uses so that we do not have to reinvent the wheel every time MS releases a new package. -- Roy Chastain -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Options button in Burn application
Is there a way to remove the Options button in the resulting bootstrapper without using WixStandandardBootstrapperApplication.Foundation and completely theming the install? If so, how? If not, is there ANY documentation (beyond the schema reference) on the theming process etc? If not, is my best bet attempting to learn from the example by using HyperlinkTheme.xml RTFTheme.xml? -- Roy Chastain -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to have Burn start an MSI with User Interface enabled?
I have a simple Burn bundle with a prerequisite exe package and the target msi package. When it runs, the MSI package appears to be running in silent mode. (The install log has the following content - Client-side and UI is none or basic: Running entire install on the server.) How do I make the MSI display its normal UI? -- Roy Chastain -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Should Burn download an exe package that is not needed
I have a simple Burn bundle with a prerequisite exe package and a single msi. The exe package is for dotNetFx35Setup.exe with a download link to http://go.microsoft.com/fwlink/?linkid=118076 and compressed=no. The framework is already installed and the Burn log indicates that it was detected. However, Burn asked if I would like it to download the package and it did do a download. Is that correct behavior? -- Roy Chastain -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Questions about the Burn bootstrapper installing itself
I was testing a bootstrapper package this afternoon and when I happened to look at the Add/Remove programs, I found about 8 copies of the bootstrapper installed. What was more surprising was that I could run uninstall on each one. This seems like very strange behavior. This implies that the bootstrapper is creating its own MSI with a unique product code and upgrade code each time it is built. Is that the case? Is that changeable? In each case my actual MSI failed to install and the prerequisites did not install because they were not needed, so Burn should have been a giant no-op. I also noticed that something keeps track of the prerequisites downloaded files. They were only asked about the first time. Once I removed all copies of the installed bootstrapper, it again asked about the downloads of the prerequisites. Given that the prerequisites are required and cannot be uninstalled, I have marked them as vital=yes and permanent=yes. I put them and the MSI in the same chain and marked it as DisableRollback=yes. Is there some way that I can author this package so that, if my MSI fails, the bootstrapper application itself would not be installed. I am trying to understand the big picture with Burn, but I am struggling. -- Roy Chastain -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn using an old copy of an embedded msi
I have a Burn package with a MSI that is marked as Compressed=yes. The Cache attribute was left off the MsiPackage element. I run that copy of Burn and my MSI failed to install (due to errors in the MSI). The bootstrapper application shows as installed. I rebuild the Burn package with a new MSI file (same product and upgrade code, but different contents). I then run the newly created Burn package, without removing the previous one, it attempts to run the older cached MSI file. Is this designed and expected behavior? If so, what do I do to make it attempt to run the NEW MSI that is embedded in the Burn package? Is setting cache=no sufficient? I remember seeing a discussion on all the effects of cache yes/no, but I cannot find it again. PS. Intuitively, embedded files should not be cached in the sense that an old one is run when a new Burn application is run. After all, we have already downloaded it so we should use it. Granted this view might be opposition to some orthogonal thought process that says that cache=yes should be consistent irrespective of compress=yes/no. -- Roy Chastain -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What is the purpose of the MbaNetfxPackageId and MbaPreqPackageName variables
We would never do something as silly as REQUIRE a native application to install the .NET Framework just to use the WiX toolset's bootstrapper, Burn. Well, I did not think so, but the first response through me off. The answer told me it was use by Burn and that I was off the beaten path. Imagine my surprise at that when all I wanted to do was install a prereq for may application. There is some problem here with the nomenclature. MBA?? I now (think I) know it stands for Managed Burn A?? I don't have a clue what the A is for. I realize that all of this uses the BAL extension, but again, do idea. The last BAL I knew was IBM assembler :-) -- Roy Chastain -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] What is the usage of Name and SrouceFIle on the xxxPackage statement?
I am trying to author a bundle that has .NET 3.5 SP1 as a requirement. I found the fragment used in the WiX install for .NET 4.0 and changed the (appropriate) pieces. I removed the SourceFile and added a Name attribute. I ASSUMED that SourceFile meant that it would find the file on the local system and embed in the output. Given that there is a DownloadUrl specified, that behavior does not make too much sense. My final goal is to have a package that will download standard Microsoft packages from the Microsoft website and have my msi embedded in the .exe created by Wix. Well, anyway, with just the Name I receive a Light 103 error telling me that it cannot find file 'SourceDir\DorNetFx35setup.exe'. Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Bundle Name=Bootstrapper1 Version=1.0.0.0 Manufacturer=Bootstrapper1 UpgradeCode=1befc64e-be9a-4238-b8b6-7e2357cffa91 BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.HyperlinkLicense / Chain DisableRollback=yes ParallelCache=yes PackageGroupRef Id=Netfx3.5SP1Full/ PackageGroupRef Id=Bundle.Generated.Packages/ /Chain /Bundle Fragment Variable Name=MbaNetfxPackageId Value=Netfx35Full / Variable Name=MbaPreqPackageName Value=.Net Framework 3.5 / util:RegistrySearch Root=HKLM Key=Software\Microsoft\NET Framework Setup\NDP\v3.5 Value=Version Variable=Netfx35SP1FullVersion / util:RegistrySearch Root=HKLM Key=SOFTWARE\Microsoft\Net Framework Setup\NDP\v3.5 Value=Version Variable=Netfx35SP1x64FullVersion Win64=yes / PackageGroup Id=Netfx3.5SP1Full ExePackage Id=Netfx3.5SP1Full Cache=no Compressed=no PerMachine=yes Permanent=yes Vital=yes DownloadUrl=http://go.microsoft.com/fwlink/?linkid=118076; Name=dotNetFx35setup.exe InstallCommand=/lang:enu /passive /norestart DetectCondition=Netfx35SP1FullVersion AND (NOT VersionNT64 OR Netfx35SP1x64FullVersion) / /PackageGroup /Fragment /Wix -- Roy Chastain -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] What is the purpose of the MbaNetfxPackageId and MbaPreqPackageName variables
The fragment to install .NET Framework 4.0 used in the WiX install has the following Variable Name=MbaNetfxPackageId Value=Netfx4Full / Variable Name=MbaPreqPackageName Value=.Net Framework 4.0 / What are the purposes of these two variables and is this something that needs to be emulated when authoring an install with a prereq of .NET 3.5 SP1? -- Roy Chastain -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What is the usage of Name and SrouceFIle on the
Light uses the source file to get information about the file to put into the manifest (e.g., file size, hash); if specified, it also uses it to embed, but that's optional. So you are telling me that I must have a local copy of any of the Microsoft install packages that I wish to have downloaded at install time. The implication is that should MS change the package between when I build the bootstrapper and when the customer runs it, the process will fail because the HASH code etc will be different. If the above is correct, are we sure this is the right path? I cannot say for sure, but I would not expect that behavior from the MS supplied SETUP.exe bootstrapper. -- Roy Chastain -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What is the purpose of the MbaNetfxPackageId and MbaPreqPackageName variables
They're used by the Burn managed bootstrapper app to manage installing .NET. They're still needed but note that the current managed BA has only supported (tested/validated) .NET 4, not 3.5. At the moment, you're in uncharted waters. Are you trying to tell me that the Burn bootstrapper REQUIRES .NET 4.0 to run? I am only wanting to install 3.5SP1 for my application, not for extension etc for Burn. -- Roy Chastain -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error message Cannot convert RelativePathinto Registry elements.
Okay, removing the attribute removed the error. Is that a bug? I seems
that no should mean no. 3.5 has the same behavior?
Since I am not using the Advertise attribute, does the RelativePath
attribute have any meaning?
Is the lack of relative path support a WIX issue or an installer issue?
I am trying to get all the registry entries that are created by RegAsm
created with as few manual entries as possible. I have to add the AppId
etc because I am also registering the COM object for elevation.
--
Roy Chastain
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, November 09, 2009 21:28
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Error message Cannot convert RelativePathinto
Registry elements.
Looking at the 3.0 RTM help chm, here is what I see:
Try removing RelativePath attribute entirely from the Class element.
-Original Message-
From: Roy Chastain [mailto:r...@roychastain.org]
Sent: Monday, November 09, 2009 12:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Error message Cannot convert RelativePath into
Registry elements.
I have the following XML
Component Id=COMDllComponent
Guid=FE540942-A911-4bc3-851C-1A810122011E
File Id=COMDll Name=$(var.COMDll.TargetFileName)
Source=$(var.COMDll.TargetPath)
Assembly=.net AssemblyApplication=COMUser
AssemblyManifest=COMDll
DiskId=1 KeyPath=yes /
AppId Id={2415C722-C6DC-4a7c-80DA-447EA126BD4D} Advertise=no
Description=Test COM Dll
Class Id={34224BB0-7F1C-4b88-9D1A-F06A4C9A396F} Advertise=no
Context=InprocServer32
Description=Test COM Dll ForeignServer=mscoree.dll
RelativePath=no
ThreadingModel=both Version=1.0/
/AppId
/Component
Candle indicates the error is on the Class statement. I have tried
this with Class as a descendent of File and as a descendent of AppId
(as shown). Same error message in both cases.
What does this error message really mean?
--
Roy Chastain
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day trial. Simplify your report design, integration and deployment -
and focus on what you do best, core application coding. Discover what's
new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day trial. Simplify your report design, integration and deployment -
and focus on what you do best, core application coding. Discover what's
new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Use of DllSurrogate on the AppId statement
I am not an expert at using any of the bug stuff, but I went to the tracker, put DllSurrogate into the box and click search. No results. That leads me to believe it was not a reported bug. Did I miss a step? -- Roy Chastain -Original Message- From: Blair [mailto:os...@live.com] Sent: Monday, November 09, 2009 21:16 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Use of DllSurrogate on the AppId statement I don't know, but it may have been one of those bugs that was punted for 3.0 and fixed in 3.5. You could search the bugs to see if there was a workaround listed for 3.0 (which is one reason it may have been punted, assuming it was filed against 3.0), or you could use 3.5. The core toolset for 3.5 is undergoing not much more than bug fixes as the active feature development work for 3.5 is concentrated on burn. -Original Message- From: Roy Chastain [mailto:r...@roychastain.org] Sent: Monday, November 09, 2009 12:55 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Use of DllSurrogate on the AppId statement Version 3.0 (final version) will not allow DllSurrogate= on the AppId. It says that if I want an empty string to remove the attribute. Current build of 3.5 will allow DllSurrogate=. If the attribute is removed, there is no entry in the Registry table for the DllSurrogate value and that is not the same as it being the empty string. I am not an expert on COM but, I believe that I really need the DLLSurrogate value in the registry. Any comments? -- Roy Chastain -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Use of DllSurrogate on the AppId statement
Version 3.0 (final version) will not allow DllSurrogate= on the AppId. It says that if I want an empty string to remove the attribute. Current build of 3.5 will allow DllSurrogate=. If the attribute is removed, there is no entry in the Registry table for the DllSurrogate value and that is not the same as it being the empty string. I am not an expert on COM but, I believe that I really need the DLLSurrogate value in the registry. Any comments? -- Roy Chastain -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Error message Cannot convert RelativePath into Registry elements.
I have the following XML
Component Id=COMDllComponent
Guid=FE540942-A911-4bc3-851C-1A810122011E
File Id=COMDll Name=$(var.COMDll.TargetFileName)
Source=$(var.COMDll.TargetPath)
Assembly=.net AssemblyApplication=COMUser
AssemblyManifest=COMDll
DiskId=1 KeyPath=yes /
AppId Id={2415C722-C6DC-4a7c-80DA-447EA126BD4D} Advertise=no
Description=Test COM Dll
Class Id={34224BB0-7F1C-4b88-9D1A-F06A4C9A396F} Advertise=no
Context=InprocServer32
Description=Test COM Dll ForeignServer=mscoree.dll
RelativePath=no
ThreadingModel=both Version=1.0/
/AppId
/Component
Candle indicates the error is on the Class statement. I have tried
this with Class as a descendent of File and as a descendent of AppId
(as shown). Same error message in both cases.
What does this error message really mean?
--
Roy Chastain
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Please explain - ran your entire MSI elevated
Rob Mensching just made the reply below and I don't want to hi-jack that
conversation, but I would like an explanation of that that statement.
Do we have control over what part of the install is elevated and if so,
how?
--
Roy Chastain
-Original Message-
From: Rob Mensching [mailto:r...@wixtoolset.org]
Sent: Friday, September 11, 2009 06:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] C# Custom Action,change some files during
installation
That will only work if the target file is not in a per-machine directory
or you ran your entire MSI elevated (icky, icky, icky).
Adr!an Serafin wrote:
Hi!
Thank's for the response :) I need my own CA for some other things to
;) Besides I found solution. If anyone needs it:
Custom Action=EditConfig After=InstallFinalize
Overridable=no/Custom
where After=InstallFinalize is the key ;)
Adrian
2009/9/11 John Nannenga john.nanne...@microsoft.com
You likely don't need your own CA for this, check out XmlConfig or
XmlFile.
Your problem here is likely that you get a FileNotFoundException or
something similar which is due to the fact you have your CA scheduled
to execute in the immediate sequence and scheduled after
InstallFiles which doesn't put any files onto the machine until the
deferred sequence.
From: Adrian Serafin [abus...@gmail.com]
Sent: Thursday, September 10, 2009 9:10 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] C# Custom Action, change some files during
installation
Hi!
I'm struggling with this for some time now... I'm trying to make my
custom action to modify applications config.exe file but no success.
Maybe someone can help??
CustomAction
Id=EditConfig
BinaryKey=EditConfigDLL
DllEntry=EditCPConfig
Execute=immediate
Return=ignore /
Binary Id=EditConfigDLL SourceFile=ConfigEditCA.CA.dll /
InstallExecuteSequence Custom Action=EditConfig
After=InstallFiles Overridable=no/Custom
/InstallExecuteSequence
And here is c# code:
public static ActionResult EditCPAConfig(Session session)
{
string db_user = session[DB_USER];
string db_password = session[DB_PASSWORD];
string u_profile = localSU;
string installdir = session[INSTALLDIR];
System.Xml.XmlDocument xml_doc = new
System.Xml.XmlDocument();
System.Diagnostics.Debugger.Launch();
xml_doc.Load(installdir +
Cairo.Producer.Admin.exe.config);
System.Diagnostics.Debugger.Launch();
System.Xml.XmlElement conf_elem = xml_doc.DocumentElement;
System.Xml.XmlElement conn_string =
(System.Xml.XmlElement)conf_elem.FirstChild;
System.Xml.XmlElement add_conn =
xml_doc.CreateElement(add);
add_conn.SetAttribute(name, u_profile);
add_conn.SetAttribute(connectionString, something);
add_conn.SetAttribute(providerName, Npgsql);
conn_string.AppendChild(add_conn);
xml_doc.Save(installdir + Cairo.Producer.exe.config);
System.Diagnostics.Debugger.Launch();
return ActionResult.Success;
}
Code works when i put files in installfolder on my computer...
--
View this message in context:
http://n2.nabble.com/C-Custom-Action-change-some-files-during-install
ation-tp3617476p3617476.html Sent from the wix-users mailing list
archive at Nabble.com.
-
- Let Crystal Reports handle the reporting - Free Crystal
Reports 2008 30-Day trial. Simplify your report design, integration
and deployment - and focus on what you do best, core application
coding. Discover what's new with Crystal Reports now.
http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
- Let Crystal Reports handle the reporting - Free Crystal
Reports 2008 30-Day trial. Simplify your report design, integration
and deployment - and focus on what you do best, core application
coding. Discover what's new with Crystal Reports now.
http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Let Crystal Reports handle the reporting - Free Crystal
Reports 2008 30-Day trial. Simplify your report design, integration
and deployment - and focus on what you do best, core application
coding. Discover what's new with Crystal
Re: [WiX-users] installing an application as a pure x86 app on Vista 64.
I really does not matter what the install is doing. If you have compiled your main program as an AnyCPU and any DLL in the chain is 32-bit only, then the application will not run on a x64 system. This is because the AnyCPU code is jited into x64 on a 64 bit machine and a x64 application cannot load a 32-bit DLL. You must compile at least the main program as x86. All of the managed (CLR) DLLs will then be loaded and jited as 32-bit and then the application can load the 32-bit only DLLs. -- Roy Chastain -Original Message- From: dvo...@icrcompany.com [mailto:dvo...@icrcompany.com] Sent: Wednesday, September 09, 2009 20:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] installing an application as a pure x86 app on Vista 64. Why would the .NET binaries try to load any 32-bit dependent Dlls during installation? As far as I was aware the installer was just copying those Dlls to the proper locations. I'll try installing via command line. Hopefully that will actually produce some sort of error message. Dan I've seen this when it's not an installer issue, it's because the .NET binaries are AnyCpu and consequently run as native 64-bit and can't load 32-bit dependent Dlls. When this happens during the install custom actions fail etc. You didn't see any kind of error message when the install failed? Anyway, installing with a command line to produce a log might help. Msiexec /I path to msi /l*v path to a log file Phil Wilson -Original Message- From: Dan Vogel [mailto:dvo...@icrcompany.com] Sent: Wednesday, September 09, 2009 4:25 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] installing an application as a pure x86 app on Vista 64. When I run the installer on a 32-bit machine everything works fine. When I run the installer on a 64-bit it prematurely ends due to some unspecified error. I need the application to be a purely x86 application. The app is written in C# and WPF and so should run fine as 64-bit. However, several dll dependencies are 32-bit. What sort of flags or settings do I need to use to get the installer to work properly in a 64-bit environment, but install the application as purely x86? Are there some sort of logs that are created when the installer fails that will let me know why it is prematurely ending? Thanks, -- *Dan Vogel* Software Engineer iCRco - The Innovative CR Company P) 310-921-9559 F) 310-542-7236 dvo...@icrcompany.com mailto:dvo...@icrcompany.com http://www.icrcompany.com iCRco logo This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users
Re: [WiX-users] installing an application as a pure x86 app on Vista 64.
No, you did not misstate your question, but the point was that the application will not run (based on what you said earlier) and I believe that a working application is easier to install than a non-working one. This is especially true if you have an managed custom actions etc, that would cause application code to be run during the installation. As I see your other response indicates a driver issue, then this it was not the case of mismatched application code, but it could have been. To solve your driver issue, you will need the x64 bit drivers and (I think) a separate install setup for the x64 bit machines that reference them instead of the x86 drivers. While it might be possible to include them in a 8x6 setup I do not believe that it is. -- Roy Chastain -Original Message- From: dvo...@icrcompany.com [mailto:dvo...@icrcompany.com] Sent: Thursday, September 10, 2009 12:42 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] installing an application as a pure x86 app on Vista 64. Clearly I've stated my question wrong. My problem right now is with the intsaller. My installer works fine on 32 bit machines, but when I try to use it on a 64 bit machine running Vista 64 it fails. My main app and all it's Dlls are compiled as x86. I really does not matter what the install is doing. If you have compiled your main program as an AnyCPU and any DLL in the chain is 32-bit only, then the application will not run on a x64 system. This is because the AnyCPU code is jited into x64 on a 64 bit machine and a x64 application cannot load a 32-bit DLL. You must compile at least the main program as x86. All of the managed (CLR) DLLs will then be loaded and jited as 32-bit and then the application can load the 32-bit only DLLs. -- Roy Chastain -Original Message- From: dvo...@icrcompany.com [mailto:dvo...@icrcompany.com] Sent: Wednesday, September 09, 2009 20:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] installing an application as a pure x86 app on Vista 64. Why would the .NET binaries try to load any 32-bit dependent Dlls during installation? As far as I was aware the installer was just copying those Dlls to the proper locations. I'll try installing via command line. Hopefully that will actually produce some sort of error message. Dan I've seen this when it's not an installer issue, it's because the .NET binaries are AnyCpu and consequently run as native 64-bit and can't load 32-bit dependent Dlls. When this happens during the install custom actions fail etc. You didn't see any kind of error message when the install failed? Anyway, installing with a command line to produce a log might help. Msiexec /I path to msi /l*v path to a log file Phil Wilson -Original Message- From: Dan Vogel [mailto:dvo...@icrcompany.com] Sent: Wednesday, September 09, 2009 4:25 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] installing an application as a pure x86 app on Vista 64. When I run the installer on a 32-bit machine everything works fine. When I run the installer on a 64-bit it prematurely ends due to some unspecified error. I need the application to be a purely x86 application. The app is written in C# and WPF and so should run fine as 64-bit. However, several dll dependencies are 32-bit. What sort of flags or settings do I need to use to get the installer to work properly in a 64-bit environment, but install the application as purely x86? Are there some sort of logs that are created when the installer fails that will let me know why it is prematurely ending? Thanks, -- *Dan Vogel* Software Engineer iCRco - The Innovative CR Company P) 310-921-9559 F) 310-542-7236 dvo...@icrcompany.com mailto:dvo...@icrcompany.com http://www.icrcompany.com iCRco logo This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. - - Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - - Let Crystal
[WiX-users] How to install/register a managed (clr) com object
I am using Wix 3.0 release. I have a managed dll that has a class exposed to com. The normal registration process for this dll is Regasm /codebase /tlb dllname.dll AND if on a x64 bit system Regasm64 /codebase /tlb dllname.dll This works when the dll is not in the GAC. If the dll is placed in the GAC, then /codebase is removed from both calls. I have tested and I cannot activate the object without the typelib being registered also (/tlb option). I have seen people discussing a custom action calling regasm and I have seen discussion about using ComPlusAssembly. I saw a post by Rob (response to http://stackoverflow.com/questions/373436/how-do-i-install-a-net-dll-int o-a-com-application-using-msi-wix) that indicated (at least at one time) that there was an issue in the custom action created by the ComPlusExtension in which it only did the 32 bit registration. The link (marked update) at the top of the post to a closed bug (http://sourceforge.net/tracker/?func=detailaid=1914217group_id=105970 atid=642714) seems to indicate that x64 registration still does not work. The bug references a dll built for x64, but in my case it is probably even harder to get right because the dll with the com object is built for AnyCPU, which is what allows my two calls to regasm(64) to work correctly and allows my object to be activated from both 32 bit and 64 bit code. What is the BEST way to get the equivalent of the two calls to regasm(64) done? If it is to use the ComPlusAssembly as a child of the Component with Assembly=.net so that the dll is placed into the GAC, where should the type lib file be placed? One would think it should go into the GAC, but how do I get it there? Thanks -- Roy -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to install/register a managed (clr) com object
Thanks, but will that register both in the 64 and 32 bit registry?
Also, I am using the [ComRegisterFunctionAttribute()] declaration on a
method in the class.
Do you know if you method will honor the call to the decelerated method.
I do not know exactly who looks at this and calls the associated method,
but my guess is that I have to go through either REGASM or a DLL that it
calls.
--
Roy Chastain
-Original Message-
From: Jaspreet Nabha [mailto:jaspreet.na...@headstrong.com]
Sent: Wednesday, September 09, 2009 09:22
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to install/register a managed (clr) com
object
Roy,
Try below code. It should work This will take care of REGASM.
File Id=fil_abc.dll Source=\abc.dll
TypeLib Id='{54EEBB27-9602-4172-8081-6C19A0ADFFB2}'
MinorVersion='0' Language='1033'/TypeLib /File
You can use Assembly=.net, if you want it to be GACed also
Thanks
Jaspreet Singh
From: Roy Chastain [...@roychastain.org]
Sent: Wednesday, September 09, 2009 6:34 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to install/register a managed (clr) com object
I am using Wix 3.0 release.
I have a managed dll that has a class exposed to com. The normal
registration process for this dll is Regasm /codebase /tlb dllname.dll
AND if on a x64 bit system
Regasm64 /codebase /tlb dllname.dll
This works when the dll is not in the GAC. If the dll is placed in the
GAC, then /codebase is removed from both calls. I have tested and I
cannot activate the object without the typelib being registered also
(/tlb option).
I have seen people discussing a custom action calling regasm and I have
seen discussion about using ComPlusAssembly. I saw a post by Rob
(response to
http://stackoverflow.com/questions/373436/how-do-i-install-a-net-dll-int
o-a-com-application-using-msi-wix) that indicated (at least at one time)
that there was an issue in the custom action created by the
ComPlusExtension in which it only did the 32 bit registration. The link
(marked update) at the top of the post to a closed bug
(http://sourceforge.net/tracker/?func=detailaid=1914217group_id=105970
atid=642714) seems to indicate that x64 registration still does not
work. The bug references a dll built for x64, but in my case it is
probably even harder to get right because the dll with the com object is
built for AnyCPU, which is what allows my two calls to regasm(64) to
work correctly and allows my object to be activated from both 32 bit and
64 bit code.
What is the BEST way to get the equivalent of the two calls to
regasm(64) done? If it is to use the ComPlusAssembly as a child of the
Component with Assembly=.net so that the dll is placed into the GAC,
where should the type lib file be placed? One would think it should go
into the GAC, but how do I get it there?
Thanks
--
Roy
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day trial. Simplify your report design, integration and deployment -
and focus on what you do best, core application coding. Discover what's
new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
***The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material. Any review,retransmission,dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer.***
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008
30-Day trial. Simplify your report design, integration and deployment -
and focus on what you do best, core application coding. Discover what's
new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
[WiX-users] Installing a managed (clr) com object
I am using Wix 3.0 release. I have a managed dll that has a class exposed to com. The normal registration process for this dll is Regasm /codebase /tlb dllname.dll AND if on a x64 bit system Regasm64 /codebase /tlb dllname.dll This works when the dll is not in the GAC. If the dll is placed in the GAC, then /codebase is removed from both calls. I have tested and I cannot activate the object without the typelib being registered also (/tlb option). I have seen people discussing a custom action calling regasm and I have seen discussion about using ComPlusAssembly. I saw a post by Rob (response to http://stackoverflow.com/questions/373436/how-do-i-install-a-net-dll-int o-a-com-application-using-msi-wix) that indicated (at least at one time) that there was an issue in the custom action created by the ComPlusExtension in which it only did the 32 bit registration. The link (marked update) at the top of the post to a closed bug (http://sourceforge.net/tracker/?func=detailaid=1914217group_id=105970 atid=642714) seems to indicate that x64 registration still does not work. The bug references a dll built for x64, but in my case it is probably even harder to get right because the dll with the com object is built for AnyCPU, which is what allows my two calls to regasm(64) to work correctly and allows my object to be activated from both 32 bit and 64 bit code. What is the BEST way to get the equivalent of the two calls to regasm(64) done? If it is to use the ComPlusAssembly as a child of the Component with Assembly=.net so that the dll is placed into the GAC, where should the type lib file be placed? One would think it should go into the GAC, but how do I get it there? Thanks -- Roy -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
