You can run dot net code during installation, although there are some reason
why you should not. I have been executing .net code in my installation for
quite a while now
Anyways here how to do it :
Include the following
In a class library project, add a installer class. Check out
http://g
はじめまして美樹です。
掲示板で見て趣味合うかなって思ってメールしちゃいました。
イキナリでゴメンなさいm(__)m
こういう感じで知り合えるのに憧れてて初挑戦しちゃいました。
お返事もらえたら簡単な自己紹介しますネ(^_-)-☆
もしそんな気なかったらそう言ってもらえれば諦めますので。
もちろん仲良くなれた方が嬉しいけど。
お返事気長に待ってま〜す(^_^)/~
http://www.star-lightz.com/m-box
-
Tak
I need to launch some .net code during installation. Which possibilities do
I have? As I hear there are problems with .net custom actions in Windows
Installer.
So I cant add my .net assembly exe into the product as file or binary stream
and use one of the custom actions types to launch it?
Only wa
I have a Wix generated .msi file and it has been working fine for sometime
now (in English). Recently when I tried to deply on a machine that was low
on disk space I received an error dialog indicating that the machine had
insufficient space to proceed but this error message was in German. The
butt
I don't believe there's been a change in ALLUSERS=2 behavior, only in
the documentation that Scott pointed at. MSADN from August 2006 doesn't
single out XP, for example.
I've never been a fan of ALLUSERS=2 because of its unpredictability.
Sometimes you'll get per-user, sometimes per-machine. How
Hello Fredrik,
Thanks for the help. I was able to create a queue using pca:MessageQueue
element.
There is one weird thing:
If I already have a queue created and i try to run the install it says
failed prematurely because queue exist so it rolls back and deletes the
queue. Now I run the install a
In a previous message this was posted:
Re: [WiX-users] Question about upgrading to Wix3 (beta)
Bob Arnson
Sun, 25 Feb 2007 11:57:39 -0800
James Hill wrote:
So, my question is why are there no .wixlib and .wxl files in the Wix
3.0 beta distribution.
They're included in the WiX extensions. So
Hi,
I sucessfully did a per-machine installer that works on XP and on Vista (at
least on the tests in the virtual machines worked fine).
I use the ALLUSERS=2 option to make vista put the shortcuts on all the users
desktop and start menu, but the secret is to include a bootstrapper. I use
the Gen
Correct. Neither WiX's nor SC CREATE need or use the
Installer class. But, they can both install .NET based services whether
the service has an Installer based class or not.
From: Kevin Burton [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 05, 2007 12:54 PM
To: John Vottero; 'Don Tasanasan
The problem is that none if the "Installer" methods or events are getting
called. With InstallUtil the methods and events associated with the
Installer base class are call. With they are not. I would
assume that SC_CREATE would also not call the Installer base class methods.
From: [EMAIL PROTE
I don't think there's a difference between installing a .NET service vs
. a "regular" service so, ServiceInstall doesn't need to detect
anything. Can you install your service with SC CREATE?
The InstallUtil.exe doesn't know a service from a hole in the ground.
All it does is look for classes t
My apologies if this has already been answered, but I did skim all the
digests since the one this was in looking for an answer. With the caveat
that I setup the localization to the default (en-us), this works for me
(simplified here):
light -cultures:en-us -loc "lang\en-us\prod_en-us.wxl" -ext
How does ServiceInstall detect that you're installing a .net service as
opposed to a "regular" service?
I'm experiencing difficulties installing a .net service using
ServiceInstall. The service is there but doesn't seem to be registering
properly.
How does ServiceInstall work compared to th
Are there Wix 3 versions of the UI libs?
If so how can I integrate them into Visual Studio?
Justin Rockwood wrote:
>
> Using Votive you cannot target the Wix 2 stuff. You have to use Votive 2
> (supported on VS 2003) in order to target Wix 2.
>
>
>
> Justin
>
>
>
> From: [EMAIL PROTECTE
Isn't that your custom action is not scheduled correctly? I mean you should
instruct the system to create a port monitor once your 'monitor file' was
extracted from msi, right?
Dacian
- Original Message
From: Friedrich Dominicus <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Thanks for the response,
Actually I found out that the problem is due to one of my files that is
installed is not the correct size. The file is listed in ORCA as 204K but
when it is installed, the size is 36K. I am using a Merge Module and the
file that has problems is the first component in
Oh right,
It's Visual Studio 2005 i'm using.
Is there an editor for the WiX 2 stuff? intellisense etc, I'll probably have
to remove the Wix3 in order to get it to work with WiX 2 again!
Justin Rockwood wrote:
>
> Using Votive you cannot target the Wix 2 stuff. You have to use Votive 2
> (sup
Using Votive you cannot target the Wix 2 stuff. You have to use Votive 2
(supported on VS 2003) in order to target Wix 2.
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of learnerplates
Sent: Thursday, April 05, 2007 7:54 AM
To: wix-users@lists.sourceforge.net
Subject: [
Bob Arnson-3 wrote:
>
>
>
> Why are you specifying ExecuteAction? By placing it at sequence number
> 1, no other UI will run before it.
>
> --
> sig://boB
> http://bobs.org
>
>
>
Ok, I took that out, but I get the same result...no UI. I've been trying
different things (including not h
Ok, I took that out, but I get the same result...no UI. I've been
trying different things (including not having an InstallUISequence at
all) the past couple of days, but nothing seems to work.
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 05, 2007 9:
Hallquist Jr, Robert wrote:
I have created a WiX install of a .NET program and when it is run I
get a Microsoft Windows Error (the one that wants to send information
to Microsoft).
It's impossible to say without more details. What error do you get? If
you run the .exe from the command lin
Lars Lars wrote:
> Any reason why I receive these problems? The source files and configuration
> is unchanged, only trying to build on another computer than the one normally
> used.
>
A likely cause is different versions of WiX.
--
sig://boB
http://bobs.org
--
Scott Palmer wrote:
> That article indicates that Windows Installer is broken for
> per-machine installs as there is no way to specify that you must have
> a per-machine install that works on both XP and Vista.
ALLUSERS=1 does that. Pretend ALLUSERS=2 doesn't exist.
> My ultimate goal is to ins
JCWrs wrote:
>
>
>After="LaunchConditions"/>
>
>After="InstallLoc" />
>
>
Why are you specifying ExecuteAction? By placing
Jason Van Eaton wrote:
> I have a weird bug. When installing to the default path, uninstall works
> correctly. When installing to any other path, uninstall succeeds (that is to
> say there are no errors) but it forgets to remove the files. Even if I have
> a bug in my xml, it seems there must
Davut Karabay wrote:
> I was thinking creating two sets of s one for down level and one
> for Vista. Then adding s to each for detecting OS
> version, and install/not-install accordingly.
>
That'll work fine.
--
sig://boB
http://bobs.org
-
I've installed WiX 3 in order to get the Visual Studio integrated version.
It works fine, and I can use sourcesafe through Visual Studio.
Now I've just started to use the UI part of WiX, it's failing, I think the
installed WiXUI library in Visual Studio is from Version 2 and may have come
with th
Hi,
I'm currently having a problem with my installation package. I've got it
successfully creating a MSMQ queue, but the problem is that the queue may
already exist on the destination machine, and in such circumstances the
installation ends prematurely. I would want it to skip the creation of t
Hello,
> the dependency walker (depends.exe) shows an error saying that, "The
> side-by-side configuration information in the DLL contains errors". It
> fails to find the assembly DLLs (MFC80.dll, MSVCR80.dll, MSVCP80.dll)
> that *are* there in the WinSxS directory.
If they are installed, maybe
29 matches
Mail list logo
