RE: [ASCOM] Re: Need some help getting V5 installation to work
I have a V5 driver installing OK using Windows Installer, though not with the latest Platform 5 beta.
Usually when you see this error it means that your assembly references a type that is not installed on the target computer. Your best friend is the “Fusion Log Viewer” or FusLogVw.exe. Run FusLogVw and enable logging, then run your install and see if any errors appear in the log output. This might shed some light on what is not found.
Sorry I can't help directly. I'm on the client side of the operation at this point. But if it fails with the Inno installer maybe you could try building a VS2k5 installer and see if that's any different. If it works with the installer from VS then you can compare what the too installers do.
BTW, I presume you're using something like Virtual PC for testing so you don't have residual effects from prior installs.
PS, I am getting hooked on your approach to minimize the "usings..." in C#. Thanks for the tip.
From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On Behalf Of Chris Rowland
Sent: Thursday, November 29, 2007 4:16 AM
Subject: [ASCOM] Re: Need some help getting V5 installation to work
I'm still stuck on this.
I'll ask again in case it's been lost in the rush of PulseGuide
> I've been trying to get Version 5 C# based drivers to install for
> several weeks now off and on with no success. What happens is that
> I try to load the driver I get the "File does not exist" message
> far as I can see the offending file is the driver dll itself.
> This is doing an install on a different PC to the one used for the
> development, using the Inno Setup template. The target PC does not
> VS 2005 on it.
> If the application that is calling the driver is in the same folder
> it works but this is clearly not acceptable.
> I've seen this with the camera driver I've developed and also with
> test telescope driver built using the template with no changes.
> run on the development machine but not on another machine that
> have VS 2005 on it, except if the application is in the same folder.
> Does anyone have any ideas of what the problem might be?
> Has anyone managed to get a Version 5 driver installed and working
> different PC to the one it was developed on?
> What further information would be useful? I can post a couple of
> projects to the files area if this will help.
> Thanks for any help,
- But individual drivers might use many persistent parameters, and if
different versions of the same driver can coexist, they need to store
those parameters in different places. Is that a problem with the current
Chris L Peterson
----- Original Message -----
From: "Bob Denny" <rdenny@...>
Sent: Wednesday, December 19, 2007 1:11 PM
Subject: Re: [ASCOM] Re: Need some help getting V5 installation to work
> The only persistent storage used in platform components is the flag in
> Chooser that remembers whether a driver has ever had its SetupDialog()
> called. This info would survive updates to the platform and is
> It's only used to force the user to click (in the Chooser)
> Properties... before
> OK. Once the driver has been set up, the OK button is lit when that
> driver is
> chosen thereafter. This has worked well for 6 years.