The issue has got resolved by .def file & then specifying at
Linker/Input/ModuleDefinatioFile in project settings which seems mandatory
for release build.
Thanks for all the inputs.
Regards,
Nag
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Friday, Januar
One issue that I noticed with depends.exe is that in case of release version
DLL the exported functions are decorated like ?funcName@@y...@z but whereas
in case of debug version the function remained same(not decorated)
- Nag
-Original Message-
From: nagaram.c [mailto:nagara
I am able to see the exported functions & the MSI if using
__declspec(dllexport) instead .def but still the issue exists with release
build not working while adding to .cub file
- Nag
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Friday, January 08, 2010 4:5
I am using #pragma comment(lib, "msi.lib") in the code
- Nag
-Original Message-----
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Friday, January 08, 2010 4:52 AM
To: 'Blair'; 'General discussion for Windows Installer XML toolset.';
'ra...@symphony.c
ally link to their libraries
such that those dlls are no longer required.
-Original Message-----
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Tuesday, January 06, 2009 9:59 PM
To: 'General discussion for Windows Installer XML toolset.'; 'Blair';
ra...@symphony.cc
he following string format was not
expected by the external UI message logger: "There is a problem with this
Windows Installer package. A DLL required for this install to complete could
not be run. Contact your support personnel or package vendor. ".
- Nag
-----Original Message-
From:
nges in the confirmation dialog), change
the Runtime Library setting to "Multi-threaded (/MT)", then hit Apply and
OK.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Wednesday, January 06, 2010 5:17 AM
To: 'Blair'; 'General discussion for
build Release (not Debug) for the version you
run away from the developer's box.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Tuesday, January 05, 2010 11:43 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] getting win32 exception while running
Hi,
I am getting below exception to my newly added ICE, whereas the same works
fine in the developer environment but fails in the tester environment, both
are XP machines.
To the tester environment I have deployed the below files
smoke.exe
wconsole.dll
wix.dll
darice.cub (containi
Thanks Blair, it took a while for me to understand what is all about,
MsiProcessMessage as you suggested works absolutely fine. It's just that
formatting that I was attempting was incorrect.
I appreciate for all your support.
- Nag
-Original Message-
From: nagaram.c [mailto:n
Hi,
I am using just smoke.exe to one of solutions I am working right now, Is
there any link by which only this light weight component be downloaded
instead of wix toolkit that requires visual studio.
Thanks,
Nag
--
The vbs in darice.cub are specific to ICE it does not contain any generic
functions as I taught of earlier.
Nag
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Tuesday, January 05, 2010 5:43 AM
To: 'Blair'; 'General discussion for Windows Instal
quence) and never as
control events (there is no UI associated with ICE tests).
Why is a control event even an issue?
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Monday, January 04, 2010 10:39 PM
To: 'Blair'; 'General discussion for Windows Instal
== error)
{
return MsiProcessMessage(hInstall, INSTALLMESSAGE_USER, hRecord);
}
return (int) error;
}
-----Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Monday, January 04, 2010 5:20 AM
To: 'Blair'; 'General discussion for Windows Installer
indows Installer
custom actions that are marked 'extern "C"' and are also listed in the .def
file to prevent any form of compiler/linker decoration.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Sunday, January 03, 2010 10:08 PM
To: 'B
al Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Thursday, December 31, 2009 3:33 AM
To: 'Schrieken, Rene'; 'General discussion for Windows Installer XML
toolset.'
Subject: Re: [WiX-users] writing to console from smoke.exe using
customaction
With the
API-s for this.
Dan
Quoting "nagaram.c" :
> Thanks once again for clarification, I think if there is any way to locate
> non-COM file then that should be File table & selfReg table, like if
suppose
> if a particular record in File table has reference to selfReg then i
sole(...);
Please save everything before you try this...
_
Van: nagaram.c [mailto:nagara...@symphony.cc]
Verzonden: di 29-12-2009 8:04
Aan: Schrieken, Rene; 'General discussion for Windows Installer XML
toolset.'; 'General discussion for Windows Installer XML toolset.&#
Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: 29 December 2009 10:37
To: Peter Shirtcliffe; 'General discussion for Windows Installer XML
toolset.'
Subject: RE: [WiX-users] differentiating between COM & C++ dlls from
installerdatabase (.msi)
Hi,
Thanks for your informa
s a File table ID.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: 29 December 2009 12:20
To: Peter Shirtcliffe; 'General discussion for Windows Installer XML
toolset.'
Subject: RE: [WiX-users] differentiating between COM & C++ dlls from
installerd
he following:
Class table
ProgId table
Registry table
SelfReg table
TypeLib table
There is no equivalent of the MSIAssembly table for COM.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: 29 December 2009 09:59
To: 'General discussion for Windows Installer XML
Hi,
Is there a way that I could differentiate between COM & C++ DLL by looking
into the installer database file (.msi), I know that all .NET components are
maintained in msiAssembly table but I think both COM & C++ files are
maintained under Files table, is there a way by looking into some attr
myMSI.msi >> smoke.log
(use two >> to redirect output, that will open the file for append, instead
of create)
_____
Van: nagaram.c [mailto:nagara...@symphony.cc]
Verzonden: do 24-12-2009 6:46
Aan: 'General discussion for Windows Installer XML toolset.'; 'Blair
; switch in the command line could get appended every time the program is
executed
Nag
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Tuesday, December 22, 2009 11:54 PM
To: 'Blair'; 'General discussion for Windows Installer XML toolset.'
Subj
o console from smoke.exe using custom
action
You need to use MsiProcessMessage with the INSTALLMESSAGE_USER type. See
http://msdn.microsoft.com/library/aa369205.aspx for details.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Tuesday, December 22, 2009 5:13 AM
Hi,
I wrote a custom action dll in C++ & added to .cub file that I am using in
-cub switch in smoke.exe, I was not successful in writing to console like
the ICE(s) in darice.cub does it but I am able to display the log info in
MessageBox.
Thanks,
Nag
-
26 matches
Mail list logo
