Re: [WiX-users] Call a .NET dll file in wix using custom
Can you just provide me some example of how to use msicoree.dll in my
present wix file??
Regards
Poornima.S
Aztecsoft Limited
--
Message: 7
Date: Wed, 13 Aug 2008 13:27:00 -0700
From: Wilson, Phil [EMAIL PROTECTED]
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net,
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
Unfortunately that registration is still incomplete for a .NET assembly.
You need assembly name attributes plus the InprocServer32 Dll isn't your
assembly, it's msicoree.dll.
If you run regasm on your assembly with the /regfile option it will
generate a .reg file that will show you what registration is required.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Poornima S
Sent: Wednesday, August 13, 2008 6:35 AM
To: wix-users@lists.sourceforge.net;
[EMAIL PROTECTED]
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
Hi,
I checked verbose debug installation log and corrected the error, but
the initial issue is still existing, i.e,
DLFetcher Component is not registered[object error]
Can you please check the COM registry that I have made and let me know
what to do further?
COM registry in my WIX file as follows:
Component Id=DlFetcher Guid={235B5F90-EC82-4ce7-B433-8E4269A409EC}
Location=local
File KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
Class Id={E311303A-0F49-41cc-BF8D-549E376B6852}
Context=InprocServer32
ProgId Id=DLFetcher.RetreiveDL.1
ProgId Id=DLFetcher.RetreiveDL/
/ProgId
/Class
/File
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\InprocServer32
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
/Component
But when I checked into the registry entries, in HKLM I am able to see
the entries as follows:
*
HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\InprocServer32
* HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\ProgID
* HKLM\DLFetcher.RetreiveDL
In HKCR the entries are not happening Can you please help me in
solving this issue further Thanks in advance.
Regards
Poornima.S
Aztecsoft Limited
From: Blair Murri [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2008 1:17 AM
To: Poornima S
Cc: wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] Call a .NET dll file in wix using custom
Please check your verbose debug installation log to see what is causing
this error. That is a separate issue.
This email message and its attachments may contain CONFIDENTIAL AND
PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If
you have received it in error, please contact the sender by return
email, notify your system manager and destroy the original message and
any copies thereof. Any review, use, disclosure or distribution is
unlawful. Please check this email and any attachments for the presence
of viruses. The Company accepts no liability for any damage caused by
any virus transmitted by this email. The views or opinions presented in
this e-mail are solely those of the author and do not necessarily
represent those of the company.
The Company reserves the right to monitor, review and store the content
of all messages sent to or from this e-mail address.
www.aztecsoft.com
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url
Re: [WiX-users] Call a .NET dll file in wix using custom
Hi,
I checked verbose debug installation log and corrected the error, but
the initial issue is still existing, i.e,
DLFetcher Component is not registered[object error]
Can you please check the COM registry that I have made and let me know
what to do further?
COM registry in my WIX file as follows:
Component Id=DlFetcher Guid={235B5F90-EC82-4ce7-B433-8E4269A409EC}
Location=local
File KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
Class Id={E311303A-0F49-41cc-BF8D-549E376B6852}
Context=InprocServer32
ProgId Id=DLFetcher.RetreiveDL.1
ProgId Id=DLFetcher.RetreiveDL/
/ProgId
/Class
/File
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\InprocServer32
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
/Component
But when I checked into the registry entries, in HKLM I am able to see
the entries as follows:
*
HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\InprocServer32
* HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\ProgID
* HKLM\DLFetcher.RetreiveDL
In HKCR the entries are not happening Can you please help me in
solving this issue further Thanks in advance.
Regards
Poornima.S
Aztecsoft Limited
From: Blair Murri [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2008 1:17 AM
To: Poornima S
Cc: wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] Call a .NET dll file in wix using custom
Please check your verbose debug installation log to see what is causing
this error. That is a separate issue.
This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED
INFORMATION intended for the sole use of the addressee(s). If you have received
it in error, please contact the sender by return email, notify your system
manager and destroy the original message and any copies thereof. Any review,
use, disclosure or distribution is unlawful. Please check this email and any
attachments for the presence of viruses. The Company accepts no liability for
any damage caused by any virus transmitted by this email. The views or opinions
presented in this e-mail are solely those of the author and do not necessarily
represent those of the company.
The Company reserves the right to monitor, review and store the content of all
messages sent to or from this e-mail address.
www.aztecsoft.com
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Call a .NET dll file in wix using custom
Hi,
I checked verbose debug installation log and corrected the error, but the
initial issue is still existing, i.e,
DLFetcher Component is not registered[object error]
Can you please check the COM registry that I have made and let me know what to
do further?
COM registry in my WIX file as follows:
Component Id=DlFetcher Guid={235B5F90-EC82-4ce7-B433-8E4269A409EC}
Location=local
File
KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
Class
Id={E311303A-0F49-41cc-BF8D-549E376B6852}
Context=InprocServer32
ProgId Id=DLFetcher.RetreiveDL.1
ProgId Id=DLFetcher.RetreiveDL/
/ProgId
/Class
/File
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\InprocServer32
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
/Component
But when I checked into the registry entries, in HKLM I am able to see the
entries as follows:
* HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\InprocServer32
* HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\ProgID
* HKLM\DLFetcher.RetreiveDL
In HKCR the entries are not happening Can you please help me in solving
this issue further Thanks in advance.
Regards
Poornima.S
Aztecsoft Limited
From: Blair Murri [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2008 1:17 AM
To: Poornima S
Cc: wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] Call a .NET dll file in wix using custom
Please check your verbose debug installation log to see what is causing this
error. That is a separate issue.
This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED
INFORMATION intended for the sole use of the addressee(s). If you have received
it in error, please contact the sender by return email, notify your system
manager and destroy the original message and any copies thereof. Any review,
use, disclosure or distribution is unlawful. Please check this email and any
attachments for the presence of viruses. The Company accepts no liability for
any damage caused by any virus transmitted by this email. The views or opinions
presented in this e-mail are solely those of the author and do not necessarily
represent those of the company.
The Company reserves the right to monitor, review and store the content of all
messages sent
Re: [WiX-users] Call a .NET dll file in wix using custom
Hi,
I checked verbose debug installation log and corrected the error, but
the initial issue is still existing, i.e,
DLFetcher Component is not registered[object error]
Can you please check the COM registry that I have made and let me know
what to do further?
COM registry in my WIX file as follows:
Component Id=DlFetcher Guid={235B5F90-EC82-4ce7-B433-8E4269A409EC}
Location=local
File KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
Class Id={E311303A-0F49-41cc-BF8D-549E376B6852}
Context=InprocServer32
ProgId Id=DLFetcher.RetreiveDL.1
ProgId Id=DLFetcher.RetreiveDL/
/ProgId
/Class
/File
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\InprocServer32
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
/Component
But when I checked into the registry entries, in HKLM I am able to see
the entries as follows:
*
HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\InprocServer32
* HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\ProgID
* HKLM\DLFetcher.RetreiveDL
In HKCR the entries are not happening Can you please help me in
solving this issue further Thanks in advance.
Regards
Poornima.S
Aztecsoft Limited
From: Blair Murri [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2008 1:17 AM
To: Poornima S
Cc: wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] Call a .NET dll file in wix using custom
Please check your verbose debug installation log to see what is causing
this error. That is a separate issue.
This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED
INFORMATION intended for the sole use of the addressee(s). If you have received
it in error, please contact the sender by return email, notify your system
manager and destroy the original message and any copies thereof. Any review,
use, disclosure or distribution is unlawful. Please check this email and any
attachments for the presence of viruses. The Company accepts no liability for
any damage caused by any virus transmitted by this email. The views or opinions
presented in this e-mail are solely those of the author and do not necessarily
represent those of the company.
The Company reserves the right to monitor, review and store the content of all
messages sent to or from this e-mail address.
www.aztecsoft.com
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Call a .NET dll file in wix using custom
Unfortunately that registration is still incomplete for a .NET assembly. You
need assembly name attributes plus the InprocServer32 Dll isn't your assembly,
it's msicoree.dll.
If you run regasm on your assembly with the /regfile option it will generate a
.reg file that will show you what registration is required.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Poornima S
Sent: Wednesday, August 13, 2008 6:35 AM
To: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
Hi,
I checked verbose debug installation log and corrected the error, but
the initial issue is still existing, i.e,
DLFetcher Component is not registered[object error]
Can you please check the COM registry that I have made and let me know
what to do further?
COM registry in my WIX file as follows:
Component Id=DlFetcher Guid={235B5F90-EC82-4ce7-B433-8E4269A409EC}
Location=local
File KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
Class Id={E311303A-0F49-41cc-BF8D-549E376B6852}
Context=InprocServer32
ProgId Id=DLFetcher.RetreiveDL.1
ProgId Id=DLFetcher.RetreiveDL/
/ProgId
/Class
/File
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\InprocServer32
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
RegistryValue
Root=HKCR
Key=CLSID\{0F599288-CA74-467c-83CF-B853254159C7}\ProgID\ProgID
Value={0F599288-CA74-467c-83CF-B853254159C7}
Type=string
Action=write/
/Component
But when I checked into the registry entries, in HKLM I am able to see
the entries as follows:
*
HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\InprocServer32
* HKLM\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\ProgID
* HKLM\DLFetcher.RetreiveDL
In HKCR the entries are not happening Can you please help me in
solving this issue further Thanks in advance.
Regards
Poornima.S
Aztecsoft Limited
From: Blair Murri [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2008 1:17 AM
To: Poornima S
Cc: wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] Call a .NET dll file in wix using custom
Please check your verbose debug installation log to see what is causing
this error. That is a separate issue.
This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED
INFORMATION intended for the sole use of the addressee(s). If you have received
it in error, please contact the sender by return email, notify your system
manager and destroy the original message and any copies thereof. Any review,
use, disclosure or distribution is unlawful. Please check this email and any
attachments for the presence of viruses. The Company accepts no liability for
any damage caused by any virus transmitted by this email. The views or opinions
presented in this e-mail are solely those of the author and do not necessarily
represent those of the company.
The Company reserves the right to monitor, review and store the content of all
messages sent to or from this e-mail address.
www.aztecsoft.com
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Call a .NET dll file in wix using custom
Hi,
I added a COM registration to my wix file as follows:
Component Id=DlFetcher Guid={235B5F90-EC82-4ce7-B433-8E4269A409EC}
Location=local
File KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
/File
RegistryValue
Root=HKLM
Key=Software\WINDOWS\Microsoft.NET\Framework\v1.1.4322
Name={0F599288-CA74-467c-83CF-B853254159C7}
Type=string Value=D:\DLFetcher_July10\DLFetcher.dll
Action=write/
/Component
But still when when I try to run a html file, I am getting the same
problem:
DLFetcher Component is not registered[object error]
Can you please help me out in solving this issue further..
Regards,
Poornima.S
Message: 6
Date: Sun, 10 Aug 2008 22:28:15 -0700
From: Blair Murri [EMAIL PROTECTED]
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Message-ID:
[EMAIL PROTECTED]
icrosoft.com
Content-Type: text/plain; charset=us-ascii
GAC registration is only one part of the registration you have in your
sample batch file, the other part is COM registration. Please add your
COM registration (registry) to your wix sources. IE/javascript do not
look in the GAC, they look in the COM portion of the registry for the
objects they access.
From: [EMAIL PROTECTED]
[EMAIL PROTECTED] On Behalf Of Poornima S
[EMAIL PROTECTED]
Sent: Wednesday, August 06, 2008 5:08 AM
To: Neil Enns; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
But still I have a problem when I try to run a html file, although
DLfetcher is registered in gac, issue is as follows:
DLFetcher Component is not registered[object error]
Html file:
html
body
script language=javascript
try
{
ob1 = new ActiveXObject(DLFetcher.RetreiveDL);
alert(ob1);
if(ob1!=null)
{
username=ob1.GetUserName();
//alert(Windows : +username);
var IsUserValid=ob1.IsUserExist(username);
if(IsUserValid)
{
alert(UserName is available );
var arDL=ob1.GetDLforUserAsString(baijuv);
if(arDL.length==0)
{
alert(Invalid User);
}
else
{
alert(arDL);
}
}
else
{
alert(User is not avaliable in the Domain Control to
connect to Active Directory);
}
}
}
catch(e)
{
alert(DLFetcher component is not registered +e); } /script
/body /html
Can you please suggest me further, what changes can I do in wix so that
the dlfetcher component gets registered.
But when I try to run a batch file as follows:
c:
cd C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
regasm D:\DLFetcher_July10\DLFetcher.dll
gacutil /i D:\DLFetcher_July10\DLFetcher.dll
pause
the registry is happening in gac, as well as when I try to run my html
file, no issues are coming... So can you please suggest me a way to do
this procedure in wix...
Thanks in advance
Regards,
Poornima.S
This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED
INFORMATION intended for the sole use of the addressee(s). If you have received
it in error, please contact the sender by return email, notify your system
manager and destroy the original message and any copies thereof. Any review,
use, disclosure or distribution is unlawful. Please check this email and any
attachments for the presence of viruses. The Company accepts no liability for
any damage caused by any virus transmitted by this email. The views or opinions
presented in this e-mail are solely those of the author and do not necessarily
represent those of the company.
The Company reserves the right to monitor, review and store the content of all
messages sent to or from this e-mail address.
www.aztecsoft.com
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Call a .NET dll file in wix using custom
HKLM\Software\Windows\Microsoft.NET\Framework\v1.1.4322 is NOT a COM
registration. A COM registration would include registry keys similar to these
(values not included):
* HKCR\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\InprocServer32
* HKCR\CLSID\{576bdc7a-1b68-444b-8ea9-5c07d88b1ff2}\ProgID
* HKCR\DLFetcher.RetreiveDL
In WiX source, you can get these keys created using code like this (I don't
know which of your guids is your CLSID, so I can't fill it in for you):
Component Id=DlFetcher Guid={Component-GUID-HERE} Location=local
File
KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
Class Id={CLSID-GUID-HERE}
Context=InprocServer32
ProgId Id=DLFetcher.RetreiveDL.1
ProgId Id=DLFetcher.RetreiveDL/
/ProgId
/Class
/File
/Component
There are tutorials online on deployment of .Net and COM using WiX.
From: Poornima S [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2008 4:11 AM
To: Blair Murri; wix-users@lists.sourceforge.net
Subject: RE: Re: [WiX-users] Call a .NET dll file in wix using custom
Hi,
I added a COM registration to my wix file as follows:
Component Id=DlFetcher Guid={235B5F90-EC82-4ce7-B433-8E4269A409EC}
Location=local
File
KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
/File
RegistryValue
Root=HKLM
Key=Software\WINDOWS\Microsoft.NET\Framework\v1.1.4322
Name={0F599288-CA74-467c-83CF-B853254159C7}
Type=string Value=D:\DLFetcher_July10\DLFetcher.dll
Action=write/
/Component
But still when when I try to run a html file, I am getting the same problem:
DLFetcher Component is not registered[object error]
Can you please help me out in solving this issue further..
Regards,
Poornima.S
Message: 6
Date: Sun, 10 Aug 2008 22:28:15 -0700
From: Blair Murri [EMAIL PROTECTED]
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
GAC registration is only one part of the registration you have in your sample
batch file, the other part is COM registration. Please add your COM
registration (registry) to your wix sources. IE/javascript do not look in the
GAC, they look in the COM portion of the registry for the objects they access.
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Poornima S [EMAIL
PROTECTED]
Sent: Wednesday, August 06, 2008 5:08 AM
To: Neil Enns; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
But still I have a problem when I try to run a html file, although DLfetcher is
registered in gac, issue is as follows:
DLFetcher Component is not registered[object error]
Html file:
html
body
script language=javascript
try
{
ob1 = new ActiveXObject(DLFetcher.RetreiveDL);
alert(ob1);
if(ob1!=null)
{
username=ob1.GetUserName();
//alert(Windows : +username
Re: [WiX-users] Call a .NET dll file in wix using custom
GAC registration is only one part of the registration you have in your sample
batch file, the other part is COM registration. Please add your COM
registration (registry) to your wix sources. IE/javascript do not look in the
GAC, they look in the COM portion of the registry for the objects they access.
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Poornima S [EMAIL
PROTECTED]
Sent: Wednesday, August 06, 2008 5:08 AM
To: Neil Enns; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
But still I have a problem when I try to run a html file, although
DLfetcher is registered in gac, issue is as follows:
DLFetcher Component is not registered[object error]
Html file:
html
body
script language=javascript
try
{
ob1 = new ActiveXObject(DLFetcher.RetreiveDL);
alert(ob1);
if(ob1!=null)
{
username=ob1.GetUserName();
//alert(Windows : +username);
var IsUserValid=ob1.IsUserExist(username);
if(IsUserValid)
{
alert(UserName is available );
var arDL=ob1.GetDLforUserAsString(baijuv);
if(arDL.length==0)
{
alert(Invalid User);
}
else
{
alert(arDL);
}
}
else
{
alert(User is not avaliable in the Domain Control to
connect to Active Directory);
}
}
}
catch(e)
{
alert(DLFetcher component is not registered +e);
}
/script
/body
/html
Can you please suggest me further, what changes can I do in wix so that
the dlfetcher component gets registered.
But when I try to run a batch file as follows:
c:
cd C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
regasm D:\DLFetcher_July10\DLFetcher.dll
gacutil /i D:\DLFetcher_July10\DLFetcher.dll
pause
the registry is happening in gac, as well as when I try to run my html
file, no issues are coming... So can you please suggest me a way to do
this procedure in wix...
Thanks in advance
Regards,
Poornima.S
--
Glad to help. Unless you have an exceptionally good reason you should
*always* have exactly one file per component.
Neil
From: Poornima S [EMAIL PROTECTED]
Sent: Monday, August 04, 2008 10:59 PM
To: Neil Enns
Subject: RE: [WiX-users] Call a .NET dll file in wix using custom
Thanks Neil, its working fine now, I created a separate component and
under that I created my file element its working fine Thanks a
lot :)
Regards
Poornima.S
Aztecsoft Limited
-Original Message-
From: Neil Enns [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2008 10:30 AM
To: Poornima S; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Call a .NET dll file in wix using custom
A live.com search for 0x80131043 yielded many results, including this
one at Aaron's blog:
http://blogs.msdn.com/astebner/archive/2004/11/10/255346.aspx, and this
specific comment from him in the comment section:
The error code you are getting is 0x80131043. According to the chart
at the top of this blog post, it means Modules which are not in the
manifest were streamed in. This most likely means that your assembly
component contains other files that are not a part of this assembly.
You will need to double check your WXS file and make sure that you are
only installing one assembly per component (unless the assembly consists
of multiple files and is a multi-module assembly).
Neil
-Original Message-
From: Poornima S
Sent: Tuesday, August 05, 2008 10:24 AM
To: 'wix-users@lists.sourceforge.net'
Cc: '[EMAIL PROTECTED]'
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
I tried to register DLL in the GAC, by adding Assembly=.net to my
File element, as below:
File KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
/File
But I am getting an error when I try to run my installer as follows:
An error occurred during the installation of assembly
'DLFetcher,version=1.1.0.0,
culture=neutral,publickeyToken=402B9D8975482830'. Please refer to
Help and support for more information. HRESULT:0x80131043.
Please can you further help me out in solving this issue.
Regards
Poornima.S
Aztecsoft Limited
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, August 04, 2008 8:32 PM
To: wix-users@lists.sourceforge.net
Subject: WiX-users Digest, Vol 27, Issue 8
Send WiX-users mailing list submissions to
wix-users@lists.sourceforge.net
To subscribe
Re: [WiX-users] Call a .NET dll file in wix using custom
But still I have a problem when I try to run a html file, although
DLfetcher is registered in gac, issue is as follows:
DLFetcher Component is not registered[object error]
Html file:
html
body
script language=javascript
try
{
ob1 = new ActiveXObject(DLFetcher.RetreiveDL);
alert(ob1);
if(ob1!=null)
{
username=ob1.GetUserName();
//alert(Windows : +username);
var IsUserValid=ob1.IsUserExist(username);
if(IsUserValid)
{
alert(UserName is available );
var arDL=ob1.GetDLforUserAsString(baijuv);
if(arDL.length==0)
{
alert(Invalid User);
}
else
{
alert(arDL);
}
}
else
{
alert(User is not avaliable in the Domain Control to
connect to Active Directory);
}
}
}
catch(e)
{
alert(DLFetcher component is not registered +e);
}
/script
/body
/html
Can you please suggest me further, what changes can I do in wix so that
the dlfetcher component gets registered.
But when I try to run a batch file as follows:
c:
cd C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
regasm D:\DLFetcher_July10\DLFetcher.dll
gacutil /i D:\DLFetcher_July10\DLFetcher.dll
pause
the registry is happening in gac, as well as when I try to run my html
file, no issues are coming... So can you please suggest me a way to do
this procedure in wix...
Thanks in advance
Regards,
Poornima.S
--
Glad to help. Unless you have an exceptionally good reason you should
*always* have exactly one file per component.
Neil
From: Poornima S [EMAIL PROTECTED]
Sent: Monday, August 04, 2008 10:59 PM
To: Neil Enns
Subject: RE: [WiX-users] Call a .NET dll file in wix using custom
Thanks Neil, its working fine now, I created a separate component and
under that I created my file element its working fine Thanks a
lot :)
Regards
Poornima.S
Aztecsoft Limited
-Original Message-
From: Neil Enns [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2008 10:30 AM
To: Poornima S; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Call a .NET dll file in wix using custom
A live.com search for 0x80131043 yielded many results, including this
one at Aaron's blog:
http://blogs.msdn.com/astebner/archive/2004/11/10/255346.aspx, and this
specific comment from him in the comment section:
The error code you are getting is 0x80131043. According to the chart
at the top of this blog post, it means Modules which are not in the
manifest were streamed in. This most likely means that your assembly
component contains other files that are not a part of this assembly.
You will need to double check your WXS file and make sure that you are
only installing one assembly per component (unless the assembly consists
of multiple files and is a multi-module assembly).
Neil
-Original Message-
From: Poornima S
Sent: Tuesday, August 05, 2008 10:24 AM
To: 'wix-users@lists.sourceforge.net'
Cc: '[EMAIL PROTECTED]'
Subject: Re: [WiX-users] Call a .NET dll file in wix using custom
I tried to register DLL in the GAC, by adding Assembly=.net to my
File element, as below:
File KeyPath=yes Id=InstallDlfetcher
Name=DLFetcher.dll
DiskId=1
Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net
/File
But I am getting an error when I try to run my installer as follows:
An error occurred during the installation of assembly
'DLFetcher,version=1.1.0.0,
culture=neutral,publickeyToken=402B9D8975482830'. Please refer to
Help and support for more information. HRESULT:0x80131043.
Please can you further help me out in solving this issue.
Regards
Poornima.S
Aztecsoft Limited
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, August 04, 2008 8:32 PM
To: wix-users@lists.sourceforge.net
Subject: WiX-users Digest, Vol 27, Issue 8
Send WiX-users mailing list submissions to
wix-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of WiX-users digest...
Today's Topics:
1. FW: Re: ServiceInstall account problem (Daniel Rieck)
2. updating with a different account? (Mattias ?slund)
3. Call a .NET dll file in wix using custom action (Poornima S)
4
[WiX-users] Call a .NET dll file in wix using custom action
Hi All, I have a DLfetcher.dll file which is in .NET. I need to create a WIX installer for my application, and when I run that msi the dll file should get registered in GAC. I modified my WXS file to use custom action behaviour of WIX. Code is as below: Binary Id=InstallDlfetcher SourceFile=D:\DLFetcher_July10\DLFetcher.dll/ CustomAction Id=LaunchDlfetcher BinaryKey=InstallDlfetcher DllEntry=InstallDlfetcher Execute=deferred/ InstallExecuteSequence Custom Action=LaunchDlfetcher Before=InstallFinalize/ InstallExecuteSequence But when I run installer, I couldn't find in gac folder the registry entry creating a DlFetcher folder. Please help me to get out of here. Is there any way to call a dll file from wix and while I try to run my installer that should get registered in GAC.? Thanks everyone in advance... Regards Poornima.S This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If you have received it in error, please contact the sender by return email, notify your system manager and destroy the original message and any copies thereof. Any review, use, disclosure or distribution is unlawful. Please check this email and any attachments for the presence of viruses. The Company accepts no liability for any damage caused by any virus transmitted by this email. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The Company reserves the right to monitor, review and store the content of all messages sent to or from this e-mail address. www.aztecsoft.com - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Call a .NET dll file in wix using custom action
If all you are trying to do is register your DLL in the GAC, add Assembly=.net to your File element and it'll automatically get installed to the GAC. Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Poornima S [EMAIL PROTECTED] Sent: Monday, August 04, 2008 5:38 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Call a .NET dll file in wix using custom action Hi All, I have a DLfetcher.dll file which is in .NET. I need to create a WIX installer for my application, and when I run that msi the dll file should get registered in GAC. I modified my WXS file to use custom action behaviour of WIX. Code is as below: Binary Id=InstallDlfetcher SourceFile=D:\DLFetcher_July10\DLFetcher.dll/ CustomAction Id=LaunchDlfetcher BinaryKey=InstallDlfetcher DllEntry=InstallDlfetcher Execute=deferred/ InstallExecuteSequence Custom Action=LaunchDlfetcher Before=InstallFinalize/ InstallExecuteSequence But when I run installer, I couldn't find in gac folder the registry entry creating a DlFetcher folder. Please help me to get out of here. Is there any way to call a dll file from wix and while I try to run my installer that should get registered in GAC.? Thanks everyone in advance... Regards Poornima.S This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If you have received it in error, please contact the sender by return email, notify your system manager and destroy the original message and any copies thereof. Any review, use, disclosure or distribution is unlawful. Please check this email and any attachments for the presence of viruses. The Company accepts no liability for any damage caused by any virus transmitted by this email. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The Company reserves the right to monitor, review and store the content of all messages sent to or from this e-mail address. www.aztecsoft.comhttp://www.aztecsoft.com/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Call a .NET dll file in wix using custom
:* 31.07.08 23:47:23 *An:* General discussion for Windows Installer XML toolset. WIX-USERS@LISTS.SOURCEFORGE.NET *Betreff:* Re: [WiX-users] ServiceInstall account problem Daniel Rieck wrote: 1) I'm getting error 1923. 1923 almost always indicates a problem with the attributes on the ServiceInstall element, such as a bad user/password combination. Can you show what yours looks like? -- sig://boB http://joyofsetup.com/ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Message: 2 Date: Sun, 3 Aug 2008 14:29:26 +0200 From: Mattias ?slund [EMAIL PROTECTED] Subject: [WiX-users] updating with a different account? To: wix-users@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 This is not a WiX-specific question I guess, but rather a windows installer problem, but you guys seem to have a lot of answers? I have two msi-packages for different versions of the same application (created by wix 3). Version two successfully upgrades version one, if run manually from the same user account with ?msiexec /i package2.msi /quiet REINSTALL=ALL REINSTALLMODE=vomus?. However, I?m trying to implement an auto-upgrade system by letting a service (run as LocalSystem) download the msi from a website and run the above command. When I do this, all features are marked as not installed and the installer doesn?t change the system. Not even the ARP-entry changes version. I have set MigrateFeatures=yes in UpgradeVersion/, but this only fixes things for the same user account. So, where am I shooting myself in the foot? ;) Yours, Mattias ?slund [EMAIL PROTECTED] -- Message: 3 Date: Mon, 4 Aug 2008 18:08:34 +0530 From: Poornima S [EMAIL PROTECTED] Subject: [WiX-users] Call a .NET dll file in wix using custom action To: wix-users@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Hi All, I have a DLfetcher.dll file which is in .NET. I need to create a WIX installer for my application, and when I run that msi the dll file should get registered in GAC. I modified my WXS file to use custom action behaviour of WIX. Code is as below: Binary Id=InstallDlfetcher SourceFile=D:\DLFetcher_July10\DLFetcher.dll/ CustomAction Id=LaunchDlfetcher BinaryKey=InstallDlfetcher DllEntry=InstallDlfetcher Execute=deferred/ InstallExecuteSequence Custom Action=LaunchDlfetcher Before=InstallFinalize/ InstallExecuteSequence But when I run installer, I couldn't find in gac folder the registry entry creating a DlFetcher folder. Please help me to get out of here. Is there any way to call a dll file from wix and while I try to run my installer that should get registered in GAC.? Thanks everyone in advance... Regards Poornima.S This email message and its attachments may contain CONFIDENTIAL AND PRIVILEGED INFORMATION intended for the sole use of the addressee(s). If you have received it in error, please contact the sender by return email, notify your system manager and destroy the original message and any copies thereof. Any review, use, disclosure or distribution is unlawful. Please check this email and any attachments for the presence of viruses. The Company accepts no liability for any damage caused by any virus transmitted by this email. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those
Re: [WiX-users] Call a .NET dll file in wix using custom
A live.com search for 0x80131043 yielded many results, including this one at Aaron's blog: http://blogs.msdn.com/astebner/archive/2004/11/10/255346.aspx, and this specific comment from him in the comment section: The error code you are getting is 0x80131043. According to the chart at the top of this blog post, it means Modules which are not in the manifest were streamed in. This most likely means that your assembly component contains other files that are not a part of this assembly. You will need to double check your WXS file and make sure that you are only installing one assembly per component (unless the assembly consists of multiple files and is a multi-module assembly). Neil From: Poornima S [EMAIL PROTECTED] Sent: Monday, August 04, 2008 9:54 PM To: wix-users@lists.sourceforge.net Cc: Neil Enns Subject: Re: [WiX-users] Call a .NET dll file in wix using custom I tried to register DLL in the GAC, by adding Assembly=.net to my File element, as below: File KeyPath=yes Id=InstallDlfetcher Name=DLFetcher.dll DiskId=1 Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net /File But I am getting an error when I try to run my installer as follows: An error occurred during the installation of assembly 'DLFetcher,version=1.1.0.0, culture=neutral,publickeyToken=402B9D8975482830'. Please refer to Help and support for more information. HRESULT:0x80131043. Please can you further help me out in solving this issue. Regards Poornima.S Aztecsoft Limited -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, August 04, 2008 8:32 PM To: wix-users@lists.sourceforge.net Subject: WiX-users Digest, Vol 27, Issue 8 Send WiX-users mailing list submissions to wix-users@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/wix-users or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of WiX-users digest... Today's Topics: 1. FW: Re: ServiceInstall account problem (Daniel Rieck) 2. updating with a different account? (Mattias ?slund) 3. Call a .NET dll file in wix using custom action (Poornima S) 4. Re: updating with a different account? (Eitan Behar) 5. Re: Call a .NET dll file in wix using custom action (Neil Enns) 6. Sending params to Deferred Custom Action (Benas) 7. Re: Sending params to Deferred Custom Action (Buddell, James) -- Message: 1 Date: Mon, 04 Aug 2008 13:07:39 +0200 From: Daniel Rieck [EMAIL PROTECTED] Subject: [WiX-users] FW: Re: ServiceInstall account problem To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-15 That put me in the right direction. Thanks to everyone! *Von:* Daniel Rieck [EMAIL PROTECTED] *Gesendet:* 01.08.08 22:35:39 *An:* General discussion for Windows Installer XML toolset. WIX-USERS@LISTS.SOURCEFORGE.NET *Betreff:* Re: [WiX-users] ServiceInstall account problem I'm already home for the weekend, but I'll check that on Monday, because I changed all the names in the file before sending it... *Von:* Wilson, Phil [EMAIL PROTECTED] *Gesendet:* 01.08.08 20:40:07 *An:* General discussion for Windows Installer XML toolset. *Betreff:* Re: [WiX-users] ServiceInstall account problem Isn't the Name required to be the same in ServiceInstall and ServiceControl? (As in the example at http://avinashkt.blogspot.com/2007/05/how-to-install-windows-service-usi ng.html where they are both WixServiceInstaller). Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Rieck Sent: Friday, August 01, 2008 12:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall account problem Here's my entire WiX file: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi [http://schemas.microsoft.com/wix/2006/wi]; Product Id=5028B1BB-BCDE-470b-8A0D-25E49DE32661 Name=MyService Language=1031 Version=1.0.0.0 Manufacturer=Me UpgradeCode=7EAE2B64-7637-4c89-BF85-D288CE0E5E6F Package InstallerVersion=200 Compressed=yes / Condition Message=This application requires Windows XP SP2 or above. ![CDATA[Installed OR (VersionNT=501 AND ServicePackLevel=2) OR (VersionNT501)]] /Condition Media Id=1 Cabinet=MyService.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=INSTALLLOCATION Name=MyService Component Id=InstallService Guid=0A86B4CB-3494-4a12-B88B-66C75B23BCFE Permanent=no SharedDllRefCount
Re: [WiX-users] Call a .NET dll file in wix using custom
Hi Poornima, Did You add SNk for u r library(dll). Thanks Regards, Chandrashekar vuppala Noor College of Engineering Tech M-9908298419 From: [EMAIL PROTECTED] on behalf of Poornima S Sent: Tue 5/08/2008 10:24 AM To: wix-users@lists.sourceforge.net Cc: [EMAIL PROTECTED] Subject: Re: [WiX-users] Call a .NET dll file in wix using custom I tried to register DLL in the GAC, by adding Assembly=.net to my File element, as below: File KeyPath=yes Id=InstallDlfetcher Name=DLFetcher.dll DiskId=1 Source=D:\DLFetcher_July10\DLFetcher.dll Assembly=.net /File But I am getting an error when I try to run my installer as follows: An error occurred during the installation of assembly 'DLFetcher,version=1.1.0.0, culture=neutral,publickeyToken=402B9D8975482830'. Please refer to Help and support for more information. HRESULT:0x80131043. Please can you further help me out in solving this issue. Regards Poornima.S Aztecsoft Limited -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, August 04, 2008 8:32 PM To: wix-users@lists.sourceforge.net Subject: WiX-users Digest, Vol 27, Issue 8 Send WiX-users mailing list submissions to wix-users@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/wix-users or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of WiX-users digest... Today's Topics: 1. FW: Re: ServiceInstall account problem (Daniel Rieck) 2. updating with a different account? (Mattias ?slund) 3. Call a .NET dll file in wix using custom action (Poornima S) 4. Re: updating with a different account? (Eitan Behar) 5. Re: Call a .NET dll file in wix using custom action (Neil Enns) 6. Sending params to Deferred Custom Action (Benas) 7. Re: Sending params to Deferred Custom Action (Buddell, James) -- Message: 1 Date: Mon, 04 Aug 2008 13:07:39 +0200 From: Daniel Rieck [EMAIL PROTECTED] Subject: [WiX-users] FW: Re: ServiceInstall account problem To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-15 That put me in the right direction. Thanks to everyone! *Von:* Daniel Rieck [EMAIL PROTECTED] *Gesendet:* 01.08.08 22:35:39 *An:* General discussion for Windows Installer XML toolset. WIX-USERS@LISTS.SOURCEFORGE.NET *Betreff:* Re: [WiX-users] ServiceInstall account problem I'm already home for the weekend, but I'll check that on Monday, because I changed all the names in the file before sending it... *Von:* Wilson, Phil [EMAIL PROTECTED] *Gesendet:* 01.08.08 20:40:07 *An:* General discussion for Windows Installer XML toolset. *Betreff:* Re: [WiX-users] ServiceInstall account problem Isn't the Name required to be the same in ServiceInstall and ServiceControl? (As in the example at http://avinashkt.blogspot.com/2007/05/how-to-install-windows-service-usi ng.html where they are both WixServiceInstaller). Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Rieck Sent: Friday, August 01, 2008 12:40 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall account problem Here's my entire WiX file: ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi [http://schemas.microsoft.com/wix/2006/wi]; Product Id=5028B1BB-BCDE-470b-8A0D-25E49DE32661 Name=MyService Language=1031 Version=1.0.0.0 Manufacturer=Me UpgradeCode=7EAE2B64-7637-4c89-BF85-D288CE0E5E6F Package InstallerVersion=200 Compressed=yes / Condition Message=This application requires Windows XP SP2 or above. ![CDATA[Installed OR (VersionNT=501 AND ServicePackLevel=2) OR (VersionNT501)]] /Condition Media Id=1 Cabinet=MyService.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=INSTALLLOCATION Name=MyService Component Id=InstallService Guid=0A86B4CB-3494-4a12-B88B-66C75B23BCFE Permanent=no SharedDllRefCount=no File Id=WindowsService Name=MyService.exe Source=D:...in?ReleaseMyService.exe KeyPath=yes Checksum=yes / ServiceInstall Id=MyServiceId Name=MyService DisplayName=MyService Type=ownProcess Start=auto ErrorControl=normal Description= Interactive=no Vital=yes Account=[SERVICEACCOUNT] Password=[SERVICEPASSWORD] / ServiceControl Id=StartService Name=MyServiceId Start=install Stop=uninstall Remove=uninstall / /Component /Directory /Directory /Directory Feature Id=ProductFeature Title=MyService Level=1 ComponentRef Id=InstallService / /Feature
