RE: [OT] - killing a windows process?

["Steve Morgan" <steve@xxxxxxx>]

I presume you're talking about the COM interface. The only real option
is to use late binding.

1. Remove the reference to Homeseer

2. Change all the declarations to Homeseer COM classes to 'Object'

3. Instantiate Homeseer using either CreateObject or GetObject, not New

You'll lose Intellisense, because VB no longer knows what the types are,
but since you've already written the code, it's less of an issue.

I have to say, I'm really glad that I've given up VB and VC++ in favour
of C#.

Steve

> -----Original Message-----
> From: Paul Gordon [mailto:paul_gordon@xxxxxxx]
> Sent: 07 March 2003 15:42
> To: ukha_d@xxxxxxx
> Subject: RE: [ukha_d] [OT] - killing a windows process?
>
>
> OK.
>
> Looks like I sussed out the API call, as I now have my VB app
> killing the
> HomeSeer process with a TerminateProcess call...
>
> My next question regards what to do about about changing
> GUIDS for different
> versions of Homeseer.... - every time the version of Homeseer
> changes, my VB
> app breaks, - presumably because the registration of the GUID for the
> Homeseer.exe server is different? To fix it, I have to
> recompile my app with
> the new version of HomeSeer.exe installed and registered....
>
> Is there a way round this?


http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/