I think throwing an exception will do the trick...
I was hoping for something cleaner. When these class get run via InstallUtil, the exception get displayed etc. Not really what I
want most of the time.
>I think throwing an exception will do the trick...
>
[quoted text clipped - 11 lines]
>> KMSYS Worldwide, Inc.
>> http://www.kmsys.com
-------------------------------------------
Roy Chastain
KMSYS Worldwide, Inc.
http://www.kmsys.com
"Peter Huang" [MSFT] - 15 Sep 2005 07:41 GMT
Hi
I think Lloyd's suggestion is to try...catch.... the problem code, so if
there is any error occur, the exception will catch in the catch block, and
then you can do something to indicate the installation is failed. e.g.
write a file or popup a messagebox......
Best regards,
Peter Huang
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
Lloyd Dupont - 15 Sep 2005 08:20 GMT
Try to throw a System.Configuration.Install.InstallException instead.
That might fix it, perhaps...
>I was hoping for something cleaner. When these class get run via
>InstallUtil, the exception get displayed etc. Not really what I
[quoted text clipped - 21 lines]
> KMSYS Worldwide, Inc.
> http://www.kmsys.com