Any Inputs on this . Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-Dynamically-Conditionally-Display-a-Wizard-in-Wix-Bootstapper-tp7595589p7595649.html
Sent from the wix-users mailing list archive at Nabble.com.
---
"Fortunately, I do not need reference count."
In that case, I wish you the best of luck.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Marek Mielcarek [mailto:
No, the Fed uses ancient IBM Mainframes. My service communicates directly with
them via routers owned and provided by the Fed. In nearly four years of
operation, the only glitches have been hardware failures of the routers
themselves.
All of IIS configuration settings for AppPools, Applicatio
I agree with the arguments on reference counting and upgrades. If you need
that, heat is better for sure. Fortunately, I do not need reference count. In
my case uninstalling is easy - just calling the regasm again. Today you can
grill anything based on security but we surely run into a paradox
I leave that to you. As usual you are right, but it slips by from my radar
because I can't do it any other way. The installer must be transactional or QA
testing of it becomes burdensome. Upgrade support is a given and won't work if
the installer isn't mostly transactional. Even more so for
You skipped the important stuff. Like rollback, upgrade, uninstall and
reference counting. Calling regasm will not help you solve any of the hard
problems around those situations. It'll be easy to get clean install running
but everything else is much harder.
At FireGiant, we always recommend us
Many executable utilities from Microsoft have known buffer overruns bugs in
their parameter passing. If the particular version of the executable is not
known before execution, there is no guarantee that it doesn't have one or more
of these flaws. In any case, signing of the MSI does not help y
John,
thank you for your comments. I find them very valuable. Please find below my
remarks.
RE 1: I am not sure how you define "code injections" in MSI. If you sign your
MSI with certificate, classic injections will not work.
RE 2: The remark on Trojan is as good for MSI as for any other situ
It is a very bad idea to use any external executable in an MSI because:
1) the MSI is now defenseless against code injection
2) defenseless against a Trojan
3) at the mercy of whatever version to version changes are made to the calling
interface of the executable
Any responsible security analysi
Phill,
Thank you for the hint. I am aware of using heat for registering COM however I
find calling regasm immensely easier and better way. If you have dedicated
resource with nothing on the neck but just playing with WiX, using heat is
probably fine. In my case WiX is just a very small fragment
Not really the question asked, but are you aware of using heat to harvest
regasm entries?
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-To-regasm-or-to-not-regasm-td7580188.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/cal
11 matches
Mail list logo
