[WiX-users] Install specific version of package by Burn
Hello! I need to install VC11 runtime, but specific version: 11.0.61030.0. I implement it in this way: It works perfect, but in some conditions I've got troubles. Suppose that older version on VC11 is already installed (11.0.50727.01). What happens in this case: * Burn detects that package IS installed (probably, product code of 11.0.61030.0 and 11.0.50727.01 is same) * Burn does NOT install 11.0.61030.0 since it is installed * My application refuses to install because VC11 is older than 11.0.61030.0. How to fix it? It wood be good to replace somehow old version of VC11 with package in bootstrapper, but how to do it? I found that I can install new VC11 if I do "repair" on it. But how to "repair" VC11 by Burn? -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Is it possible to customize compiled installer?
Hi All, I need to find (if possible) solution for following problem: Installer (WiX 3.5) of our product must be able to be customized AFTER compilation. This means that some data in installer (resource DLLs and product name on installer UI) will be changed after compilation. This is how it should work: - We compile installer (call it "base installer") - We do SOMETHING with base installer; as a result we have "customized installers": A, B, C etc. - Users install "customized installers" and have same product, but with different DLLs. What is the best way to achieve it? Possible ways: 1. Wrap "base installer" into some .exe file which will install product and perform customization (but how?) 2. Implement some tricky custom action which will replace some files on target machine. But I suppose installation will be broken because replaced files will NOT be correctly uninstalled. Why we need this feature: our customers distribute "customized installers", and they want to separate creation of installer itself and creation of specific "flavour" of installer. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to register OLE server?
Hello, all!
Please briefly explain me (or give me a link to documentation) how to
register OLE server in WiX? I tried to find this information, but I could
not find anything.
Our developers provided me a .reg file with data required in registry on
target machine:
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}]
@="IntelliCAD Drawing"
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\AuxUserType]
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\AuxUserType\2]
@="Drawing"
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\AuxUserType\3]
@="icad"
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\DefaultIcon]
@="E:\\Work\\INTELL~1.X\\Icad7.1\\Source\\INTELL~1\\make\\VC9\\Std\\Stage\\icad.exe,0"
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\InprocHandler32]
@="ole32.dll"
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\Insertable]
@=""
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\LocalServer32]
@="E:\\Work\\INTELL~1.X\\Icad7.1\\Source\\INTELL~1\\make\\VC9\\Std\\Stage\\icad.exe"
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\MiscStatus]
@="32"
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\ProgID]
@="Icad.Drawing"
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\Verb]
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\Verb\0]
@="&Edit,0,2"
[HKEY_CLASSES_ROOT\CLSID\{000D0E00---C000-0046}\Verb\1]
@="&Open,0,2"
I suppose it must be written in WiX with tags "TypeLib", "Class", "ProgId",
"ProgId". But how to?
P.S. I tries to harvest (with "heat.exe") required data from OLE-server
executable file (like I do it for COM). But "heat.exe" return file without
anything looking like class registration.
--
Cloud Computing - Latest Buzzword or a Glimpse of the Future?
This paper surveys cloud computing today: What are the benefits?
Why are businesses embracing it? What are its payoffs and pitfalls?
http://www.accelacomm.com/jaw/sdnl/114/51425149/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Register com objects
Use heat.exe tool to extract COM-related information. 2009/3/30 sandun css > Hi, > > Is there a way in WiX, to register a COM object, without using custom > actions? > > Thanks, > Sandun. > > -- > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] test (please do not reply)
test -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
