I've group of assemblies, one .exe service and two .dlls. The .dlls
are to be placed in the GAC prior to attempting to 'installUtil' the
service.
Unfortunately there doesn't appear to be any way to control the
ordering of installation of the folders using VS.Net2003 setup
project, and yep ... it chooses the wrong order despite knowing that
the dlls are dependencies of the exe.
Do I have to manually edit the MSI using Orca to affect this change or
is there some other way I can affect the installation order in the
project settings using VS.Net. If not this is very painful for
automatic builds.
Thanks if you can help,
Richard.
It seems mad that VS.Net can't do this and we're forced to circumnavigate
MSI in this way ... what's the point of having MSI ...?
Please tell me I'm missing something ... ?
R.
"Richard" <ric...@richardchandler.net> wrote in message
news:ca7c0c64.03051...@posting.google.com...
I'll now have to check the distribution rights to this utility and add .Net
version context sensetive code into my installation script.
Have I overlooked something simple here ... ?
It is bizarre that the easy to use GAC folder facility is provided quite
upfront by VS.Net but execution happens in the wrong order ... should I put
my service in the GAC too (surely not) ?
"Phil Wilson" <phil....@unisys.spamcom> wrote in message
news:%23y%23LzBLG...@TK2MSFTNGP12.phx.gbl...
Interestingly I was able to gac the assemblies then delete the original
files during the setup ...
I think I'm sorted now ... thanks.
R.
"Richard Chandler" <richard.cha...@mapson.monactive.com> wrote in
message news:OKFofdSG...@TK2MSFTNGP12.phx.gbl...