Unfortunately that is not the case! Later on the Client will be run on multiple machines - that is the clue about this special installation method: The real Client binaries and other stuff is only installed on *one* physical machine. The real users do not have most stuff locally; they just refer to those files via a network folder.
I know about the CAS issues and that problem can be solved with granting rights. -----Ursprüngliche Nachricht----- Von: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Gesendet: Mittwoch, 29. August 2012 17:57 An: General discussion for Windows Installer XML toolset. Betreff: [Spam-Wahrscheinlichkeit=37]Re: [WiX-users] To regasm or to not regasm... If you are only wanting to register these DLL's for your own private usage within a single application, I'd strongly suggest using registration free COM and deploy them with the application. This allows the OS to load the info into the activation context at application start, and would allow you to have multiple folders with multiple versions without the need to invoke a setup/repair operation when switching between them. Regardless of if you register the DLL or use it in isolation, I seem to remember issues with .Net assemblies running on a network share being in a "sandboxed" zone where the CAS (prior to 4.0) would not allow the evil network binary to be able to do privileged operations without messing with the machine policy (granting full trust to our strong name). Jacob -----Original Message----- From: Christian Hausknecht [mailto:chauskne...@beracom.de] Sent: Wednesday, August 29, 2012 10:44 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] To regasm or to not regasm... Hello folks, me again :-D The next problem I must solve requires some experience that I do not have, so I hope I can get good advice as usual from here :) Base problem is quite easy: I need to register some DLLs during installation process. But my initial situation is like this: I do not install the DLLs on the local system! They are already located in a mounted net drive (is it called like this in the Windows-World?). The proper location can be different on every system, so one might have access to it like this "X:\foo\bar\bin\MyDLL.dll" some other might have a different drive name. So the path to the dll differs. My question is now: Is it possible to use ``heat`` to harvest the information *once* from the build-server and integrate them into my wix-project as usual? That is the way Rob mentioned here: http://stackoverflow.com/a/1397481 But is that an option for my situation? Is the path something that affects the registration? And is it possible just to keep some parts (e.g. TypeLib-Part?!?) from the heat-output, as I do not want to install the dll locally? So can I just "register" the dlls with wix or is there always an installation process on top? And if so, what "parts" do I need? If all else fails I think I just have to call ``regasm`` from a CustomAction - that should not be the problem to implement. But as Rob mentioned, it is perhaps not a good solution. So if it is possible to solve this with "plain" wix, I would definitely appreciate that. I hope it is understandable for you, sorry my English is not so good :( If something is still confusing or not sufficiently explained, please let me know. If not, please help me :) Best regards, Mit freundlichen Grüßen Christian Hausknecht Entwicklung BeraCom Beratung und Software-Entwicklung GmbH & Co. KG Weidestr. 134, 22083 Hamburg T: +49 (0)40 547 241 - DW F: +49 (0)40 547 241 - 60 M: chauskne...@beracom.de<mailto:chauskne...@beracom.de> http://www.beracom.de ============================================= Kommanditgesellschaft: Sitz Hamburg, RG Hamburg, HRA 90932 Persönlich haftende Gesellschafterin: BeraCom Beratung und Software-Entwicklung GmbH Sitz Hamburg, RG Hamburg, HRB 64844 Geschäftsführer: Arno Schaefer, Britta Kahlfuss Diese E-Mail ist vertraulich und exklusiv für den/die Adressaten bestimmt. Weiterleitung oder Kopieren, auch auszugsweise, darf nur mit ausdrücklicher schriftlicher Einwilligung des Absenders erfolgen. In jedem Fall ist sicherzustellen, dass keinerlei inhaltliche Veränderungen erfolgen. Der Absender ist von der Richtigkeit dieser Mail zum Zeitpunkt ihrer Erstellung überzeugt. Er und/oder sein Unternehmen übernimmt jedoch keine Haftung für ihre Richtigkeit. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
