I've got an installer for a utility that includes a COM+ component. The
solution was originally created in VS2008 and targetted .NET 3.5. The
solution was 'upgraded' to VS2010 and .NET 4.0, and now the installation
fails ...
Here's a fragment for COM+ component & TLB [this was working fine until
I've got an installer for a utility that includes a COM+ component. The
solution was originally created in VS2008 and targetted .NET 3.5. The
solution was 'upgraded' to VS2010 and .NET 4.0, and now the installation
fails ...
Here's a fragment for COM+ component & TLB [this was working fine until
Any suggestions for a workaround ... ?
I need to get this working in 2 installers ...
Thanks in advance,
-dmm
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ComPlus-Problem-Was-working-now-not-working-2nd-Attempt-at-Posting-tp6162048p6169486.htm
I've built a custom UI based on WixUI_Mondo [WiX v3.5.2519.0] ... following
the pattern outlined in the WiX Tutorial
[http://www.tramontana.co.hu/wix/index.php] and by Neil Sleightholm
[http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html]
... but I'm experiencing some weirdness
Just like the subject line says ...
We've got a couple of dozen installers that build with a variety of versions
of WiX [haven't had time to update all of them to v3.7] ... and we're moving
all of our packaging builds to TFSBuild from a variety of methods [older
TFSBuild scripts, batch files, etc.
Just found it, thanks!
-dmm
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Use-WiX-with-TFSBuild-without-installing-WiX-on-buildmachine-tp7583184p7583199.html
Sent from the wix-users mailing list archive at Nabble.com.
-
Like the subject line says ...
I'm using WiX v3.7.1224.0 to build an installation package for an app that
has a COM+ service
application ... I've tried to use the COM+ custom actions and have had
nothing but failures, this
installer & app were working until the app was updated to use .NET v4 - I
Hi Rob -
Your 'nothing' is probably more than my nothing on this topic, so thanks in
advance for any assistance and insight you can provide.
Here's the relevant log segment:
**
ComPlusInstallExecuteCommit: Entering ComPlusInstallExecuteCommit in
C:\WINDOWS\Installer\MSI29.tmp, version 3
Yes, Neil ... RegSvcs works fine for either version of the DLL, installs fine
... uninstalls fine ...
Weird, eh?
I'm going to take a look at the ComPlus extension code to see if I can find
any obvious
reason why it's not working ... not familiar territory, but I may as well
give it a shot ...
Th
Christopher Painter-2 wrote
> If that's the case, a DTF custom action wouldn't have that problem.
Thanks for the tip ...
I've never done anything with DTF, do you have any suggestions on how to get
started ?
Thanks again for your time and attention,
-dmm
--
View this message in context:
h
Christopher Painter-2 wrote
> http://blog.torresdal.net/2008/10/24/wix-and-dtf-using-a-custom-action-to-list-available-web-sites-on-iis/
Thanks!
I'll check this out ...
-dmm
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/COM-registration-help-
Neil Sleightholm wrote
> I'll see if I can make a simple repro first and try and come up with some
> ideas.
>
>
> dmm - can you raise a defect so this is not lost?
Thanks Neil!
I believe there are already a couple of bug reports / fix requests for this
but I will double-check and enter one if m
How are folks here documenting their installation packages ?
Are there any automated tools for doing this ... ?
If you're doing this manually, what information are you
capturing ... and how are you presenting it ? [charts /
spreadsheet type table(s) / ???]
I'm working on this issue ... and ther
mah...@bangalore wrote:
>
> My WiX file is something like this:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> So, my requirement is Component 'a' should be executed with file "abc.txt"
> if Feature1 is marked for install and it should be executed with
> Name="xyz.txt" if Feature2 is marked for ins
Just like the subject line says ...
Does anybody have any examples of WiX authoring that illustrate use of the
new chainer capabilities in Windows Installer v4.5 ?
Thanks in advance,
-dmm
--
View this message in context:
http://n2.nabble.com/Any-examples---samples-of-using-built-in-chainer--
Kamil Mierzejewski wrote:
>
> The tool is not publicly available. All I can do is to post source code
> (C++) or the compiled binary on your e-mail address.
>
> You can learn how to use it from the source - it's very small and simple.
>
> I think it is a piece of functionality that could be i
Is there any trick to this ... ?
We've got a merge module that is used by a couple of other groups, and while
the assemblies
get installed to the GAC properly ... when upgraded assemblies & policy
files get shipped, the
policy files don't seem to upgrade properly.
Thanks in advance,
-dmm
--
Vi
Mike, Phil -
Thanks for the quick responses !
After some more testing, it appears to be a problem with how InstallShield
is consuming the merge modules ... not with how they're built.
Now I just need to convince another development group to use WiX ...
Regards,
-dmm
--
View this message i
I'm building an updated version of an installation package [only the Crystal
Reports merge modules
have changed at this point ...] and I'm getting the following error:
light.exe : error LGHT0001 : Error HRESULT E_FAIL has been returned from a
call to a COM component.
Exception Type: System.Runti
OT, but I love that word...catastrophically. When functions in my
code fail, I generally don't relate them to cataclysmic events. :-)
**
I guess it depends on how close you are to your release date
**
Can you post some snippets of the module so we can have a look, namely
h
The documentation for ImsmMerge2::Merge wasn't exactly helpful
(http://msdn2.microsoft.com/en-us/library/aa369275.aspx):
Return Value
The Merge function returns the following values.
E_FAIL The merge failed catastrophically. This indicates an operational
error, and is not the normal error retur
Mike Dimmick wrote:
> Their build process generates random GUIDs every time they run a build.
>
Surely nobody does something that insane...?!
**
You'd be amazed at what some vendors will do to their customers ... !
And stop calling me Shirley ...
Thanks for the laugh Bob ...
Here's an update, just in case anybody cares ...
The problem cropped up with v2.0.5325.0 of WiX, in doing some testing to try
and isolate the
source of the error(s), I tested with v2.0.5213.0 ... and everything worked
fine.
I checked the change log and saw that with v2.0.5325.0, WiX was being bu
Bob Arnson-6 wrote:
>
>
> Mergemod.dll is a black box so it's impossible to know exactly what's
> different. WiX v3 also uses the Vista SDK so any problems are going to
> affect it too. It's either a bug in mergemod.dll or bad merge modules.
>
>
**
Thanks Bob ... I kinda figured th
Hi Folks -
I've run in to some weirdness with an installation package when trying to
modify an existing installation.
In Add/Remove Programs, both the Change and Remove buttons are displayed ...
but the Change button doesn't work as expected.
When the Change button is clicked, the installation
Chad Petersen wrote:
>
> Have you tried running the same MSI a second time. Does it do the same
> thing as when you click Change in Add/Remove Programs? If so, you should
> be able to have it create a verbose log which might lend some clues,
> like whether or not ARPNOMODIFY is being set or not.
Bob Arnson-6 wrote:
>
> ResumeDlg is used when restarting a setup after a forced reboot. Neither
> RESUME nor Preselected is set during a normal maintenance-mode run.
>
> --
> sig://boB
> http://joyofsetup.com/
>
Thanks Bob !
So how do you handle a setup which requires a reboot for complet
Bob Arnson-6 wrote:
>
> I'm not sure what you're asking. WixUI should handle it based on its
> conditions, but it's exceedingly rare (and rude) to require a reboot in
> the middle of an installation; worst case, reboots should happen at the
> end.
>
> sig://boB
> http://joyofsetup.com/
>
T
Richard.Foster wrote:
>
> I had so much hassle with the Business Objects merge modules I moved to
> using their MSI file and triggering it from a bootstrapper.
>
> > Snippage Applied ... <
>
> Hope this info is of interest.
> Regards,
> Richard
>
Thanks Richard !
Sounds like
Bob Arnson-6 wrote:
>
> If it's the BO merge modules, they should be taken out back and given a
> proper burial.
>
> --
> sig://boB
> http://joyofsetup.com/
>
Yes ... well ... if I get that opportunity, I'll be sure to invite you and
Richard to the wake.
Any ... other ... thoughts on the m
Bob Arnson-6 wrote:
>
> If the BO merge modules are causing Preselected to be set, I'm not sure
> there's a viable workaround. You should consider not using their merge
> modules -- they have .msi equivalents, at least for some of their stuff.
> Or you could create one, by merging their modul
Bob Arnson-6 wrote:
>
> It could be in the merge module's Property table or in custom actions.
>
I've checked through all of those ... but where does the property get
stored between runs of the installer ?
It's someplace that isn't effected by reboots [registry, but where?],
but how does the
Bob Arnson-6 wrote:
>
> It doesn't. MSI sets the Preselected property at runtime. See
> http://msdn2.microsoft.com/en-us/library/aa370839.aspx for the list.
>
Ok ... [scratching head & looking perplexed] ... if none of those properties
are being set via command line [since the installer is be
33 matches
Mail list logo
