Unfortunally, Windows Installer resolves this when creating the shortcut:
>From the doc:
The references are resolved to an actual path when the installer resolves
the working directory to create the shortcut.
-> http://msdn.microsoft.com/en-us/library/aa371847%28VS.85%29.aspx
Best regards,
Sebast
hi all,
well, it still does not work as the Launch condition still executed on
Uninstall.
I have tried "NOT Installed" and "OR Installed" within the condition and it
does not work.
i am using Wix 3.0.5419.0 and Votive with VS 2008.
Can someone maybe give me a sample code that work?
Thanks.
hi all,
well, it still does not work as the Launch condition still executed on
Uninstall.
I have tried "NOT Installed" within the condition and it does not work.
i am using Wix 3.0.5419.0 and Votive with VS 2008.
Can someone maybe give me a sample code that work?
Thanks.
Blair-2 wrote:
Hi All,
I want to create a shortcut and installed as per-machine.
Add I set the shortcut's working directory to %USERPROFILE%, with intension
to set the Start In with different values under differ users.
Unfortunately this value was resolved and wrote same value for all user.
Any ideas ho
If you are still looking for an answer to this, I faced a similar situation a
few months ago - the issue could be that the default working dir for the NT
service is something like windows\system32. You would need to set it right in
the code, so that the service executable can find the app.config
Word on the Christmas stuff. I got around it by programmatically
setting the endpoint configuration, so no need to dig further. Thanks
for the help though.
On Nov 22, 2009, at 5:47 PM, Christopher Painter
wrote:
> I'd have to spend some time on this to make sure I'm not wrong, but
> I th
I'd have to spend some time on this to make sure I'm not wrong, but I thought I
recalled putting together a windows service that exposed a WCF webservice and
that that when I did the endpoint (ABC's) was stored in the exe's app.config.
Again, I could be wrong as this isn't something I do every
So I tried having the App.config get installed to the same directory, but no
luck. Also, when using installutil.exe, you don't have to carry around the
app.config file. Strange.
Can you point me in the right direction for profiling? Not exactly sure
what you mean.
Thanks again,
James
On Sun,
InstallUtil truely is evil and the WiX way of doing things should work just
fine. I've installed dozens on .NET services this way.
The error message about no endpoints makes me wonder if your app.config is
getting installed. I'd do some profiling of the app to see whats going on.
Christopher
So I'm fairly new to WIX and I'm running into a problem that seems pervasive
on the web.
Basically, I have a .NET self-hosted WCF service inside of a windows
service. If I follow Msft's guidelines and add a installer class to the
Windows Service project, then run installutil.exe, everything works
10 matches
Mail list logo
