I think Rob is right, the WiX code uses an assembly
System.EnterpriseServices (method RegistrationHelper) to install COM+ this
doesn't seem to have a .NET version associated with it but on a couple of
machines I have checked they don't always have the .NET 4.0 reference
under the InprocServer32
Thanks for your answer, Creation C++ dll is overkill for our App and
described problem.
BTW: Problem solved.
The custom action can't modify property inside InstallExecuteSequence for
some reason. Embedding into InstallUISequence helps.
2013/3/19 Christopher Painter chr...@iswix.com
You want:
Vladimir,
You're problems are not solved, you just don't know what other problems
you have are yet. I suggest starting with reading:
http://www.installsite.org/pages/en/isnews/200108/index.htm
Regards,
CHris
From: Vladimir Yelnikov
They are being marked as a shared file in the registry but I don't know why.
Here is my WXS file:
?xml version=1.0?
?include ..\..\files\ProductVersion.wxi ?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Module Id=APIx86 Language=1033 Version=$(var.ProductVersion)
Hi all,
I need to know the Feature/Component states for the following scenarios
1) Install
2) Uninstall
3) Repair
4) Patch Install
5) Patch Uninstall
I have separate custom actions for these scenarios which needs to be
scheduled based on condition. Also what is the relation
thanks!
2013/3/20 Christopher Painter chr...@iswix.com
Vladimir,
You're problems are not solved, you just don't know what other problems
you have are yet. I suggest starting with reading:
http://www.installsite.org/pages/en/isnews/200108/index.htm
Regards,
CHris
Classification: Public
See below
-Original Message-
From: Subbiah Ganesan [mailto:subbiahtv...@gmail.com]
Sent: March-20-13 9:43 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] CA schedule
Hi all,
I need to know the Feature/Component states for the following scenarios
1)
I've also been pointed to this:
http://code.dblock.org/msi-property-patterns-upgrading-firstinstall-and-maintenance
Alain
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: March 20, 2013 09:57
To: General discussion for Windows Installer XML toolset.
No problem. Come back if you have any questions. As an example, I mention
this link to you because by moving your CA from the execute sequence to the
UI sequence you've broken your silent installation story.
The next thing on your reading list is:
Hmmm... I haven't done COM+ apps in 10 years but I guess I don't see the
connection to .NET. My custom actions (InstallScript back then) always
used the COMAdmin objects which were unmanaged.
For .NET remoting I think of things like remoting, webservices, wcf et
al...
I described the problem here few days ago:
http://stackoverflow.com/questions/15495998/custom-action-as-64-bit-process
I have a setup destined for 64 bit platforms. In that setup I referenced a
C# custom action project that is build 64 bit. In one of functions, I
noticed that process is 32 bit
These are COM objects written in .NET, IIRC you have to go through some
hoops to install them and you can (and WiX does) use the
System.EnterpriseServices to do it.
Hmmm... I haven't done COM+ apps in 10 years but I guess I don't see the
connection to .NET. My custom actions (InstallScript back
I had a really good response typed up but then IE10 crapped out on me like
it always does. It really doesn't like my webmail site.
The short version is that namespace is .NET Enterprsie Services is 12 years
old and I wouldn't touch it with a 10 foot pole. Microsoft has rewritten
the remoting
We have a custom action that was working just fine in 3.5, we are upgrading to
3.7 and have noticed that for some reason we are getting an Out of Memory
errors anytime we call WcaGetProperty.
Our first entry point is called BeginInstall and here are the first few lines
of code:
UINT
Just a guess but you aren't initializing your pointer to null. Possibly the
API is trying to free the old string before allocating a new one...
On Mar 20, 2013, at 11:45 AM, Tristen Fielding tfield...@tradestation.com
wrote:
We have a custom action that was working just fine in 3.5, we are
I am not sure I follow what has remoting API got to do with installing COM+
services? System.EnterpriseServices is still part of all versions of .NET and
is used to support COM+ and as far as I can tell is what WiX uses to install
COM+ and I was just trying to help someone with COM+
Rob answered in StackOverFlow
Phil
-Original Message-
From: Eddy Ukstein [mailto:edd...@gmail.com]
Sent: Wednesday, March 20, 2013 7:21 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] 64bit custom actions
I described the problem here few days ago:
As the documentation says, if the file path is already in SharedDlls it will
be incremented there.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368007(v=vs.85).as
px
See msidbComponentAttributesSharedDllRefCount. Your log shows this is
happening. It's too late for you to do
Thanks. Sometimes the obvious thing is the thing you overlook. This code had
been working just fine for many years (under 3.5) and now it is failing (under
3.7) all because we aren't initializing our pointers to null before call
WcaGetProperty.
Thanks for the tip!
Tristen Fielding
Neil,
I'm just giving my opinion. ArrayList and HashTable is still in the .NET
Framework but that doesn't mean you should use it instead of ListT and
DictionaryT.
COM+ is a remoting technology and there are several generations that have
followed it that are better and make deployment
Thanks got it all fixed up.
Thank you,
Michael Ogilvie
Application Support Specialist
1900 City Park Drive Ottawa, ON K1J 1A3
Tel: 613-247-1211 ext 242 | Cell: 613-302-9844
http://www.Pixelink.com
Sent from my iPhone
On 2013-03-20, at 2:00 PM, Phil Wilson phil.wil...@mvps.org wrote:
As the
I reverted back to 3.6 and I still see this issue, so it's nothing to so with
the wix version.
Any ideas on why it would automatically restart the exe when the install
finishes?
I am using the custom ba from Neil S.
Thank you,
Michael Ogilvie
Application Support Specialist
1900 City Park
Classification: Public
Can you post the bundle.wxs code (if you did already sorry)
I am also using Neil's custom BA and it is fine...
Steve
-Original Message-
From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com]
Sent: March-20-13 2:54 PM
To: General discussion for Windows
Can't disagree that there are better alternatives to COM+ for remoting but it
is more than just remoting technology and unfortunately some of us still use
it. Anyway we've gone a bit off topic.
From: Christopher Painter [mailto:chr...@iswix.com]
Sent: 20 March 2013 18:30
To: Neil Sleightholm;
The two logs you posted earlier seem to be from different installs,
Camera_Kit.exe and SDK_Kit.exe. When this happen do you get two consecutive
logs from the same install?
-Original Message-
From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com]
Sent: 20 March 2013 18:54
To:
You were getting very lucky if you were not initializing your pointers to
NULL. I'm surprised things weren't crashing immediately. smile/
On Wed, Mar 20, 2013 at 10:48 AM, Tristen Fielding
tfield...@tradestation.com wrote:
Thanks. Sometimes the obvious thing is the thing you overlook. This
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 ...
I have had a look at the WiX code and my suspicion is that it loads which ever
version of the .NET framework is in the msiexec process space, so if .NET 2.0
(or 3.5) was first then that is how it loads the COM+ assembly therefore if
yours if .NET 4.0 is won't work. I am not sure how that could
If that's the case, a DTF custom action wouldn't have that problem.
From: Neil Sleightholm n...@x2systems.com
Sent: Wednesday, March 20, 2013 4:49 PM
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Subject: Re:
Hi,
Our product may ship database changes in a Patch.
The database may be shared between users.
We are not recording the current state of the database - like save the
Upgrade Code, Product Code and Patch Code in a table in the database, so we
can't derive whether the database has already been
30 matches
Mail list logo
