Rob R. Ainscough
7/7/2006 2:51:00 PM
I guess I'll have to add the code to the ProjectInstaller component -- so
technically I can do anything from VS 2005, but like you said, poor
documentation and very fragile.
We use InstallShield for other products, but the cost of IS (user licenses)
and support is not worth it IMHO and 95% of the time we have to perform
custom scripting in it -- so may as well use VS 2005 and code it.
I know I've been pretty critical of VS 2005 and rightly so in it's current
state (which really is a BETA not a final). But, if M$ can fix most of it
with an SP and update their documentation, they could possibly restore some
confidence in my company. At this point, if I don't see an SP1 for VS 2005
by Q3, then we're going to migrate to something else (serious evaluation of
Delphi and Java and dump are M$ all around including as a web platform also)
as we can't wait for VS 2007 to be "the fix". Knowing M$, VS 2007 will be
another rush out the door for Nov 2007 -- we can get most of our products
converted over to something else by then.
Thanks for your help Phil.
"Phil Wilson" <Phil.Wilson@unisys.spamcom> wrote in message
news:eIRSB9ToGHA.4124@TK2MSFTNGP03.phx.gbl...
> There are literally dozens of things that MSI does that VS setups don't
> support with IDE features, that's just one of them. VS setups have never
> been a fully-featured substitute for products from Wise, InstallShield,
> Advanced Installer, Wix.
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Rob R. Ainscough" <robains@pacbell.net> wrote in message
> news:%23fYinmSoGHA.4772@TK2MSFTNGP03.phx.gbl...
>> Any hints on how to accomplish this? I no MSI supports ForceReboot but
>> I'll be damn if I can find this option in VS 2005 deployment project?
>>
>> Thanks, Rob.
>>
>
>