Skip to search.

Breaking News Visit Yahoo! News for the latest.

×Close this window

ASCOM-Talk · ASCOM Initiative Discussion List

The Yahoo! Groups Product Blog

Check it out!

Group Information

  • Members: 3668
  • Category: Astronomy
  • Founded: Nov 21, 2000
  • Language: English
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Hear how Yahoo! Groups has changed the lives of others. Take me there.

Messages

Advanced
Messages Help
Messages 21171 - 21200 of 29959   Oldest  |  < Older  |  Newer >  |  Newest
Messages: Show Message Summaries Sort by Date ^  
#21171 From: "drbarton11" <drbarton11@...>
Date: Thu Jul 1, 2010 4:53 am
Subject: Windows 7/Starry Night Pro/Celestron
drbarton11
Send Email Send Email
 
I recently purchased a Celestron 8SE telescope. I simultaneously purchased
Starry Night Pro to aid me in this hobby.

I installed the Nexstar remote program (NexRemote - Firmware NXS 4.18) on a
Windows 7 based laptop and connected the telescope with a serial port/usb
adapter (I had to download a generic driver).

The telescope responds to the Nexstar program without incidence.

When I try to connect the telescope to the Starry Night Pro program using
'ASCOM', I get the message, "MSComm - The device is not open".
I've tried changing the COM port, but get the same message.

I've tried restarting the program, shutting down the computer, turning on and
off the Nexstar handpiece, and restarting the NexRemote program, changing the
COM ports.

I've also downloaded and installed the latest ASCOM driver to my computer. Still
no resolve.

I'm not sure whether or not the serial cable is the issue or not - the cable
cost me $25.00 from a local computer shop. The fact that I can use that cable to
operate the NexRemote Software without incident tells me that the cable is
probably fine.

Any ideas? Thank you in advance!

#21172 From: "Tim Long" <Tim@...>
Date: Thu Jul 1, 2010 12:57 pm
Subject: RE: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
t_p_long
Send Email Send Email
 

If you do that... you’re on your own! We’ve got to be very careful about letting users do stuff like that because it will create confusion and a support nightmare.

 

ASCOM interfaces is (currently) a COM object that lives in the GAC. It should be installed by the platform installer and referenced from the COM tab of the references dialog.

--Tim

 

-----Original Message-----
From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On Behalf Of robt2112
Sent: 01 July 2010 02:20
To: ASCOM-Talk@yahoogroups.com
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

 

Well... If I copy the dll from my svn download to common files\ascom\.net then it shows up on my .NET references tab in VS. So I think the problem is the dll is not included in the install.

 

Robert

 

--- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@...> wrote:

> 

> Yes in windows\assembly it shows ASCOM.Interfaces that points to ASCOM.Interfaces.dll. The only thing that shows up in Visual Studio is a reference in COM to the tlb located in Program Files\Common Files\ASCOM\Interfaces.

>

> I do have a copy of the dll in the Platform Dependancies folder of the ASCOM platform Drivers and Simulators that I downloaded from SVN. The dll doesn't seem to get installed with the platform install.

>

> Robert

>

> --- In ASCOM-Talk@yahoogroups.com, "paulkccd" <yh@> wrote:

> >

> > As far as I can tell, platform 5 installs ASCOM.Interface.dll in GAC, not in Common Files\ASCOM. Check Windows\Assembly folder to see if it's there.

> >

> > Regards,

> >

> >     -Paul

> >

> > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:

> > >

> > > Slight correction. I installed Platform 5.0b then updated to 5.5.1. Both show installed in programs and features.

> > >

> > > Robert

> > >

> > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:

> > > >

> > > > Well I think what is wrong is the installer for 5.5.1. This is a brand new install. I havent installed any previous versions which are not available on the website. I just installed the latest version. The Interfaces dll was not installed.

> > > >

> > > > I believe if you had installed a previous platform version that dll would be there. Since I installed fresh it didn't get on my machine.

> > > >

> > > > Robert

> > > >

> > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:

> > > > >

> > > > > I'm assuming you have .NET 3.5 and ASCOM Platform 5.5.

> > > > >

> > > > > Paul is correct that it's a .NET assembly, but it is also a COM Primary

> > > > > Interop Assembly (PIA) so (confusingly) it show up under the COM tab as

> > > > > shown here:

> > > > >

> > > > > 

> > > > >

> > > > > So reference that, and also from the .NET tab, bring in the

> > > > > ASCOM.DriverAccess namespace thus:

> > > > >

> > > > > 

> > > > >

> > > > > Your project's references would then look something like this (I'm using

> > > > > C# in VS2010, yours may appear differently):

> > > > >

> > > > > 

> > > > >

> > > > > Then in visual studio, you can use some code like this to test:

> > > > >

> > > > > using System;

> > > > >

> > > > > using ASCOM.DriverAccess;

> > > > >

> > > > > 

> > > > >

> > > > > namespace ConsoleApplication1

> > > > >

> > > > > {

> > > > >

> > > > >     class Program

> > > > >

> > > > >     {

> > > > >

> > > > >         static void Main(string[] args)

> > > > >

> > > > >         {

> > > > >

> > > > >             var userChoice = Telescope.Choose(String.Empty);

> > > > >

> > > > >             var scope = new Telescope(userChoice);

> > > > >

> > > > >             scope.Connected = true;

> > > > >

> > > > >             scope.Park();

> > > > >

> > > > >             scope.Connected = false;

> > > > >

> > > > >             scope.Dispose();

> > > > >

> > > > >             scope = null;

> > > > >

> > > > >         }

> > > > >

> > > > >     }

> > > > >

> > > > > }

> > > > >

> > > > > 

> > > > >

> > > > > This code does work, I just ran it. If you can't get this to work, then

> > > > > something is badly wrong and needs sorting out.

> > > > >

> > > > > --Tim

> > > > >

> > > > > 

> > > > >

> > > > > > -----Original Message-----

> > > > >

> > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> > > > >

> > > > > > Talk@yahoogroups.com] On Behalf Of robt2112

> > > > >

> > > > > > Sent: 30 June 2010 20:53

> > > > >

> > > > > > To: ASCOM-Talk@yahoogroups.com

> > > > >

> > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

> > > > >

> > > > > >

> > > > >

> > > > > > It should be, but its not on my .NET assembly tab in visual studio. I

> > > > > only see it

> > > > >

> > > > > > on the COM tab. Looks like the install didnt not register something.

> > > > > This is a

> > > > >

> > > > > > new Win7 machine with a brand new ASCOM install.

> > > > >

> > > > > >

> > > > >

> > > > > > Robert

> > > > >

> > > > > >

> > > > >

> > > > > > --- In ASCOM-Talk@yahoogroups.com <mailto:ASCOM-Talk@yahoogroups.com>

> > > > > , "paulkccd" <yh@ <mailto:yh@> > wrote:

> > > > >

> > > > > > >

> > > > >

> > > > > > > ASCOM.Interfaces is a .NET assembly, not COM. You can add a

> > > > > reference

> > > > >

> > > > > > to it from the .NET tab in Visual Studio Add References dialog.

> > > > >

> > > > > > >

> > > > >

> > > > > > > Regards,

> > > > >

> > > > > > >

> > > > >

> > > > > > >     -Paul

> > > > >

> > > > > > >

> > > > >

> > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@> wrote:

> > > > >

> > > > > > > >

> > > > >

> > > > > > > > That is what I was trying. I cant get access to ITelescope. I

> > > > > added a

> > > > >

> > > > > > reference to DriverAccess and it complained that the interfaces were

> > > > > defined

> > > > >

> > > > > > in ASCOM.Interfaces. I added that reference from COM, but dont see a

> > > > > .NET

> > > > >

> > > > > > version. When I try to use ASCOM.ITelescope it complains it doesn't

> > > > > exist.

> > > > >

> > > > > > > >

> > > > >

> > > > > > > > It won't let you create an instance with Type Telescope. It says I

> > > > > must use

> > > > >

> > > > > > ITelescope.

> > > > >

> > > > > > > >

> > > > >

> > > > > > > > Robert

> > > > >

> > > > > > > >

> > > > >

> > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:

> > > > >

> > > > > > > > >

> > > > >

> > > > > > > > >

> > > > >

> > > > > > > > > And this is how I'd do it in C#:

> > > > >

> > > > > > > > >

> > > > >

> > > > > > > > >      ITelescope g;

> > > > >

> > > > > > > > >      g =

> > > > >

> > > > > > > > >

> > > > >

> > > > > > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM

> > > > >

> > > > > > > > > .Gemin\

> > > > >

> > > > > > > > > iTelescope.Telescope"));

> > > > >

> > > > > > > > >      g.Connected = true;

> > > > >

> > > > > > > > >

> > > > >

> > > > > > > > > Regards,

> > > > >

> > > > > > > > >

> > > > >

> > > > > > > > >       -Paul

> > > > >

> > > > > > > > >

> > > > >

> > > > > > > > >

> > > > >

> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > > > Rob, what error do you get? Here's sample VB.Net code I sent

> > > > > to

> > > > >

> > > > > > > > > > a

> > > > >

> > > > > > > > > Gemini

> > > > >

> > > > > > > > > > user:

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =

> > > > >

> > > > > > > > > > CreateObject("ASCOM.GeminiTelescope.Telescope")

> > > > >

> > > > > > > > > > g.Connected = True

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > > > You just need to add a reference ASCOM.Interfaces assembly.

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > > > Does this not work for you?

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > > > Regards,

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > > > -Paul

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" robt2112@ wrote:

> > > > >

> > > > > > > > > > >

> > > > >

> > > > > > > > > > > So this is basic question. How do I access and use an ASCOM

> > > > >

> > > > > > > > > > > driver

> > > > >

> > > > > > > > > in

> > > > >

> > > > > > > > > > .NET code. I keep running into cant create instances that

> > > > >

> > > > > > > > > > represent

> > > > >

> > > > > > > > > COM

> > > > >

> > > > > > > > > > components.

> > > > >

> > > > > > > > > > >

> > > > >

> > > > > > > > > > >

> > > > >

> > > > > > > > > > > Robert

> > > > >

> > > > > > > > > > >

> > > > >

> > > > > > > > > >

> > > > >

> > > > > > > > >

> > > > >

> > > > > > > >

> > > > >

> > > > > > >

> > > > >

> > > > > >

> > > > >

> > > > > >

> > > > >

> > > > > >

> > > > >

> > > > > >

> > > > >

> > > > > > ------------------------------------

> > > > >

> > > > > >

> > > > >

> > > > > > For more information see http://ASCOM-Standards.org/

> > > > > <http://ASCOM-Standards.org/> .

> > > > >

> > > > > >

> > > > >

> > > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU

> > > > >

> > > > > > USED TO SUBSCRIBE(!) to:

> > > > >

> > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> > > > >

> > > > > >

> > > > >

> > > > > > Yahoo! Groups Links

> > > > >

> > > > > >

> > > > >

> > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/

> > > > > <http://groups.yahoo.com/group/ASCOM-Talk/>

> > > > >

> > > > > >

> > > > >

> > > > > >     Individual Email | Traditional

> > > > >

> > > > > >

> > > > >

> > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join

> > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join>

> > > > >

> > > > > >     (Yahoo! ID required)

> > > > >

> > > > > >

> > > > >

> > > > > >     ASCOM-Talk-digest@yahoogroups.com

> > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com>

> > > > >

> > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com

> > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>

> > > > >

> > > > > >

> > > > >

> > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com

> > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> > > > >

> > > > > >

> > > > >

> > > > > >     http://docs.yahoo.com/info/terms/

> > > > > <http://docs.yahoo.com/info/terms/>

> > > > >

> > > > > 

> > > > >

> > > > >

> > > > > --

> > > > > ExchangeDefender Message Security: Click below to verify authenticity

> > > > > http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from=tim@

> > > > > Complete email hygeine and business continuity solution available from http://www.tigranetworks.co.uk

> > > > >

> > > >

> > >

> >

> 

 

 

 

 

------------------------------------

 

For more information see http://ASCOM-Standards.org/.

 

To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED TO SUBSCRIBE(!) to:

ASCOM-Talk-unsubscribe@yahoogroups.com

 

Yahoo! Groups Links

 

<*> To visit your group on the web, go to:

    http://groups.yahoo.com/group/ASCOM-Talk/

 

<*> Your email settings:

    Individual Email | Traditional

 

<*> To change settings online go to:

    http://groups.yahoo.com/group/ASCOM-Talk/join

    (Yahoo! ID required)

 

<*> To change settings via email:

    ASCOM-Talk-digest@yahoogroups.com

    ASCOM-Talk-fullfeatured@yahoogroups.com

 

<*> To unsubscribe from this group, send an email to:

    ASCOM-Talk-unsubscribe@yahoogroups.com

 

<*> Your use of Yahoo! Groups is subject to:

    http://docs.yahoo.com/info/terms/

 


ExchangeDefender Message Security: Check Authenticity
Complete email hygeine and business continuity solution available from TiGra Networks


#21173 From: "Tim Long" <Tim@...>
Date: Thu Jul 1, 2010 1:00 pm
Subject: RE: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
t_p_long
Send Email Send Email
 
The 5.5.1 installer is an upgrade install. It requires Platform 5.0a or
5.0b to be installed as a prerequisite. You cannot install 5.5.1 on its
own. If you did manage to do that, you should report it as a bug.

Regards,
--Tim Long


-----Original Message-----
From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
Behalf Of robt2112
Sent: 01 July 2010 00:06
To: ASCOM-Talk@yahoogroups.com
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

Well I think what is wrong is the installer for 5.5.1. This is a brand
new install. I havent installed any previous versions which are not
available on the website. I just installed the latest version. The
Interfaces dll was not installed.

I believe if you had installed a previous platform version that dll
would be there. Since I installed fresh it didn't get on my machine.

Robert

--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> I'm assuming you have .NET 3.5 and ASCOM Platform 5.5.
>
> Paul is correct that it's a .NET assembly, but it is also a COM
Primary
> Interop Assembly (PIA) so (confusingly) it show up under the COM tab
as
> shown here:
>
>
>
> So reference that, and also from the .NET tab, bring in the
> ASCOM.DriverAccess namespace thus:
>
>
>
> Your project's references would then look something like this (I'm
using
> C# in VS2010, yours may appear differently):
>
>
>
> Then in visual studio, you can use some code like this to test:
>
> using System;
>
> using ASCOM.DriverAccess;
>
>
>
> namespace ConsoleApplication1
>
> {
>
>     class Program
>
>     {
>
>         static void Main(string[] args)
>
>         {
>
>             var userChoice = Telescope.Choose(String.Empty);
>
>             var scope = new Telescope(userChoice);
>
>             scope.Connected = true;
>
>             scope.Park();
>
>             scope.Connected = false;
>
>             scope.Dispose();
>
>             scope = null;
>
>         }
>
>     }
>
> }
>
>
>
> This code does work, I just ran it. If you can't get this to work,
then
> something is badly wrong and needs sorting out.
>
> --Tim
>
>
>
> > -----Original Message-----
>
> > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > Talk@yahoogroups.com] On Behalf Of robt2112
>
> > Sent: 30 June 2010 20:53
>
> > To: ASCOM-Talk@yahoogroups.com
>
> > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
> >
>
> > It should be, but its not on my .NET assembly tab in visual studio.
I
> only see it
>
> > on the COM tab. Looks like the install didnt not register something.
> This is a
>
> > new Win7 machine with a brand new ASCOM install.
>
> >
>
> > Robert
>
> >
>
> > --- In ASCOM-Talk@yahoogroups.com
<mailto:ASCOM-Talk@yahoogroups.com>
> , "paulkccd" <yh@ <mailto:yh@> > wrote:
>
> > >
>
> > > ASCOM.Interfaces is a .NET assembly, not COM. You can add a
> reference
>
> > to it from the .NET tab in Visual Studio Add References dialog.
>
> > >
>
> > > Regards,
>
> > >
>
> > >     -Paul
>
> > >
>
> > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@> wrote:
>
> > > >
>
> > > > That is what I was trying. I cant get access to ITelescope. I
> added a
>
> > reference to DriverAccess and it complained that the interfaces were
> defined
>
> > in ASCOM.Interfaces. I added that reference from COM, but dont see a
> .NET
>
> > version. When I try to use ASCOM.ITelescope it complains it doesn't
> exist.
>
> > > >
>
> > > > It won't let you create an instance with Type Telescope. It says
I
> must use
>
> > ITelescope.
>
> > > >
>
> > > > Robert
>
> > > >
>
> > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:
>
> > > > >
>
> > > > >
>
> > > > > And this is how I'd do it in C#:
>
> > > > >
>
> > > > >      ITelescope g;
>
> > > > >      g =
>
> > > > >
>
> > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
>
> > > > > .Gemin\
>
> > > > > iTelescope.Telescope"));
>
> > > > >      g.Connected = true;
>
> > > > >
>
> > > > > Regards,
>
> > > > >
>
> > > > >       -Paul
>
> > > > >
>
> > > > >
>
> > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:
>
> > > > > >
>
> > > > > >
>
> > > > > > Rob, what error do you get? Here's sample VB.Net code I sent
> to
>
> > > > > > a
>
> > > > > Gemini
>
> > > > > > user:
>
> > > > > >
>
> > > > > > Dim g As ASCOM.Interface.ITelescope g =
>
> > > > > > CreateObject("ASCOM.GeminiTelescope.Telescope")
>
> > > > > > g.Connected = True
>
> > > > > >
>
> > > > > > You just need to add a reference ASCOM.Interfaces assembly.
>
> > > > > >
>
> > > > > > Does this not work for you?
>
> > > > > >
>
> > > > > > Regards,
>
> > > > > >
>
> > > > > > -Paul
>
> > > > > >
>
> > > > > >
>
> > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" robt2112@ wrote:
>
> > > > > > >
>
> > > > > > > So this is basic question. How do I access and use an
ASCOM
>
> > > > > > > driver
>
> > > > > in
>
> > > > > > .NET code. I keep running into cant create instances that
>
> > > > > > represent
>
> > > > > COM
>
> > > > > > components.
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > Robert
>
> > > > > > >
>
> > > > > >
>
> > > > >
>
> > > >
>
> > >
>
> >
>
> >
>
> >
>
> >
>
> > ------------------------------------
>
> >
>
> > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/> .
>
> >
>
> > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
>
> > USED TO SUBSCRIBE(!) to:
>
> > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> >
>
> > Yahoo! Groups Links
>
> >
>
> >     http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> >
>
> >     Individual Email | Traditional
>
> >
>
> >     http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> >     (Yahoo! ID required)
>
> >
>
> >     ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> >     ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> >
>
> >     ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> >
>
> >     http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/>
>
>
>
>
> --
> ExchangeDefender Message Security: Click below to verify authenticity
>
http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from=tim@..
.
> Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
>




------------------------------------

For more information see http://ASCOM-Standards.org/.

To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED
TO SUBSCRIBE(!) to:
ASCOM-Talk-unsubscribe@yahoogroups.com

Yahoo! Groups Links




--
ExchangeDefender Message Security: Click below to verify authenticity
http://www.exchangedefender.com/verify.asp?id=o61D3A30024465&from=tim@tigranetwo\
rks.co.uk
Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk

#21174 From: "robt2112" <robt2112@...>
Date: Thu Jul 1, 2010 1:57 pm
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
robt2112
Send Email Send Email
 
This was just a verification that it is a bug in the installer. The file should
have been installed. I verified that the file was missing and that putting the
file in place solves the problem. This should be fixed in the installation.

Robert

--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> If you do that... you're on your own! We've got to be very careful about
> letting users do stuff like that because it will create confusion and a
> support nightmare.
>
>
>
> ASCOM interfaces is (currently) a COM object that lives in the GAC. It
> should be installed by the platform installer and referenced from the
> COM tab of the references dialog.
>
> --Tim
>
>
>
> -----Original Message-----
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
> Behalf Of robt2112
> Sent: 01 July 2010 02:20
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
>
>
> Well... If I copy the dll from my svn download to common
> files\ascom\.net then it shows up on my .NET references tab in VS. So I
> think the problem is the dll is not included in the install.
>
>
>
> Robert
>
>
>
> --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
>
> >
>
> > Yes in windows\assembly it shows ASCOM.Interfaces that points to
> ASCOM.Interfaces.dll. The only thing that shows up in Visual Studio is a
> reference in COM to the tlb located in Program Files\Common
> Files\ASCOM\Interfaces.
>
> >
>
> > I do have a copy of the dll in the Platform Dependancies folder of the
> ASCOM platform Drivers and Simulators that I downloaded from SVN. The
> dll doesn't seem to get installed with the platform install.
>
> >
>
> > Robert
>
> >
>
> > --- In ASCOM-Talk@yahoogroups.com, "paulkccd" <yh@> wrote:
>
> > >
>
> > > As far as I can tell, platform 5 installs ASCOM.Interface.dll in
> GAC, not in Common Files\ASCOM. Check Windows\Assembly folder to see if
> it's there.
>
> > >
>
> > > Regards,
>
> > >
>
> > >     -Paul
>
> > >
>
> > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
>
> > > >
>
> > > > Slight correction. I installed Platform 5.0b then updated to
> 5.5.1. Both show installed in programs and features.
>
> > > >
>
> > > > Robert
>
> > > >
>
> > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
>
> > > > >
>
> > > > > Well I think what is wrong is the installer for 5.5.1. This is a
> brand new install. I havent installed any previous versions which are
> not available on the website. I just installed the latest version. The
> Interfaces dll was not installed.
>
> > > > >
>
> > > > > I believe if you had installed a previous platform version that
> dll would be there. Since I installed fresh it didn't get on my machine.
>
> > > > >
>
> > > > > Robert
>
> > > > >
>
> > > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
>
> > > > > >
>
> > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform 5.5.
>
> > > > > >
>
> > > > > > Paul is correct that it's a .NET assembly, but it is also a
> COM Primary
>
> > > > > > Interop Assembly (PIA) so (confusingly) it show up under the
> COM tab as
>
> > > > > > shown here:
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > So reference that, and also from the .NET tab, bring in the
>
> > > > > > ASCOM.DriverAccess namespace thus:
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > Your project's references would then look something like this
> (I'm using
>
> > > > > > C# in VS2010, yours may appear differently):
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > Then in visual studio, you can use some code like this to
> test:
>
> > > > > >
>
> > > > > > using System;
>
> > > > > >
>
> > > > > > using ASCOM.DriverAccess;
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > namespace ConsoleApplication1
>
> > > > > >
>
> > > > > > {
>
> > > > > >
>
> > > > > >     class Program
>
> > > > > >
>
> > > > > >     {
>
> > > > > >
>
> > > > > >         static void Main(string[] args)
>
> > > > > >
>
> > > > > >         {
>
> > > > > >
>
> > > > > >             var userChoice = Telescope.Choose(String.Empty);
>
> > > > > >
>
> > > > > >             var scope = new Telescope(userChoice);
>
> > > > > >
>
> > > > > >             scope.Connected = true;
>
> > > > > >
>
> > > > > >             scope.Park();
>
> > > > > >
>
> > > > > >             scope.Connected = false;
>
> > > > > >
>
> > > > > >             scope.Dispose();
>
> > > > > >
>
> > > > > >             scope = null;
>
> > > > > >
>
> > > > > >         }
>
> > > > > >
>
> > > > > >     }
>
> > > > > >
>
> > > > > > }
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > This code does work, I just ran it. If you can't get this to
> work, then
>
> > > > > > something is badly wrong and needs sorting out.
>
> > > > > >
>
> > > > > > --Tim
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > > -----Original Message-----
>
> > > > > >
>
> > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > > > > >
>
> > > > > > > Talk@yahoogroups.com] On Behalf Of robt2112
>
> > > > > >
>
> > > > > > > Sent: 30 June 2010 20:53
>
> > > > > >
>
> > > > > > > To: ASCOM-Talk@yahoogroups.com
>
> > > > > >
>
> > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in
> .NET
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > It should be, but its not on my .NET assembly tab in visual
> studio. I
>
> > > > > > only see it
>
> > > > > >
>
> > > > > > > on the COM tab. Looks like the install didnt not register
> something.
>
> > > > > > This is a
>
> > > > > >
>
> > > > > > > new Win7 machine with a brand new ASCOM install.
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > Robert
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > > > > , "paulkccd" <yh@ <mailto:yh@> > wrote:
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM. You can add
> a
>
> > > > > > reference
>
> > > > > >
>
> > > > > > > to it from the .NET tab in Visual Studio Add References
> dialog.
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > > > Regards,
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > > >     -Paul
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > > > --- In ASCOM-Talk@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@>
> wrote:
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > > > That is what I was trying. I cant get access to
> ITelescope. I
>
> > > > > > added a
>
> > > > > >
>
> > > > > > > reference to DriverAccess and it complained that the
> interfaces were
>
> > > > > > defined
>
> > > > > >
>
> > > > > > > in ASCOM.Interfaces. I added that reference from COM, but
> dont see a
>
> > > > > > .NET
>
> > > > > >
>
> > > > > > > version. When I try to use ASCOM.ITelescope it complains it
> doesn't
>
> > > > > > exist.
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > > > It won't let you create an instance with Type Telescope.
> It says I
>
> > > > > > must use
>
> > > > > >
>
> > > > > > > ITelescope.
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > > > Robert
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > And this is how I'd do it in C#:
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >      ITelescope g;
>
> > > > > >
>
> > > > > > > > > >      g =
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > >
> (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
>
> > > > > >
>
> > > > > > > > > > .Gemin\
>
> > > > > >
>
> > > > > > > > > > iTelescope.Telescope"));
>
> > > > > >
>
> > > > > > > > > >      g.Connected = true;
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > Regards,
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >       -Paul
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > Rob, what error do you get? Here's sample VB.Net
> code I sent
>
> > > > > > to
>
> > > > > >
>
> > > > > > > > > > > a
>
> > > > > >
>
> > > > > > > > > > Gemini
>
> > > > > >
>
> > > > > > > > > > > user:
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =
>
> > > > > >
>
> > > > > > > > > > > CreateObject("ASCOM.GeminiTelescope.Telescope")
>
> > > > > >
>
> > > > > > > > > > > g.Connected = True
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > You just need to add a reference ASCOM.Interfaces
> assembly.
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > Does this not work for you?
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > Regards,
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > -Paul
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" robt2112@
> wrote:
>
> > > > > >
>
> > > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > > So this is basic question. How do I access and use
> an ASCOM
>
> > > > > >
>
> > > > > > > > > > > > driver
>
> > > > > >
>
> > > > > > > > > > in
>
> > > > > >
>
> > > > > > > > > > > .NET code. I keep running into cant create instances
> that
>
> > > > > >
>
> > > > > > > > > > > represent
>
> > > > > >
>
> > > > > > > > > > COM
>
> > > > > >
>
> > > > > > > > > > > components.
>
> > > > > >
>
> > > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > > Robert
>
> > > > > >
>
> > > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > ------------------------------------
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > For more information see http://ASCOM-Standards.org/
>
> > > > > > <http://ASCOM-Standards.org/> .
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > To unsubscribe from this group, send an email FROM THE
> ACCOUNT YOU
>
> > > > > >
>
> > > > > > > USED TO SUBSCRIBE(!) to:
>
> > > > > >
>
> > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > Yahoo! Groups Links
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
>
> > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     Individual Email | Traditional
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
>
> > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> > > > > >
>
> > > > > > >     (Yahoo! ID required)
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     ASCOM-Talk-digest@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> > > > > >
>
> > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     http://docs.yahoo.com/info/terms/
>
> > > > > > <http://docs.yahoo.com/info/terms/>
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > --
>
> > > > > > ExchangeDefender Message Security: Click below to verify
> authenticity
>
> > > > > >
> http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from=tim@
>
> > > > > > Complete email hygeine and business continuity solution
> available from http://www.tigranetworks.co.uk
>
> > > > > >
>
> > > > >
>
> > > >
>
> > >
>
> >
>
>
>
>
>
>
>
>
>
> ------------------------------------
>
>
>
> For more information see http://ASCOM-Standards.org/.
>
>
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED
> TO SUBSCRIBE(!) to:
>
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
>
>
> Yahoo! Groups Links
>
>
>
>     http://groups.yahoo.com/group/ASCOM-Talk/
>
>
>
>     Individual Email | Traditional
>
>
>
>     http://groups.yahoo.com/group/ASCOM-Talk/join
>
>     (Yahoo! ID required)
>
>
>
>     ASCOM-Talk-digest@yahoogroups.com
>
>     ASCOM-Talk-fullfeatured@yahoogroups.com
>
>
>
>     ASCOM-Talk-unsubscribe@yahoogroups.com
>
>
>
>     http://docs.yahoo.com/info/terms/
>
>
>
>
> --
> ExchangeDefender Message Security: Click below to verify authenticity
> http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from=tim@...
> Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
>

#21175 From: "Chris" <chris_group_mail@...>
Date: Thu Jul 1, 2010 2:28 pm
Subject: Re: Windows 7/Starry Night Pro/Celestron
scope_sapiens
Send Email Send Email
 
There's quite a lot about connecting to SNP in AstroAnswers.

W7 32 or 64 bits?

What version numbers are you using with ASCOM and the Celestron driver? "The
Latest" just says it's the last one you know of.

If you can get NexRemote working you should be able to connect SNP to the
virtual Com port in NexRemote, select the COM port number reported at the base
of the NexRemote display. this eliminates questions of cables and USB to serial
port connections.

Otherwise, what cable are you using to connect to the scope? It must be one that
plugs into the base of the real HC.

The scope must be aligned before you connect.

Chris

--- In ASCOM-Talk@yahoogroups.com, "drbarton11" <drbarton11@...> wrote:
>
> I recently purchased a Celestron 8SE telescope. I simultaneously purchased
Starry Night Pro to aid me in this hobby.
>
> I installed the Nexstar remote program (NexRemote - Firmware NXS 4.18) on a
Windows 7 based laptop and connected the telescope with a serial port/usb
adapter (I had to download a generic driver).
>
> The telescope responds to the Nexstar program without incidence.
>
> When I try to connect the telescope to the Starry Night Pro program using
'ASCOM', I get the message, "MSComm - The device is not open".
> I've tried changing the COM port, but get the same message.
>
> I've tried restarting the program, shutting down the computer, turning on and
off the Nexstar handpiece, and restarting the NexRemote program, changing the
COM ports.
>
> I've also downloaded and installed the latest ASCOM driver to my computer.
Still no resolve.
>
> I'm not sure whether or not the serial cable is the issue or not - the cable
cost me $25.00 from a local computer shop. The fact that I can use that cable to
operate the NexRemote Software without incident tells me that the cable is
probably fine.
>
> Any ideas? Thank you in advance!
>

#21176 From: "Tim Long" <Tim@...>
Date: Thu Jul 1, 2010 2:43 pm
Subject: RE: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
t_p_long
Send Email Send Email
 
I find it hard to believe that the problem is what you say it is. The
interfaces PIA is so fundamental to ASCOM that we would have caught that
a long time ago. Can we please be clear about version numbers - when you
say "the installer" which version are you talking about?

To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not both). The
5.0a/b installer includes and installs the interfaces PIA in the GAC, I
am 100% certain that works correctly because it has been tested to death
on many different systems, by all the ASCOM developers and beta testers
and on many end user systems.

Something about this incident doesn't make sense. I would like to get to
the bottom of it, but I don't think it is a bug in the installer.

Regards,
--Tim Long


-----Original Message-----
From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
Behalf Of robt2112
Sent: 01 July 2010 14:57
To: ASCOM-Talk@yahoogroups.com
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

This was just a verification that it is a bug in the installer. The file
should have been installed. I verified that the file was missing and
that putting the file in place solves the problem. This should be fixed
in the installation.

Robert

--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> If you do that... you're on your own! We've got to be very careful
about
> letting users do stuff like that because it will create confusion and
a
> support nightmare.
>
>
>
> ASCOM interfaces is (currently) a COM object that lives in the GAC. It
> should be installed by the platform installer and referenced from the
> COM tab of the references dialog.
>
> --Tim
>
>
>
> -----Original Message-----
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com]
On
> Behalf Of robt2112
> Sent: 01 July 2010 02:20
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
>
>
> Well... If I copy the dll from my svn download to common
> files\ascom\.net then it shows up on my .NET references tab in VS. So
I
> think the problem is the dll is not included in the install.
>
>
>
> Robert
>
>
>
> --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
>
> >
>
> > Yes in windows\assembly it shows ASCOM.Interfaces that points to
> ASCOM.Interfaces.dll. The only thing that shows up in Visual Studio is
a
> reference in COM to the tlb located in Program Files\Common
> Files\ASCOM\Interfaces.
>
> >
>
> > I do have a copy of the dll in the Platform Dependancies folder of
the
> ASCOM platform Drivers and Simulators that I downloaded from SVN. The
> dll doesn't seem to get installed with the platform install.
>
> >
>
> > Robert
>
> >
>
> > --- In ASCOM-Talk@yahoogroups.com, "paulkccd" <yh@> wrote:
>
> > >
>
> > > As far as I can tell, platform 5 installs ASCOM.Interface.dll in
> GAC, not in Common Files\ASCOM. Check Windows\Assembly folder to see
if
> it's there.
>
> > >
>
> > > Regards,
>
> > >
>
> > >     -Paul
>
> > >
>
> > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
>
> > > >
>
> > > > Slight correction. I installed Platform 5.0b then updated to
> 5.5.1. Both show installed in programs and features.
>
> > > >
>
> > > > Robert
>
> > > >
>
> > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
>
> > > > >
>
> > > > > Well I think what is wrong is the installer for 5.5.1. This is
a
> brand new install. I havent installed any previous versions which are
> not available on the website. I just installed the latest version. The
> Interfaces dll was not installed.
>
> > > > >
>
> > > > > I believe if you had installed a previous platform version
that
> dll would be there. Since I installed fresh it didn't get on my
machine.
>
> > > > >
>
> > > > > Robert
>
> > > > >
>
> > > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
>
> > > > > >
>
> > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform 5.5.
>
> > > > > >
>
> > > > > > Paul is correct that it's a .NET assembly, but it is also a
> COM Primary
>
> > > > > > Interop Assembly (PIA) so (confusingly) it show up under the
> COM tab as
>
> > > > > > shown here:
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > So reference that, and also from the .NET tab, bring in the
>
> > > > > > ASCOM.DriverAccess namespace thus:
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > Your project's references would then look something like
this
> (I'm using
>
> > > > > > C# in VS2010, yours may appear differently):
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > Then in visual studio, you can use some code like this to
> test:
>
> > > > > >
>
> > > > > > using System;
>
> > > > > >
>
> > > > > > using ASCOM.DriverAccess;
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > namespace ConsoleApplication1
>
> > > > > >
>
> > > > > > {
>
> > > > > >
>
> > > > > >     class Program
>
> > > > > >
>
> > > > > >     {
>
> > > > > >
>
> > > > > >         static void Main(string[] args)
>
> > > > > >
>
> > > > > >         {
>
> > > > > >
>
> > > > > >             var userChoice = Telescope.Choose(String.Empty);
>
> > > > > >
>
> > > > > >             var scope = new Telescope(userChoice);
>
> > > > > >
>
> > > > > >             scope.Connected = true;
>
> > > > > >
>
> > > > > >             scope.Park();
>
> > > > > >
>
> > > > > >             scope.Connected = false;
>
> > > > > >
>
> > > > > >             scope.Dispose();
>
> > > > > >
>
> > > > > >             scope = null;
>
> > > > > >
>
> > > > > >         }
>
> > > > > >
>
> > > > > >     }
>
> > > > > >
>
> > > > > > }
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > This code does work, I just ran it. If you can't get this to
> work, then
>
> > > > > > something is badly wrong and needs sorting out.
>
> > > > > >
>
> > > > > > --Tim
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > > -----Original Message-----
>
> > > > > >
>
> > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > > > > >
>
> > > > > > > Talk@yahoogroups.com] On Behalf Of robt2112
>
> > > > > >
>
> > > > > > > Sent: 30 June 2010 20:53
>
> > > > > >
>
> > > > > > > To: ASCOM-Talk@yahoogroups.com
>
> > > > > >
>
> > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in
> .NET
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > It should be, but its not on my .NET assembly tab in
visual
> studio. I
>
> > > > > > only see it
>
> > > > > >
>
> > > > > > > on the COM tab. Looks like the install didnt not register
> something.
>
> > > > > > This is a
>
> > > > > >
>
> > > > > > > new Win7 machine with a brand new ASCOM install.
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > Robert
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > > > > , "paulkccd" <yh@ <mailto:yh@> > wrote:
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM. You can
add
> a
>
> > > > > > reference
>
> > > > > >
>
> > > > > > > to it from the .NET tab in Visual Studio Add References
> dialog.
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > > > Regards,
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > > >     -Paul
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > > > --- In ASCOM-Talk@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@>
> wrote:
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > > > That is what I was trying. I cant get access to
> ITelescope. I
>
> > > > > > added a
>
> > > > > >
>
> > > > > > > reference to DriverAccess and it complained that the
> interfaces were
>
> > > > > > defined
>
> > > > > >
>
> > > > > > > in ASCOM.Interfaces. I added that reference from COM, but
> dont see a
>
> > > > > > .NET
>
> > > > > >
>
> > > > > > > version. When I try to use ASCOM.ITelescope it complains
it
> doesn't
>
> > > > > > exist.
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > > > It won't let you create an instance with Type
Telescope.
> It says I
>
> > > > > > must use
>
> > > > > >
>
> > > > > > > ITelescope.
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > > > Robert
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
wrote:
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > And this is how I'd do it in C#:
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >      ITelescope g;
>
> > > > > >
>
> > > > > > > > > >      g =
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > >
> (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
>
> > > > > >
>
> > > > > > > > > > .Gemin\
>
> > > > > >
>
> > > > > > > > > > iTelescope.Telescope"));
>
> > > > > >
>
> > > > > > > > > >      g.Connected = true;
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > Regards,
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >       -Paul
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
wrote:
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > Rob, what error do you get? Here's sample VB.Net
> code I sent
>
> > > > > > to
>
> > > > > >
>
> > > > > > > > > > > a
>
> > > > > >
>
> > > > > > > > > > Gemini
>
> > > > > >
>
> > > > > > > > > > > user:
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =
>
> > > > > >
>
> > > > > > > > > > > CreateObject("ASCOM.GeminiTelescope.Telescope")
>
> > > > > >
>
> > > > > > > > > > > g.Connected = True
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > You just need to add a reference ASCOM.Interfaces
> assembly.
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > Does this not work for you?
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > Regards,
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > -Paul
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" robt2112@
> wrote:
>
> > > > > >
>
> > > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > > So this is basic question. How do I access and
use
> an ASCOM
>
> > > > > >
>
> > > > > > > > > > > > driver
>
> > > > > >
>
> > > > > > > > > > in
>
> > > > > >
>
> > > > > > > > > > > .NET code. I keep running into cant create
instances
> that
>
> > > > > >
>
> > > > > > > > > > > represent
>
> > > > > >
>
> > > > > > > > > > COM
>
> > > > > >
>
> > > > > > > > > > > components.
>
> > > > > >
>
> > > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > > > Robert
>
> > > > > >
>
> > > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > > >
>
> > > > > >
>
> > > > > > > > > >
>
> > > > > >
>
> > > > > > > > >
>
> > > > > >
>
> > > > > > > >
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > ------------------------------------
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > For more information see http://ASCOM-Standards.org/
>
> > > > > > <http://ASCOM-Standards.org/> .
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > To unsubscribe from this group, send an email FROM THE
> ACCOUNT YOU
>
> > > > > >
>
> > > > > > > USED TO SUBSCRIBE(!) to:
>
> > > > > >
>
> > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > > Yahoo! Groups Links
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
>
> > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     Individual Email | Traditional
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
>
> > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> > > > > >
>
> > > > > > >     (Yahoo! ID required)
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     ASCOM-Talk-digest@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> > > > > >
>
> > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
>
> > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > > > >
>
> > > > > > >
>
> > > > > >
>
> > > > > > >     http://docs.yahoo.com/info/terms/
>
> > > > > > <http://docs.yahoo.com/info/terms/>
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > --
>
> > > > > > ExchangeDefender Message Security: Click below to verify
> authenticity
>
> > > > > >
> http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from=tim@
>
> > > > > > Complete email hygeine and business continuity solution
> available from http://www.tigranetworks.co.uk
>
> > > > > >
>
> > > > >
>
> > > >
>
> > >
>
> >
>
>
>
>
>
>
>
>
>
> ------------------------------------
>
>
>
> For more information see http://ASCOM-Standards.org/.
>
>
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
USED
> TO SUBSCRIBE(!) to:
>
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
>
>
> Yahoo! Groups Links
>
>
>
>     http://groups.yahoo.com/group/ASCOM-Talk/
>
>
>
>     Individual Email | Traditional
>
>
>
>     http://groups.yahoo.com/group/ASCOM-Talk/join
>
>     (Yahoo! ID required)
>
>
>
>     ASCOM-Talk-digest@yahoogroups.com
>
>     ASCOM-Talk-fullfeatured@yahoogroups.com
>
>
>
>     ASCOM-Talk-unsubscribe@yahoogroups.com
>
>
>
>     http://docs.yahoo.com/info/terms/
>
>
>
>
> --
> ExchangeDefender Message Security: Click below to verify authenticity
>
http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from=tim@..
.
> Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
>




------------------------------------

For more information see http://ASCOM-Standards.org/.

To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED
TO SUBSCRIBE(!) to:
ASCOM-Talk-unsubscribe@yahoogroups.com

Yahoo! Groups Links




--
ExchangeDefender Message Security: Click below to verify authenticity
http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from=tim@tigranetwo\
rks.co.uk
Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk

#21177 From: "Chris" <chris_group_mail@...>
Date: Thu Jul 1, 2010 2:47 pm
Subject: Re: [ASCOM] Temperature compensated focusing issues
scope_sapiens
Send Email Send Email
 
It's not a perfect protocol.

It seems to be implementing an absolute focuser with a relative temperature
control; the position read when temperature compensation is on changes as the
temperature changes even though the focus doesn't.  This means that the value
you set to get a particular focus will change as the temperature changes.

An ideal focuser would return a fixed value as the temperature changed, the user
would set this value and the focuser would compensate for the temperature and
set the real value.

The algorithm would be:

CompensatedPosition = Position + Temperature * TempCoefficient
or
Position = CompensatedPosition - Temperature * TempCoefficient

One possibility would be to make a CompensatedFocuser driver as a shim that
applies this to a real focuser driver. It would read the position and
temperature from the real driver and adjust the position appropriately. It would
allow moves while temperature compensation was active.

Another way would be to add a CompensatedPosition to the focuser definition;
this would need agreement that we should extend the focuser definition and
commitment from driver authors and application developers that they will use it.

It looks as if it would be best to do the first option first, it should get Tom
going and demonstrate that it works - or not.

I'll try to have a go at this but don't hold your breath - and if anyone wants
to try to beat me to it they are very welcome!

Chris


--- In ASCOM-Talk@yahoogroups.com, "Chris Peterson" <cpeterson@...> wrote:
>
> The focuser interface probably doesn't need to be changed radically. Perhaps
> a new read-only property, CanMoveWhileAF(). If this is true, Move() won't
> return an error, otherwise it will (the current behavior).
>
> It seems contrary to the ASCOM philosophy to expose details of the
> temperature compensation logic itself. That should all happen invisibly in
> either the driver or the hardware itself.
>
> Chris
>
> *****************************************
> Chris L Peterson
> Cloudbait Observatory
> http://www.cloudbait.com
>
>
> ----- Original Message -----
> From: "Pierre de Ponthiere" <pierredeponthiere@...>
> To: <ASCOM-Talk@yahoogroups.com>
> Sent: Wednesday, June 30, 2010 3:19 PM
> Subject: Re: [ASCOM] Temperature compensated focusing issues
>
>
> Hi Tom,
> I am using a digital Finger Lake Instrument focuser DF2
> This focuser having no temperature compensation, I added a temperature
> sensor and I had modified the ASCOM driver to have an open loop temperature
> compensation.
>
> To cope the "filter offset" problem you mention, I added an additional class
> "Focuser Control" which has a principal method "SetReferences" with two
> parameters
> PositionReferenceValue and TemperatureReferenceValue.
> The temperature compensation algorithm uses those two values and the current
> temperature to calculate the new focus position.
>
> After an Autofocus, my custom control program (similar to ACP) records the
> Focus position and temperature as PositionReferenceValue and
> TemperatureReferenceValue .
> When a filter change occurs, the PositionReferenceValue is modified in
> accordance with the filter offset.
>
> This additional class is not defined by ASCOM, but I my opinion without it
> is impossible to cope the problem you mention. Indeed the ASCOM Focuser
> Interface does take the filter offset into account.
>
> ASCOM community should improve the Focuser Interface to cope this problem.
>
> Clear skies,
> Pierre
>

#21178 From: "Tom" <tom_krajci@...>
Date: Thu Jul 1, 2010 3:56 pm
Subject: Re: Temperature compensated focusing issues
tom_krajci
Send Email Send Email
 
--- In ASCOM-Talk@yahoogroups.com, "Chris" <chris_group_mail@...> wrote:

> It seems to be implementing an absolute focuser with a relative
> temperature control; the position read when temperature
> compensation is on changes as the temperature changes even though
> the focus doesn't.  This means that the value you set to get a
> particular focus will change as the temperature changes.

Yes, I do make an important assumption...that focus shift/behavior in the
overall system changes in a linear fashion as temperature changes.

That's a pretty good assumption when your scope is 'small'...it equilibriates
pretty rapidly with changing air temperature.  It's not a good assumption with a
bigger scope...such as the 12-inch LX-200 classic...with its four-pound pig iron
ring behind the main mirror (I presume for balance/fork arm length
considerations).  In that case it would be helpful to modify the OTA to make it
equilibriate faster.  (I take out such weights, and aggressively ventilate the
OTA.)

>
> An ideal focuser would return a fixed value as the temperature changed, the
user would set this value and the focuser would compensate for the temperature
and set the real value.
>
> The algorithm would be:
>
> CompensatedPosition = Position + Temperature * TempCoefficient
> or
> Position = CompensatedPosition - Temperature * TempCoefficient

As long it can also incorporate filter offsets (or at least not prevent their
use), then it sounds like a change for the better.

> It looks as if it would be best to do the first option first, it
> should get Tom going and demonstrate that it works - or not.
>
> I'll try to have a go at this but don't hold your breath - and if
> anyone wants to try to beat me to it they are very welcome!

Monsoon is establishing in the Southwest US.  After a few more days of
clouds/rain, I'll haul all gear into the basement so it's not a lightning
magnet.  My observing season will start again sometime in September...depending
on how monsoon behaves.

But it's also a time for maintenance and indoor testing.  For the next couple
months I'm more than happy to do what I can with simulators, dial gauges, etc.

Thank you!

--
-------------------------------------------
Tom Krajci
Cloudcroft, New Mexico
http://picasaweb.google.com/tom.krajci

Center for Backyard Astrophysics (CBA)
http://cbastro.org/ CBA New Mexico

American Association of Variable Star
Observers (AAVSO): KTC http://www.aavso.org/
-------------------------------------------

#21179 From: "robt2112" <robt2112@...>
Date: Thu Jul 1, 2010 4:19 pm
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
robt2112
Send Email Send Email
 
This was a fresh computer nothing installed. 5.0b first then update to 5.5.1.
The COM interfaces were installed with the tlb file in the ASCOM folder. The
.net dll was missing in the .net folder.

Robert

--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> I find it hard to believe that the problem is what you say it is. The
> interfaces PIA is so fundamental to ASCOM that we would have caught that
> a long time ago. Can we please be clear about version numbers - when you
> say "the installer" which version are you talking about?
>
> To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not both). The
> 5.0a/b installer includes and installs the interfaces PIA in the GAC, I
> am 100% certain that works correctly because it has been tested to death
> on many different systems, by all the ASCOM developers and beta testers
> and on many end user systems.
>
> Something about this incident doesn't make sense. I would like to get to
> the bottom of it, but I don't think it is a bug in the installer.
>
> Regards,
> --Tim Long
>
>
> -----Original Message-----
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
> Behalf Of robt2112
> Sent: 01 July 2010 14:57
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
> This was just a verification that it is a bug in the installer. The file
> should have been installed. I verified that the file was missing and
> that putting the file in place solves the problem. This should be fixed
> in the installation.
>
> Robert
>
> --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> >
> > If you do that... you're on your own! We've got to be very careful
> about
> > letting users do stuff like that because it will create confusion and
> a
> > support nightmare.
> >
> >
> >
> > ASCOM interfaces is (currently) a COM object that lives in the GAC. It
> > should be installed by the platform installer and referenced from the
> > COM tab of the references dialog.
> >
> > --Tim
> >
> >
> >
> > -----Original Message-----
> > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com]
> On
> > Behalf Of robt2112
> > Sent: 01 July 2010 02:20
> > To: ASCOM-Talk@yahoogroups.com
> > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> >
> >
> >
> > Well... If I copy the dll from my svn download to common
> > files\ascom\.net then it shows up on my .NET references tab in VS. So
> I
> > think the problem is the dll is not included in the install.
> >
> >
> >
> > Robert
> >
> >
> >
> > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
> >
> > >
> >
> > > Yes in windows\assembly it shows ASCOM.Interfaces that points to
> > ASCOM.Interfaces.dll. The only thing that shows up in Visual Studio is
> a
> > reference in COM to the tlb located in Program Files\Common
> > Files\ASCOM\Interfaces.
> >
> > >
> >
> > > I do have a copy of the dll in the Platform Dependancies folder of
> the
> > ASCOM platform Drivers and Simulators that I downloaded from SVN. The
> > dll doesn't seem to get installed with the platform install.
> >
> > >
> >
> > > Robert
> >
> > >
> >
> > > --- In ASCOM-Talk@yahoogroups.com, "paulkccd" <yh@> wrote:
> >
> > > >
> >
> > > > As far as I can tell, platform 5 installs ASCOM.Interface.dll in
> > GAC, not in Common Files\ASCOM. Check Windows\Assembly folder to see
> if
> > it's there.
> >
> > > >
> >
> > > > Regards,
> >
> > > >
> >
> > > >     -Paul
> >
> > > >
> >
> > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
> >
> > > > >
> >
> > > > > Slight correction. I installed Platform 5.0b then updated to
> > 5.5.1. Both show installed in programs and features.
> >
> > > > >
> >
> > > > > Robert
> >
> > > > >
> >
> > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
> >
> > > > > >
> >
> > > > > > Well I think what is wrong is the installer for 5.5.1. This is
> a
> > brand new install. I havent installed any previous versions which are
> > not available on the website. I just installed the latest version. The
> > Interfaces dll was not installed.
> >
> > > > > >
> >
> > > > > > I believe if you had installed a previous platform version
> that
> > dll would be there. Since I installed fresh it didn't get on my
> machine.
> >
> > > > > >
> >
> > > > > > Robert
> >
> > > > > >
> >
> > > > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> >
> > > > > > >
> >
> > > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform 5.5.
> >
> > > > > > >
> >
> > > > > > > Paul is correct that it's a .NET assembly, but it is also a
> > COM Primary
> >
> > > > > > > Interop Assembly (PIA) so (confusingly) it show up under the
> > COM tab as
> >
> > > > > > > shown here:
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > So reference that, and also from the .NET tab, bring in the
> >
> > > > > > > ASCOM.DriverAccess namespace thus:
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > Your project's references would then look something like
> this
> > (I'm using
> >
> > > > > > > C# in VS2010, yours may appear differently):
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > Then in visual studio, you can use some code like this to
> > test:
> >
> > > > > > >
> >
> > > > > > > using System;
> >
> > > > > > >
> >
> > > > > > > using ASCOM.DriverAccess;
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > namespace ConsoleApplication1
> >
> > > > > > >
> >
> > > > > > > {
> >
> > > > > > >
> >
> > > > > > >     class Program
> >
> > > > > > >
> >
> > > > > > >     {
> >
> > > > > > >
> >
> > > > > > >         static void Main(string[] args)
> >
> > > > > > >
> >
> > > > > > >         {
> >
> > > > > > >
> >
> > > > > > >             var userChoice = Telescope.Choose(String.Empty);
> >
> > > > > > >
> >
> > > > > > >             var scope = new Telescope(userChoice);
> >
> > > > > > >
> >
> > > > > > >             scope.Connected = true;
> >
> > > > > > >
> >
> > > > > > >             scope.Park();
> >
> > > > > > >
> >
> > > > > > >             scope.Connected = false;
> >
> > > > > > >
> >
> > > > > > >             scope.Dispose();
> >
> > > > > > >
> >
> > > > > > >             scope = null;
> >
> > > > > > >
> >
> > > > > > >         }
> >
> > > > > > >
> >
> > > > > > >     }
> >
> > > > > > >
> >
> > > > > > > }
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > This code does work, I just ran it. If you can't get this to
> > work, then
> >
> > > > > > > something is badly wrong and needs sorting out.
> >
> > > > > > >
> >
> > > > > > > --Tim
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > > -----Original Message-----
> >
> > > > > > >
> >
> > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> >
> > > > > > >
> >
> > > > > > > > Talk@yahoogroups.com] On Behalf Of robt2112
> >
> > > > > > >
> >
> > > > > > > > Sent: 30 June 2010 20:53
> >
> > > > > > >
> >
> > > > > > > > To: ASCOM-Talk@yahoogroups.com
> >
> > > > > > >
> >
> > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in
> > .NET
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > It should be, but its not on my .NET assembly tab in
> visual
> > studio. I
> >
> > > > > > > only see it
> >
> > > > > > >
> >
> > > > > > > > on the COM tab. Looks like the install didnt not register
> > something.
> >
> > > > > > > This is a
> >
> > > > > > >
> >
> > > > > > > > new Win7 machine with a brand new ASCOM install.
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > Robert
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com>
> >
> > > > > > > , "paulkccd" <yh@ <mailto:yh@> > wrote:
> >
> > > > > > >
> >
> > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM. You can
> add
> > a
> >
> > > > > > > reference
> >
> > > > > > >
> >
> > > > > > > > to it from the .NET tab in Visual Studio Add References
> > dialog.
> >
> > > > > > >
> >
> > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > Regards,
> >
> > > > > > >
> >
> > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > >     -Paul
> >
> > > > > > >
> >
> > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> >
> > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@>
> > wrote:
> >
> > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > That is what I was trying. I cant get access to
> > ITelescope. I
> >
> > > > > > > added a
> >
> > > > > > >
> >
> > > > > > > > reference to DriverAccess and it complained that the
> > interfaces were
> >
> > > > > > > defined
> >
> > > > > > >
> >
> > > > > > > > in ASCOM.Interfaces. I added that reference from COM, but
> > dont see a
> >
> > > > > > > .NET
> >
> > > > > > >
> >
> > > > > > > > version. When I try to use ASCOM.ITelescope it complains
> it
> > doesn't
> >
> > > > > > > exist.
> >
> > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > It won't let you create an instance with Type
> Telescope.
> > It says I
> >
> > > > > > > must use
> >
> > > > > > >
> >
> > > > > > > > ITelescope.
> >
> > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > Robert
> >
> > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> >
> > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
> wrote:
> >
> > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > And this is how I'd do it in C#:
> >
> > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > >      ITelescope g;
> >
> > > > > > >
> >
> > > > > > > > > > >      g =
> >
> > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >
> > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
> >
> > > > > > >
> >
> > > > > > > > > > > .Gemin\
> >
> > > > > > >
> >
> > > > > > > > > > > iTelescope.Telescope"));
> >
> > > > > > >
> >
> > > > > > > > > > >      g.Connected = true;
> >
> > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > Regards,
> >
> > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > >       -Paul
> >
> > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> >
> > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
> wrote:
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > Rob, what error do you get? Here's sample VB.Net
> > code I sent
> >
> > > > > > > to
> >
> > > > > > >
> >
> > > > > > > > > > > > a
> >
> > > > > > >
> >
> > > > > > > > > > > Gemini
> >
> > > > > > >
> >
> > > > > > > > > > > > user:
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =
> >
> > > > > > >
> >
> > > > > > > > > > > > CreateObject("ASCOM.GeminiTelescope.Telescope")
> >
> > > > > > >
> >
> > > > > > > > > > > > g.Connected = True
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > You just need to add a reference ASCOM.Interfaces
> > assembly.
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > Does this not work for you?
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > Regards,
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > -Paul
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> >
> > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" robt2112@
> > wrote:
> >
> > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > > So this is basic question. How do I access and
> use
> > an ASCOM
> >
> > > > > > >
> >
> > > > > > > > > > > > > driver
> >
> > > > > > >
> >
> > > > > > > > > > > in
> >
> > > > > > >
> >
> > > > > > > > > > > > .NET code. I keep running into cant create
> instances
> > that
> >
> > > > > > >
> >
> > > > > > > > > > > > represent
> >
> > > > > > >
> >
> > > > > > > > > > > COM
> >
> > > > > > >
> >
> > > > > > > > > > > > components.
> >
> > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > > > Robert
> >
> > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > ------------------------------------
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > For more information see http://ASCOM-Standards.org/
> >
> > > > > > > <http://ASCOM-Standards.org/> .
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > To unsubscribe from this group, send an email FROM THE
> > ACCOUNT YOU
> >
> > > > > > >
> >
> > > > > > > > USED TO SUBSCRIBE(!) to:
> >
> > > > > > >
> >
> > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> >
> > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > > Yahoo! Groups Links
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> >
> > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/>
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >     Individual Email | Traditional
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> >
> > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> >
> > > > > > >
> >
> > > > > > > >     (Yahoo! ID required)
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> >
> > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> >
> > > > > > >
> >
> > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> >
> > > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> >
> > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > > > > > >
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > > >     http://docs.yahoo.com/info/terms/
> >
> > > > > > > <http://docs.yahoo.com/info/terms/>
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > --
> >
> > > > > > > ExchangeDefender Message Security: Click below to verify
> > authenticity
> >
> > > > > > >
> > http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from=tim@
> >
> > > > > > > Complete email hygeine and business continuity solution
> > available from http://www.tigranetworks.co.uk
> >
> > > > > > >
> >
> > > > > >
> >
> > > > >
> >
> > > >
> >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ------------------------------------
> >
> >
> >
> > For more information see http://ASCOM-Standards.org/.
> >
> >
> >
> > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> USED
> > TO SUBSCRIBE(!) to:
> >
> > ASCOM-Talk-unsubscribe@yahoogroups.com
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >     http://groups.yahoo.com/group/ASCOM-Talk/
> >
> >
> >
> >     Individual Email | Traditional
> >
> >
> >
> >     http://groups.yahoo.com/group/ASCOM-Talk/join
> >
> >     (Yahoo! ID required)
> >
> >
> >
> >     ASCOM-Talk-digest@yahoogroups.com
> >
> >     ASCOM-Talk-fullfeatured@yahoogroups.com
> >
> >
> >
> >     ASCOM-Talk-unsubscribe@yahoogroups.com
> >
> >
> >
> >     http://docs.yahoo.com/info/terms/
> >
> >
> >
> >
> > --
> > ExchangeDefender Message Security: Click below to verify authenticity
> >
> http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from=tim@
> .
> > Complete email hygeine and business continuity solution available from
> http://www.tigranetworks.co.uk
> >
>
>
>
>
> ------------------------------------
>
> For more information see http://ASCOM-Standards.org/.
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED
> TO SUBSCRIBE(!) to:
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
> Yahoo! Groups Links
>
>
>
>
> --
> ExchangeDefender Message Security: Click below to verify authenticity
> http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from=tim@...
> Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
>

#21180 From: "robt2112" <robt2112@...>
Date: Thu Jul 1, 2010 5:05 pm
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
robt2112
Send Email Send Email
 
Just for completeness of testing this issue I started a VM with win xp. Never
had anything ascom related. Installed 5.0b. The C:\Program Files\Common
Files\ASCOM\.net is created with just the .vsi template in it.

Install 5.5.1 update. The following is the contents of the .net folder after
install. ASCOM.Interfaces.dll is missing.

Robert



Directory of C:\Program Files\Common Files\ASCOM\.net

7/01/2010  01:02 PM    <DIR>          .
7/01/2010  01:02 PM    <DIR>          ..
1/21/2009  11:30 PM           523,264 ASCOM Diagnostics.exe
1/21/2009  11:30 PM           212,480 ASCOM Diagnostics.pdb
1/24/2009  09:50 PM           540,160 ASCOM.Astrometry.dll
1/24/2009  09:50 PM           249,344 ASCOM.Astrometry.pdb
7/01/2010  01:02 PM            28,824 ASCOM.Astrometry.tlb
1/24/2009  09:50 PM           247,602 ASCOM.Astrometry.xml
1/24/2009  09:49 PM             5,632 ASCOM.Attributes.dll
1/24/2009  09:49 PM            13,824 ASCOM.Attributes.pdb
7/10/2008  02:21 PM            53,248 ASCOM.DriverAccess.dll
7/10/2008  02:21 PM           105,984 ASCOM.DriverAccess.pdb
7/10/2008  02:21 PM           105,045 ASCOM.DriverAccess.XML
1/20/2009  08:24 AM             9,216 ASCOM.Exceptions.dll
1/20/2009  08:24 AM            21,933 ASCOM.Exceptions.XML
8/01/2009  04:33 PM           125,783 ASCOM.ico
1/20/2009  08:24 AM            14,336 ASCOM.IConform.dll
1/20/2009  08:24 AM            34,304 ASCOM.IConform.pdb
7/01/2010  01:02 PM             3,808 ASCOM.IConform.tlb
1/20/2009  08:24 AM             9,589 ASCOM.IConform.xml
1/24/2009  09:49 PM           251,392 ASCOM.Utilities.dll
1/24/2009  09:49 PM           214,528 ASCOM.Utilities.pdb
7/01/2010  01:02 PM            21,216 ASCOM.Utilities.tlb
1/24/2009  09:49 PM           171,112 ASCOM.Utilities.xml
1/17/2009  06:28 PM           397,566 ASCOMDriverTemplates.vsi
4/15/2009  11:58 PM               489 driveraccess.config
1/20/2009  08:25 AM            12,288 FusionLib.dll
1/20/2009  08:25 AM            15,872 FusionLib.pdb
1/20/2009  08:25 AM            15,360 GACInstall.exe
8/01/2009  04:33 PM            37,376 NOVAS-C.dll
8/01/2009  04:33 PM           207,872 NOVAS-C.pdb
8/01/2009  04:33 PM            52,224 NOVAS-C64.dll
8/01/2009  04:33 PM           199,680 NOVAS-C64.pdb
4/15/2009  11:58 PM             3,072 policy.1.0.ASCOM.DriverAccess.dll
1/17/2009  09:10 AM             3,584 policy.5.5.ASCOM.Astrometry.dll
1/17/2009  09:10 AM             3,584 policy.5.5.ASCOM.Utilities.dll
1/17/2009  09:10 AM               741 PublisherPolicy.xml
9/23/2009  10:13 PM               683 ReadMe55.txt
              36 File(s)      3,913,015 bytes
               2 Dir(s)  80,084,582,400 bytes free

:\Program Files\Common Files\ASCOM\.net>

--- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@...> wrote:
>
> This was a fresh computer nothing installed. 5.0b first then update to 5.5.1.
The COM interfaces were installed with the tlb file in the ASCOM folder. The
.net dll was missing in the .net folder.
>
> Robert
>
> --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> >
> > I find it hard to believe that the problem is what you say it is. The
> > interfaces PIA is so fundamental to ASCOM that we would have caught that
> > a long time ago. Can we please be clear about version numbers - when you
> > say "the installer" which version are you talking about?
> >
> > To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not both). The
> > 5.0a/b installer includes and installs the interfaces PIA in the GAC, I
> > am 100% certain that works correctly because it has been tested to death
> > on many different systems, by all the ASCOM developers and beta testers
> > and on many end user systems.
> >
> > Something about this incident doesn't make sense. I would like to get to
> > the bottom of it, but I don't think it is a bug in the installer.
> >
> > Regards,
> > --Tim Long
> >
> >
> > -----Original Message-----
> > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
> > Behalf Of robt2112
> > Sent: 01 July 2010 14:57
> > To: ASCOM-Talk@yahoogroups.com
> > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> >
> > This was just a verification that it is a bug in the installer. The file
> > should have been installed. I verified that the file was missing and
> > that putting the file in place solves the problem. This should be fixed
> > in the installation.
> >
> > Robert
> >
> > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> > >
> > > If you do that... you're on your own! We've got to be very careful
> > about
> > > letting users do stuff like that because it will create confusion and
> > a
> > > support nightmare.
> > >
> > >
> > >
> > > ASCOM interfaces is (currently) a COM object that lives in the GAC. It
> > > should be installed by the platform installer and referenced from the
> > > COM tab of the references dialog.
> > >
> > > --Tim
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com]
> > On
> > > Behalf Of robt2112
> > > Sent: 01 July 2010 02:20
> > > To: ASCOM-Talk@yahoogroups.com
> > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> > >
> > >
> > >
> > > Well... If I copy the dll from my svn download to common
> > > files\ascom\.net then it shows up on my .NET references tab in VS. So
> > I
> > > think the problem is the dll is not included in the install.
> > >
> > >
> > >
> > > Robert
> > >
> > >
> > >
> > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
> > >
> > > >
> > >
> > > > Yes in windows\assembly it shows ASCOM.Interfaces that points to
> > > ASCOM.Interfaces.dll. The only thing that shows up in Visual Studio is
> > a
> > > reference in COM to the tlb located in Program Files\Common
> > > Files\ASCOM\Interfaces.
> > >
> > > >
> > >
> > > > I do have a copy of the dll in the Platform Dependancies folder of
> > the
> > > ASCOM platform Drivers and Simulators that I downloaded from SVN. The
> > > dll doesn't seem to get installed with the platform install.
> > >
> > > >
> > >
> > > > Robert
> > >
> > > >
> > >
> > > > --- In ASCOM-Talk@yahoogroups.com, "paulkccd" <yh@> wrote:
> > >
> > > > >
> > >
> > > > > As far as I can tell, platform 5 installs ASCOM.Interface.dll in
> > > GAC, not in Common Files\ASCOM. Check Windows\Assembly folder to see
> > if
> > > it's there.
> > >
> > > > >
> > >
> > > > > Regards,
> > >
> > > > >
> > >
> > > > >     -Paul
> > >
> > > > >
> > >
> > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
> > >
> > > > > >
> > >
> > > > > > Slight correction. I installed Platform 5.0b then updated to
> > > 5.5.1. Both show installed in programs and features.
> > >
> > > > > >
> > >
> > > > > > Robert
> > >
> > > > > >
> > >
> > > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
> > >
> > > > > > >
> > >
> > > > > > > Well I think what is wrong is the installer for 5.5.1. This is
> > a
> > > brand new install. I havent installed any previous versions which are
> > > not available on the website. I just installed the latest version. The
> > > Interfaces dll was not installed.
> > >
> > > > > > >
> > >
> > > > > > > I believe if you had installed a previous platform version
> > that
> > > dll would be there. Since I installed fresh it didn't get on my
> > machine.
> > >
> > > > > > >
> > >
> > > > > > > Robert
> > >
> > > > > > >
> > >
> > > > > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> > >
> > > > > > > >
> > >
> > > > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform 5.5.
> > >
> > > > > > > >
> > >
> > > > > > > > Paul is correct that it's a .NET assembly, but it is also a
> > > COM Primary
> > >
> > > > > > > > Interop Assembly (PIA) so (confusingly) it show up under the
> > > COM tab as
> > >
> > > > > > > > shown here:
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > So reference that, and also from the .NET tab, bring in the
> > >
> > > > > > > > ASCOM.DriverAccess namespace thus:
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > Your project's references would then look something like
> > this
> > > (I'm using
> > >
> > > > > > > > C# in VS2010, yours may appear differently):
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > Then in visual studio, you can use some code like this to
> > > test:
> > >
> > > > > > > >
> > >
> > > > > > > > using System;
> > >
> > > > > > > >
> > >
> > > > > > > > using ASCOM.DriverAccess;
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > namespace ConsoleApplication1
> > >
> > > > > > > >
> > >
> > > > > > > > {
> > >
> > > > > > > >
> > >
> > > > > > > >     class Program
> > >
> > > > > > > >
> > >
> > > > > > > >     {
> > >
> > > > > > > >
> > >
> > > > > > > >         static void Main(string[] args)
> > >
> > > > > > > >
> > >
> > > > > > > >         {
> > >
> > > > > > > >
> > >
> > > > > > > >             var userChoice = Telescope.Choose(String.Empty);
> > >
> > > > > > > >
> > >
> > > > > > > >             var scope = new Telescope(userChoice);
> > >
> > > > > > > >
> > >
> > > > > > > >             scope.Connected = true;
> > >
> > > > > > > >
> > >
> > > > > > > >             scope.Park();
> > >
> > > > > > > >
> > >
> > > > > > > >             scope.Connected = false;
> > >
> > > > > > > >
> > >
> > > > > > > >             scope.Dispose();
> > >
> > > > > > > >
> > >
> > > > > > > >             scope = null;
> > >
> > > > > > > >
> > >
> > > > > > > >         }
> > >
> > > > > > > >
> > >
> > > > > > > >     }
> > >
> > > > > > > >
> > >
> > > > > > > > }
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > This code does work, I just ran it. If you can't get this to
> > > work, then
> > >
> > > > > > > > something is badly wrong and needs sorting out.
> > >
> > > > > > > >
> > >
> > > > > > > > --Tim
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > -----Original Message-----
> > >
> > > > > > > >
> > >
> > > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > >
> > > > > > > >
> > >
> > > > > > > > > Talk@yahoogroups.com] On Behalf Of robt2112
> > >
> > > > > > > >
> > >
> > > > > > > > > Sent: 30 June 2010 20:53
> > >
> > > > > > > >
> > >
> > > > > > > > > To: ASCOM-Talk@yahoogroups.com
> > >
> > > > > > > >
> > >
> > > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in
> > > .NET
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > It should be, but its not on my .NET assembly tab in
> > visual
> > > studio. I
> > >
> > > > > > > > only see it
> > >
> > > > > > > >
> > >
> > > > > > > > > on the COM tab. Looks like the install didnt not register
> > > something.
> > >
> > > > > > > > This is a
> > >
> > > > > > > >
> > >
> > > > > > > > > new Win7 machine with a brand new ASCOM install.
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > Robert
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com>
> > >
> > > > > > > > , "paulkccd" <yh@ <mailto:yh@> > wrote:
> > >
> > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM. You can
> > add
> > > a
> > >
> > > > > > > > reference
> > >
> > > > > > > >
> > >
> > > > > > > > > to it from the .NET tab in Visual Studio Add References
> > > dialog.
> > >
> > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > Regards,
> > >
> > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > >     -Paul
> > >
> > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > >
> > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@>
> > > wrote:
> > >
> > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > That is what I was trying. I cant get access to
> > > ITelescope. I
> > >
> > > > > > > > added a
> > >
> > > > > > > >
> > >
> > > > > > > > > reference to DriverAccess and it complained that the
> > > interfaces were
> > >
> > > > > > > > defined
> > >
> > > > > > > >
> > >
> > > > > > > > > in ASCOM.Interfaces. I added that reference from COM, but
> > > dont see a
> > >
> > > > > > > > .NET
> > >
> > > > > > > >
> > >
> > > > > > > > > version. When I try to use ASCOM.ITelescope it complains
> > it
> > > doesn't
> > >
> > > > > > > > exist.
> > >
> > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > It won't let you create an instance with Type
> > Telescope.
> > > It says I
> > >
> > > > > > > > must use
> > >
> > > > > > > >
> > >
> > > > > > > > > ITelescope.
> > >
> > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > Robert
> > >
> > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > >
> > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
> > wrote:
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > And this is how I'd do it in C#:
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >      ITelescope g;
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >      g =
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > .Gemin\
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > iTelescope.Telescope"));
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >      g.Connected = true;
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > Regards,
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >       -Paul
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > >
> > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
> > wrote:
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > Rob, what error do you get? Here's sample VB.Net
> > > code I sent
> > >
> > > > > > > > to
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > a
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > Gemini
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > user:
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > CreateObject("ASCOM.GeminiTelescope.Telescope")
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > g.Connected = True
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > You just need to add a reference ASCOM.Interfaces
> > > assembly.
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > Does this not work for you?
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > Regards,
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > -Paul
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > >
> > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" robt2112@
> > > wrote:
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > > So this is basic question. How do I access and
> > use
> > > an ASCOM
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > > driver
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > in
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > .NET code. I keep running into cant create
> > instances
> > > that
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > represent
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > COM
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > components.
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > > Robert
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > ------------------------------------
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > For more information see http://ASCOM-Standards.org/
> > >
> > > > > > > > <http://ASCOM-Standards.org/> .
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > To unsubscribe from this group, send an email FROM THE
> > > ACCOUNT YOU
> > >
> > > > > > > >
> > >
> > > > > > > > > USED TO SUBSCRIBE(!) to:
> > >
> > > > > > > >
> > >
> > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > >
> > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > > Yahoo! Groups Links
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > >
> > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/>
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >     Individual Email | Traditional
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > >
> > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> > >
> > > > > > > >
> > >
> > > > > > > > >     (Yahoo! ID required)
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> > >
> > > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> > >
> > > > > > > >
> > >
> > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > >
> > > > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > >
> > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > >     http://docs.yahoo.com/info/terms/
> > >
> > > > > > > > <http://docs.yahoo.com/info/terms/>
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > --
> > >
> > > > > > > > ExchangeDefender Message Security: Click below to verify
> > > authenticity
> > >
> > > > > > > >
> > > http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from=tim@
> > >
> > > > > > > > Complete email hygeine and business continuity solution
> > > available from http://www.tigranetworks.co.uk
> > >
> > > > > > > >
> > >
> > > > > > >
> > >
> > > > > >
> > >
> > > > >
> > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > >
> > >
> > > For more information see http://ASCOM-Standards.org/.
> > >
> > >
> > >
> > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> > USED
> > > TO SUBSCRIBE(!) to:
> > >
> > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > >
> > >
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > >
> > >
> > >
> > >     Individual Email | Traditional
> > >
> > >
> > >
> > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > >
> > >     (Yahoo! ID required)
> > >
> > >
> > >
> > >     ASCOM-Talk-digest@yahoogroups.com
> > >
> > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > >
> > >
> > >
> > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > >
> > >
> > >
> > >     http://docs.yahoo.com/info/terms/
> > >
> > >
> > >
> > >
> > > --
> > > ExchangeDefender Message Security: Click below to verify authenticity
> > >
> > http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from=tim@
> > .
> > > Complete email hygeine and business continuity solution available from
> > http://www.tigranetworks.co.uk
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > For more information see http://ASCOM-Standards.org/.
> >
> > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED
> > TO SUBSCRIBE(!) to:
> > ASCOM-Talk-unsubscribe@yahoogroups.com
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> > --
> > ExchangeDefender Message Security: Click below to verify authenticity
> > http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from=tim@
> > Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
> >
>

#21181 From: "Douglas B. George" <dg@...>
Date: Thu Jul 1, 2010 5:08 pm
Subject: Re: [ASCOM] Re: Temperature compensated focusing issues
maximccd
Send Email Send Email
 
On 2010-07-01 11:56 AM, Tom wrote:

> Yes, I do make an important assumption...that focus shift/behavior in the
> overall system changes in a linear fashion as temperature changes.
>
> That's a pretty good assumption when your scope is 'small'...it equilibriates
> pretty rapidly with changing air temperature.  It's not a good assumption
> with a bigger scope...such as the 12-inch LX-200 classic...with its
> four-pound pig iron ring behind the main mirror (I presume for balance/fork
> arm length considerations).  In that case it would be helpful to modify the
> OTA to make it equilibriate faster.  (I take out such weights, and
> aggressively ventilate the OTA.)

It's also not a good assumption with refractors.  The different elements can
expand and contract at different rates.  As a result the focus shift behaviour
is often far from linear.

Paul Boltwood did some extensive measurements on his old 7-inch Starfire.  One
night the ambient temperature curve reversed direction and started climbing
again, but the focus shift not only didn't change direction, it ACCELERATED.  It
turned out that the focus shift was far more correlated with the RATE of
temperature change than the actual magnitude of the change.  So he came to the
conclusion that temperature compensation was useless for that telescope.

Other instruments may be much better behaved, of course, especially when the
tube itself dominates.

Doug

--

Doug George
dgeorge@...

Diffraction Limited
Makers of Cyanogen Imaging Products
http://www.cyanogen.com/

100 Craig Henry Dr., Suite 202
Ottawa, Ontario,
Canada, K2G 5W3

Phone:    (613) 225-2732
Fax:      (613) 225-9688

#21182 From: "Tom" <tom_krajci@...>
Date: Thu Jul 1, 2010 6:19 pm
Subject: [ASCOM] Re: Temperature compensated focusing issues
tom_krajci
Send Email Send Email
 
--- In ASCOM-Talk@yahoogroups.com, "Douglas B. George" <dg@...> wrote:
>
> On 2010-07-01 11:56 AM, Tom wrote:
>
> > Yes, I do make an important assumption...that focus shift/behavior in the
> > overall system changes in a linear fashion as temperature changes.
> >
> > That's a pretty good assumption when your scope is 'small'....

> Paul Boltwood did some extensive measurements on his old 7-inch Starfire.  One
> night the ambient temperature curve reversed direction and started climbing
> again, but the focus shift not only didn't change direction, it ACCELERATED. 
It
> turned out that the focus shift was far more correlated with the RATE of
> temperature change than the actual magnitude of the change.  So he came to the
> conclusion that temperature compensation was useless for that telescope.

Interesting.  Thanks for the info.

I don't know if I'd consider a 7-inch refractor small.  I'd put it closer to the
large category...where good equilibriation is more challenging, and may require
additional thermal management measures.

My refractor experience is with a 60mm Tak...the AAVSO Bright Star Monitor
(BSM):  <http://www.aavso.org/news/bsm.shtml>   which is pretty small.  (The odd
thing for this scope is that, even with a high-expansion aluminum tube...as
temperature drops...you must move the focuser inward.  But from what I've seen,
I think it would benefit from linear modeling/compensation of temperature versus
focus.)

--
-------------------------------------------
Tom Krajci
Cloudcroft, New Mexico
http://picasaweb.google.com/tom.krajci

Center for Backyard Astrophysics (CBA)
http://cbastro.org/ CBA New Mexico

American Association of Variable Star
Observers (AAVSO): KTC http://www.aavso.org/
-------------------------------------------

#21183 From: "Tim Long" <Tim@...>
Date: Thu Jul 1, 2010 6:43 pm
Subject: RE: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
t_p_long
Send Email Send Email
 
I wouldn't necessarily expect it to be there. Let me try the same thing
myself and I'll get back to you.
--Tim

> -----Original Message-----
> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> Talk@yahoogroups.com] On Behalf Of robt2112
> Sent: 01 July 2010 18:06
> To: ASCOM-Talk@yahoogroups.com
> Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
> Just for completeness of testing this issue I started a VM with win
xp. Never
> had anything ascom related. Installed 5.0b. The C:\Program
Files\Common
> Files\ASCOM\.net is created with just the .vsi template in it.
>
> Install 5.5.1 update. The following is the contents of the .net folder
after
> install. ASCOM.Interfaces.dll is missing.
>
> Robert
>
>
>
> Directory of C:\Program Files\Common Files\ASCOM\.net
>
> 7/01/2010  01:02 PM    <DIR>          .
> 7/01/2010  01:02 PM    <DIR>          ..
> 1/21/2009  11:30 PM           523,264 ASCOM Diagnostics.exe
> 1/21/2009  11:30 PM           212,480 ASCOM Diagnostics.pdb
> 1/24/2009  09:50 PM           540,160 ASCOM.Astrometry.dll
> 1/24/2009  09:50 PM           249,344 ASCOM.Astrometry.pdb
> 7/01/2010  01:02 PM            28,824 ASCOM.Astrometry.tlb
> 1/24/2009  09:50 PM           247,602 ASCOM.Astrometry.xml
> 1/24/2009  09:49 PM             5,632 ASCOM.Attributes.dll
> 1/24/2009  09:49 PM            13,824 ASCOM.Attributes.pdb
> 7/10/2008  02:21 PM            53,248 ASCOM.DriverAccess.dll
> 7/10/2008  02:21 PM           105,984 ASCOM.DriverAccess.pdb
> 7/10/2008  02:21 PM           105,045 ASCOM.DriverAccess.XML
> 1/20/2009  08:24 AM             9,216 ASCOM.Exceptions.dll
> 1/20/2009  08:24 AM            21,933 ASCOM.Exceptions.XML
> 8/01/2009  04:33 PM           125,783 ASCOM.ico
> 1/20/2009  08:24 AM            14,336 ASCOM.IConform.dll
> 1/20/2009  08:24 AM            34,304 ASCOM.IConform.pdb
> 7/01/2010  01:02 PM             3,808 ASCOM.IConform.tlb
> 1/20/2009  08:24 AM             9,589 ASCOM.IConform.xml
> 1/24/2009  09:49 PM           251,392 ASCOM.Utilities.dll
> 1/24/2009  09:49 PM           214,528 ASCOM.Utilities.pdb
> 7/01/2010  01:02 PM            21,216 ASCOM.Utilities.tlb
> 1/24/2009  09:49 PM           171,112 ASCOM.Utilities.xml
> 1/17/2009  06:28 PM           397,566 ASCOMDriverTemplates.vsi
> 4/15/2009  11:58 PM               489 driveraccess.config
> 1/20/2009  08:25 AM            12,288 FusionLib.dll
> 1/20/2009  08:25 AM            15,872 FusionLib.pdb
> 1/20/2009  08:25 AM            15,360 GACInstall.exe
> 8/01/2009  04:33 PM            37,376 NOVAS-C.dll
> 8/01/2009  04:33 PM           207,872 NOVAS-C.pdb
> 8/01/2009  04:33 PM            52,224 NOVAS-C64.dll
> 8/01/2009  04:33 PM           199,680 NOVAS-C64.pdb
> 4/15/2009  11:58 PM             3,072
policy.1.0.ASCOM.DriverAccess.dll
> 1/17/2009  09:10 AM             3,584 policy.5.5.ASCOM.Astrometry.dll
> 1/17/2009  09:10 AM             3,584 policy.5.5.ASCOM.Utilities.dll
> 1/17/2009  09:10 AM               741 PublisherPolicy.xml
> 9/23/2009  10:13 PM               683 ReadMe55.txt
>              36 File(s)      3,913,015 bytes
>               2 Dir(s)  80,084,582,400 bytes free
>
> :\Program Files\Common Files\ASCOM\.net>
>
> --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@...> wrote:
> >
> > This was a fresh computer nothing installed. 5.0b first then update
to 5.5.1.
> The COM interfaces were installed with the tlb file in the ASCOM
folder. The
> .net dll was missing in the .net folder.
> >
> > Robert
> >
> > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> > >
> > > I find it hard to believe that the problem is what you say it is.
> > > The interfaces PIA is so fundamental to ASCOM that we would have
> > > caught that a long time ago. Can we please be clear about version
> > > numbers - when you say "the installer" which version are you
talking
> about?
> > >
> > > To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not both).
> > > The 5.0a/b installer includes and installs the interfaces PIA in
the
> > > GAC, I am 100% certain that works correctly because it has been
> > > tested to death on many different systems, by all the ASCOM
> > > developers and beta testers and on many end user systems.
> > >
> > > Something about this incident doesn't make sense. I would like to
> > > get to the bottom of it, but I don't think it is a bug in the
installer.
> > >
> > > Regards,
> > > --Tim Long
> > >
> > >
> > > -----Original Message-----
> > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> Talk@yahoogroups.com]
> > > On Behalf Of robt2112
> > > Sent: 01 July 2010 14:57
> > > To: ASCOM-Talk@yahoogroups.com
> > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> > >
> > > This was just a verification that it is a bug in the installer.
The
> > > file should have been installed. I verified that the file was
> > > missing and that putting the file in place solves the problem.
This
> > > should be fixed in the installation.
> > >
> > > Robert
> > >
> > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> > > >
> > > > If you do that... you're on your own! We've got to be very
careful
> > > about
> > > > letting users do stuff like that because it will create
confusion
> > > > and
> > > a
> > > > support nightmare.
> > > >
> > > >
> > > >
> > > > ASCOM interfaces is (currently) a COM object that lives in the
> > > > GAC. It should be installed by the platform installer and
> > > > referenced from the COM tab of the references dialog.
> > > >
> > > > --Tim
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: ASCOM-Talk@yahoogroups.com
> > > > [mailto:ASCOM-Talk@yahoogroups.com]
> > > On
> > > > Behalf Of robt2112
> > > > Sent: 01 July 2010 02:20
> > > > To: ASCOM-Talk@yahoogroups.com
> > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> > > >
> > > >
> > > >
> > > > Well... If I copy the dll from my svn download to common
> > > > files\ascom\.net then it shows up on my .NET references tab in
VS.
> > > > So
> > > I
> > > > think the problem is the dll is not included in the install.
> > > >
> > > >
> > > >
> > > > Robert
> > > >
> > > >
> > > >
> > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@>
> wrote:
> > > >
> > > > >
> > > >
> > > > > Yes in windows\assembly it shows ASCOM.Interfaces that points
to
> > > > ASCOM.Interfaces.dll. The only thing that shows up in Visual
> > > > Studio is
> > > a
> > > > reference in COM to the tlb located in Program Files\Common
> > > > Files\ASCOM\Interfaces.
> > > >
> > > > >
> > > >
> > > > > I do have a copy of the dll in the Platform Dependancies
folder
> > > > > of
> > > the
> > > > ASCOM platform Drivers and Simulators that I downloaded from
SVN.
> > > > The dll doesn't seem to get installed with the platform install.
> > > >
> > > > >
> > > >
> > > > > Robert
> > > >
> > > > >
> > > >
> > > > > --- In ASCOM-Talk@yahoogroups.com, "paulkccd" <yh@> wrote:
> > > >
> > > > > >
> > > >
> > > > > > As far as I can tell, platform 5 installs
ASCOM.Interface.dll
> > > > > > in
> > > > GAC, not in Common Files\ASCOM. Check Windows\Assembly folder to
> > > > see
> > > if
> > > > it's there.
> > > >
> > > > > >
> > > >
> > > > > > Regards,
> > > >
> > > > > >
> > > >
> > > > > >     -Paul
> > > >
> > > > > >
> > > >
> > > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@>
> wrote:
> > > >
> > > > > > >
> > > >
> > > > > > > Slight correction. I installed Platform 5.0b then updated
to
> > > > 5.5.1. Both show installed in programs and features.
> > > >
> > > > > > >
> > > >
> > > > > > > Robert
> > > >
> > > > > > >
> > > >
> > > > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@>
> wrote:
> > > >
> > > > > > > >
> > > >
> > > > > > > > Well I think what is wrong is the installer for 5.5.1.
> > > > > > > > This is
> > > a
> > > > brand new install. I havent installed any previous versions
which
> > > > are not available on the website. I just installed the latest
> > > > version. The Interfaces dll was not installed.
> > > >
> > > > > > > >
> > > >
> > > > > > > > I believe if you had installed a previous platform
version
> > > that
> > > > dll would be there. Since I installed fresh it didn't get on my
> > > machine.
> > > >
> > > > > > > >
> > > >
> > > > > > > > Robert
> > > >
> > > > > > > >
> > > >
> > > > > > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@>
> wrote:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform 5.5.
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > Paul is correct that it's a .NET assembly, but it is
> > > > > > > > > also a
> > > > COM Primary
> > > >
> > > > > > > > > Interop Assembly (PIA) so (confusingly) it show up
under
> > > > > > > > > the
> > > > COM tab as
> > > >
> > > > > > > > > shown here:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > So reference that, and also from the .NET tab, bring
in
> > > > > > > > > the
> > > >
> > > > > > > > > ASCOM.DriverAccess namespace thus:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > Your project's references would then look something
like
> > > this
> > > > (I'm using
> > > >
> > > > > > > > > C# in VS2010, yours may appear differently):
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > Then in visual studio, you can use some code like this
> > > > > > > > > to
> > > > test:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > using System;
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > using ASCOM.DriverAccess;
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > namespace ConsoleApplication1
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > {
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >     class Program
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >     {
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >         static void Main(string[] args)
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >         {
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >             var userChoice =
> > > > > > > > > Telescope.Choose(String.Empty);
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >             var scope = new Telescope(userChoice);
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >             scope.Connected = true;
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >             scope.Park();
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >             scope.Connected = false;
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >             scope.Dispose();
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >             scope = null;
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >         }
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >     }
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > }
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > This code does work, I just ran it. If you can't get
> > > > > > > > > this to
> > > > work, then
> > > >
> > > > > > > > > something is badly wrong and needs sorting out.
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > --Tim
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > -----Original Message-----
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > Talk@yahoogroups.com] On Behalf Of robt2112
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > Sent: 30 June 2010 20:53
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > To: ASCOM-Talk@yahoogroups.com
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM
driver
> > > > > > > > > > in
> > > > .NET
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > It should be, but its not on my .NET assembly tab in
> > > visual
> > > > studio. I
> > > >
> > > > > > > > > only see it
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > on the COM tab. Looks like the install didnt not
> > > > > > > > > > register
> > > > something.
> > > >
> > > > > > > > > This is a
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > new Win7 machine with a brand new ASCOM install.
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > Robert
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > > <mailto:ASCOM-Talk@yahoogroups.com>
> > > >
> > > > > > > > > , "paulkccd" <yh@ <mailto:yh@> > wrote:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM. You
> > > > > > > > > > > can
> > > add
> > > > a
> > > >
> > > > > > > > > reference
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > to it from the .NET tab in Visual Studio Add
> > > > > > > > > > References
> > > > dialog.
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > Regards,
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > >     -Paul
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > >
> > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
> > > > > > > > > <robt2112@>
> > > > wrote:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > That is what I was trying. I cant get access to
> > > > ITelescope. I
> > > >
> > > > > > > > > added a
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > reference to DriverAccess and it complained that the
> > > > interfaces were
> > > >
> > > > > > > > > defined
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > in ASCOM.Interfaces. I added that reference from
COM,
> > > > > > > > > > but
> > > > dont see a
> > > >
> > > > > > > > > .NET
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > version. When I try to use ASCOM.ITelescope it
> > > > > > > > > > complains
> > > it
> > > > doesn't
> > > >
> > > > > > > > > exist.
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > It won't let you create an instance with Type
> > > Telescope.
> > > > It says I
> > > >
> > > > > > > > > must use
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > ITelescope.
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > Robert
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > >
> > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
> > > wrote:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > And this is how I'd do it in C#:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >      ITelescope g;
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >      g =
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > .Gemin\
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > iTelescope.Telescope"));
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >      g.Connected = true;
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > Regards,
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >       -Paul
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > >
> > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
> > > wrote:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > Rob, what error do you get? Here's sample
> > > > > > > > > > > > > > VB.Net
> > > > code I sent
> > > >
> > > > > > > > > to
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > a
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > Gemini
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > user:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
CreateObject("ASCOM.GeminiTelescope.Telescope"
> > > > > > > > > > > > > > )
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > g.Connected = True
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > You just need to add a reference
> > > > > > > > > > > > > > ASCOM.Interfaces
> > > > assembly.
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > Does this not work for you?
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > Regards,
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > -Paul
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > >
> > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
> > > > > > > > > robt2112@
> > > > wrote:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > > So this is basic question. How do I access
> > > > > > > > > > > > > > > and
> > > use
> > > > an ASCOM
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > > driver
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > in
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > .NET code. I keep running into cant create
> > > instances
> > > > that
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > represent
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > COM
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > components.
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > > Robert
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > ------------------------------------
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > For more information see http://ASCOM-Standards.org/
> > > >
> > > > > > > > > <http://ASCOM-Standards.org/> .
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > To unsubscribe from this group, send an email FROM
THE
> > > > ACCOUNT YOU
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > USED TO SUBSCRIBE(!) to:
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > >
> > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > > Yahoo! Groups Links
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > > >
> > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/>
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >     Individual Email | Traditional
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > > >
> > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >     (Yahoo! ID required)
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> > > >
> > > > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > > >
> > > > > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > > >
> > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > >     http://docs.yahoo.com/info/terms/
> > > >
> > > > > > > > > <http://docs.yahoo.com/info/terms/>
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > >
> > > >
> > > > > > > > > --
> > > >
> > > > > > > > > ExchangeDefender Message Security: Click below to
verify
> > > > authenticity
> > > >
> > > > > > > > >
> > > >
> http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from
> =
> > > > tim@
> > > >
> > > > > > > > > Complete email hygeine and business continuity
solution
> > > > available from http://www.tigranetworks.co.uk
> > > >
> > > > > > > > >
> > > >
> > > > > > > >
> > > >
> > > > > > >
> > > >
> > > > > >
> > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > >
> > > >
> > > > For more information see http://ASCOM-Standards.org/.
> > > >
> > > >
> > > >
> > > > To unsubscribe from this group, send an email FROM THE ACCOUNT
> YOU
> > > USED
> > > > TO SUBSCRIBE(!) to:
> > > >
> > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > >
> > > >
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > > >
> > > >
> > > >
> > > >     Individual Email | Traditional
> > > >
> > > >
> > > >
> > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > > >
> > > >     (Yahoo! ID required)
> > > >
> > > >
> > > >
> > > >     ASCOM-Talk-digest@yahoogroups.com
> > > >
> > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > > >
> > > >
> > > >
> > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > > >
> > > >
> > > >
> > > >     http://docs.yahoo.com/info/terms/
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > ExchangeDefender Message Security: Click below to verify
> > > > authenticity
> > > >
> > >
> http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from=
> ti
> > > m@
> > > .
> > > > Complete email hygeine and business continuity solution
available
> > > > from
> > > http://www.tigranetworks.co.uk
> > > >
> > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > For more information see http://ASCOM-Standards.org/.
> > >
> > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> > > USED TO SUBSCRIBE(!) to:
> > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> > > --
> > > ExchangeDefender Message Security: Click below to verify
> > > authenticity
> > >
> http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from=
> ti
> > > m@ Complete email hygeine and business continuity solution
available
> > > from http://www.tigranetworks.co.uk
> > >
> >
>
>
>
>
> ------------------------------------
>
> For more information see http://ASCOM-Standards.org/.
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> USED TO SUBSCRIBE(!) to:
> ASCOM-Talk-unsubscribe@yahoogroups.com
>
> Yahoo! Groups Links
>
>
>

--
ExchangeDefender Message Security: Click below to verify authenticity
http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=tim@tigranetwo\
rks.co.uk
Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk

#21184 From: "robt2112" <robt2112@...>
Date: Thu Jul 1, 2010 7:18 pm
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
robt2112
Send Email Send Email
 
The related issue then is if it is not there then you cant reference the
interfaces in Visual Studio. It doesn't exist anywhere searching the entire c
drive of the VM. The file is required for development in Visual Studio.

Robert

--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> I wouldn't necessarily expect it to be there. Let me try the same thing
> myself and I'll get back to you.
> --Tim
>
> > -----Original Message-----
> > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > Talk@yahoogroups.com] On Behalf Of robt2112
> > Sent: 01 July 2010 18:06
> > To: ASCOM-Talk@yahoogroups.com
> > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> >
> > Just for completeness of testing this issue I started a VM with win
> xp. Never
> > had anything ascom related. Installed 5.0b. The C:\Program
> Files\Common
> > Files\ASCOM\.net is created with just the .vsi template in it.
> >
> > Install 5.5.1 update. The following is the contents of the .net folder
> after
> > install. ASCOM.Interfaces.dll is missing.
> >
> > Robert
> >
> >
> >
> > Directory of C:\Program Files\Common Files\ASCOM\.net
> >
> > 7/01/2010  01:02 PM    <DIR>          .
> > 7/01/2010  01:02 PM    <DIR>          ..
> > 1/21/2009  11:30 PM           523,264 ASCOM Diagnostics.exe
> > 1/21/2009  11:30 PM           212,480 ASCOM Diagnostics.pdb
> > 1/24/2009  09:50 PM           540,160 ASCOM.Astrometry.dll
> > 1/24/2009  09:50 PM           249,344 ASCOM.Astrometry.pdb
> > 7/01/2010  01:02 PM            28,824 ASCOM.Astrometry.tlb
> > 1/24/2009  09:50 PM           247,602 ASCOM.Astrometry.xml
> > 1/24/2009  09:49 PM             5,632 ASCOM.Attributes.dll
> > 1/24/2009  09:49 PM            13,824 ASCOM.Attributes.pdb
> > 7/10/2008  02:21 PM            53,248 ASCOM.DriverAccess.dll
> > 7/10/2008  02:21 PM           105,984 ASCOM.DriverAccess.pdb
> > 7/10/2008  02:21 PM           105,045 ASCOM.DriverAccess.XML
> > 1/20/2009  08:24 AM             9,216 ASCOM.Exceptions.dll
> > 1/20/2009  08:24 AM            21,933 ASCOM.Exceptions.XML
> > 8/01/2009  04:33 PM           125,783 ASCOM.ico
> > 1/20/2009  08:24 AM            14,336 ASCOM.IConform.dll
> > 1/20/2009  08:24 AM            34,304 ASCOM.IConform.pdb
> > 7/01/2010  01:02 PM             3,808 ASCOM.IConform.tlb
> > 1/20/2009  08:24 AM             9,589 ASCOM.IConform.xml
> > 1/24/2009  09:49 PM           251,392 ASCOM.Utilities.dll
> > 1/24/2009  09:49 PM           214,528 ASCOM.Utilities.pdb
> > 7/01/2010  01:02 PM            21,216 ASCOM.Utilities.tlb
> > 1/24/2009  09:49 PM           171,112 ASCOM.Utilities.xml
> > 1/17/2009  06:28 PM           397,566 ASCOMDriverTemplates.vsi
> > 4/15/2009  11:58 PM               489 driveraccess.config
> > 1/20/2009  08:25 AM            12,288 FusionLib.dll
> > 1/20/2009  08:25 AM            15,872 FusionLib.pdb
> > 1/20/2009  08:25 AM            15,360 GACInstall.exe
> > 8/01/2009  04:33 PM            37,376 NOVAS-C.dll
> > 8/01/2009  04:33 PM           207,872 NOVAS-C.pdb
> > 8/01/2009  04:33 PM            52,224 NOVAS-C64.dll
> > 8/01/2009  04:33 PM           199,680 NOVAS-C64.pdb
> > 4/15/2009  11:58 PM             3,072
> policy.1.0.ASCOM.DriverAccess.dll
> > 1/17/2009  09:10 AM             3,584 policy.5.5.ASCOM.Astrometry.dll
> > 1/17/2009  09:10 AM             3,584 policy.5.5.ASCOM.Utilities.dll
> > 1/17/2009  09:10 AM               741 PublisherPolicy.xml
> > 9/23/2009  10:13 PM               683 ReadMe55.txt
> >              36 File(s)      3,913,015 bytes
> >               2 Dir(s)  80,084,582,400 bytes free
> >
> > :\Program Files\Common Files\ASCOM\.net>
> >
> > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
> > >
> > > This was a fresh computer nothing installed. 5.0b first then update
> to 5.5.1.
> > The COM interfaces were installed with the tlb file in the ASCOM
> folder. The
> > .net dll was missing in the .net folder.
> > >
> > > Robert
> > >
> > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> > > >
> > > > I find it hard to believe that the problem is what you say it is.
> > > > The interfaces PIA is so fundamental to ASCOM that we would have
> > > > caught that a long time ago. Can we please be clear about version
> > > > numbers - when you say "the installer" which version are you
> talking
> > about?
> > > >
> > > > To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not both).
> > > > The 5.0a/b installer includes and installs the interfaces PIA in
> the
> > > > GAC, I am 100% certain that works correctly because it has been
> > > > tested to death on many different systems, by all the ASCOM
> > > > developers and beta testers and on many end user systems.
> > > >
> > > > Something about this incident doesn't make sense. I would like to
> > > > get to the bottom of it, but I don't think it is a bug in the
> installer.
> > > >
> > > > Regards,
> > > > --Tim Long
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > Talk@yahoogroups.com]
> > > > On Behalf Of robt2112
> > > > Sent: 01 July 2010 14:57
> > > > To: ASCOM-Talk@yahoogroups.com
> > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> > > >
> > > > This was just a verification that it is a bug in the installer.
> The
> > > > file should have been installed. I verified that the file was
> > > > missing and that putting the file in place solves the problem.
> This
> > > > should be fixed in the installation.
> > > >
> > > > Robert
> > > >
> > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> > > > >
> > > > > If you do that... you're on your own! We've got to be very
> careful
> > > > about
> > > > > letting users do stuff like that because it will create
> confusion
> > > > > and
> > > > a
> > > > > support nightmare.
> > > > >
> > > > >
> > > > >
> > > > > ASCOM interfaces is (currently) a COM object that lives in the
> > > > > GAC. It should be installed by the platform installer and
> > > > > referenced from the COM tab of the references dialog.
> > > > >
> > > > > --Tim
> > > > >
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: ASCOM-Talk@yahoogroups.com
> > > > > [mailto:ASCOM-Talk@yahoogroups.com]
> > > > On
> > > > > Behalf Of robt2112
> > > > > Sent: 01 July 2010 02:20
> > > > > To: ASCOM-Talk@yahoogroups.com
> > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> > > > >
> > > > >
> > > > >
> > > > > Well... If I copy the dll from my svn download to common
> > > > > files\ascom\.net then it shows up on my .NET references tab in
> VS.
> > > > > So
> > > > I
> > > > > think the problem is the dll is not included in the install.
> > > > >
> > > > >
> > > > >
> > > > > Robert
> > > > >
> > > > >
> > > > >
> > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@>
> > wrote:
> > > > >
> > > > > >
> > > > >
> > > > > > Yes in windows\assembly it shows ASCOM.Interfaces that points
> to
> > > > > ASCOM.Interfaces.dll. The only thing that shows up in Visual
> > > > > Studio is
> > > > a
> > > > > reference in COM to the tlb located in Program Files\Common
> > > > > Files\ASCOM\Interfaces.
> > > > >
> > > > > >
> > > > >
> > > > > > I do have a copy of the dll in the Platform Dependancies
> folder
> > > > > > of
> > > > the
> > > > > ASCOM platform Drivers and Simulators that I downloaded from
> SVN.
> > > > > The dll doesn't seem to get installed with the platform install.
> > > > >
> > > > > >
> > > > >
> > > > > > Robert
> > > > >
> > > > > >
> > > > >
> > > > > > --- In ASCOM-Talk@yahoogroups.com, "paulkccd" <yh@> wrote:
> > > > >
> > > > > > >
> > > > >
> > > > > > > As far as I can tell, platform 5 installs
> ASCOM.Interface.dll
> > > > > > > in
> > > > > GAC, not in Common Files\ASCOM. Check Windows\Assembly folder to
> > > > > see
> > > > if
> > > > > it's there.
> > > > >
> > > > > > >
> > > > >
> > > > > > > Regards,
> > > > >
> > > > > > >
> > > > >
> > > > > > >     -Paul
> > > > >
> > > > > > >
> > > > >
> > > > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@>
> > wrote:
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > Slight correction. I installed Platform 5.0b then updated
> to
> > > > > 5.5.1. Both show installed in programs and features.
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > Robert
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@>
> > wrote:
> > > > >
> > > > > > > > >
> > > > >
> > > > > > > > > Well I think what is wrong is the installer for 5.5.1.
> > > > > > > > > This is
> > > > a
> > > > > brand new install. I havent installed any previous versions
> which
> > > > > are not available on the website. I just installed the latest
> > > > > version. The Interfaces dll was not installed.
> > > > >
> > > > > > > > >
> > > > >
> > > > > > > > > I believe if you had installed a previous platform
> version
> > > > that
> > > > > dll would be there. Since I installed fresh it didn't get on my
> > > > machine.
> > > > >
> > > > > > > > >
> > > > >
> > > > > > > > > Robert
> > > > >
> > > > > > > > >
> > > > >
> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@>
> > wrote:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform 5.5.
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > Paul is correct that it's a .NET assembly, but it is
> > > > > > > > > > also a
> > > > > COM Primary
> > > > >
> > > > > > > > > > Interop Assembly (PIA) so (confusingly) it show up
> under
> > > > > > > > > > the
> > > > > COM tab as
> > > > >
> > > > > > > > > > shown here:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > So reference that, and also from the .NET tab, bring
> in
> > > > > > > > > > the
> > > > >
> > > > > > > > > > ASCOM.DriverAccess namespace thus:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > Your project's references would then look something
> like
> > > > this
> > > > > (I'm using
> > > > >
> > > > > > > > > > C# in VS2010, yours may appear differently):
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > Then in visual studio, you can use some code like this
> > > > > > > > > > to
> > > > > test:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > using System;
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > using ASCOM.DriverAccess;
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > namespace ConsoleApplication1
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > {
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >     class Program
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >     {
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >         static void Main(string[] args)
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >         {
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >             var userChoice =
> > > > > > > > > > Telescope.Choose(String.Empty);
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >             var scope = new Telescope(userChoice);
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >             scope.Connected = true;
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >             scope.Park();
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >             scope.Connected = false;
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >             scope.Dispose();
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >             scope = null;
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >         }
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >     }
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > }
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > This code does work, I just ran it. If you can't get
> > > > > > > > > > this to
> > > > > work, then
> > > > >
> > > > > > > > > > something is badly wrong and needs sorting out.
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > --Tim
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > -----Original Message-----
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > Talk@yahoogroups.com] On Behalf Of robt2112
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > Sent: 30 June 2010 20:53
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > To: ASCOM-Talk@yahoogroups.com
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM
> driver
> > > > > > > > > > > in
> > > > > .NET
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > It should be, but its not on my .NET assembly tab in
> > > > visual
> > > > > studio. I
> > > > >
> > > > > > > > > > only see it
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > on the COM tab. Looks like the install didnt not
> > > > > > > > > > > register
> > > > > something.
> > > > >
> > > > > > > > > > This is a
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > new Win7 machine with a brand new ASCOM install.
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > Robert
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > > > <mailto:ASCOM-Talk@yahoogroups.com>
> > > > >
> > > > > > > > > > , "paulkccd" <yh@ <mailto:yh@> > wrote:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM. You
> > > > > > > > > > > > can
> > > > add
> > > > > a
> > > > >
> > > > > > > > > > reference
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > to it from the .NET tab in Visual Studio Add
> > > > > > > > > > > References
> > > > > dialog.
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > Regards,
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > >     -Paul
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > > >
> > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
> > > > > > > > > > <robt2112@>
> > > > > wrote:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > That is what I was trying. I cant get access to
> > > > > ITelescope. I
> > > > >
> > > > > > > > > > added a
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > reference to DriverAccess and it complained that the
> > > > > interfaces were
> > > > >
> > > > > > > > > > defined
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > in ASCOM.Interfaces. I added that reference from
> COM,
> > > > > > > > > > > but
> > > > > dont see a
> > > > >
> > > > > > > > > > .NET
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > version. When I try to use ASCOM.ITelescope it
> > > > > > > > > > > complains
> > > > it
> > > > > doesn't
> > > > >
> > > > > > > > > > exist.
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > It won't let you create an instance with Type
> > > > Telescope.
> > > > > It says I
> > > > >
> > > > > > > > > > must use
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > ITelescope.
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > Robert
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > > >
> > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
> > > > wrote:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > And this is how I'd do it in C#:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >      ITelescope g;
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >      g =
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > .Gemin\
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > iTelescope.Telescope"));
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >      g.Connected = true;
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > Regards,
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >       -Paul
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > > >
> > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@>
> > > > wrote:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > Rob, what error do you get? Here's sample
> > > > > > > > > > > > > > > VB.Net
> > > > > code I sent
> > > > >
> > > > > > > > > > to
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > a
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > Gemini
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > user:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> CreateObject("ASCOM.GeminiTelescope.Telescope"
> > > > > > > > > > > > > > > )
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > g.Connected = True
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > You just need to add a reference
> > > > > > > > > > > > > > > ASCOM.Interfaces
> > > > > assembly.
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > Does this not work for you?
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > Regards,
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > -Paul
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > > >
> > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
> > > > > > > > > > robt2112@
> > > > > wrote:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > > So this is basic question. How do I access
> > > > > > > > > > > > > > > > and
> > > > use
> > > > > an ASCOM
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > > driver
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > in
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > .NET code. I keep running into cant create
> > > > instances
> > > > > that
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > represent
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > COM
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > components.
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > > Robert
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > ------------------------------------
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > For more information see http://ASCOM-Standards.org/
> > > > >
> > > > > > > > > > <http://ASCOM-Standards.org/> .
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > To unsubscribe from this group, send an email FROM
> THE
> > > > > ACCOUNT YOU
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > USED TO SUBSCRIBE(!) to:
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > > >
> > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > > Yahoo! Groups Links
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > > > >
> > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/>
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >     Individual Email | Traditional
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > > > >
> > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >     (Yahoo! ID required)
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> > > > >
> > > > > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > > > >
> > > > > > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > > > >
> > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > >     http://docs.yahoo.com/info/terms/
> > > > >
> > > > > > > > > > <http://docs.yahoo.com/info/terms/>
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > > > --
> > > > >
> > > > > > > > > > ExchangeDefender Message Security: Click below to
> verify
> > > > > authenticity
> > > > >
> > > > > > > > > >
> > > > >
> > http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from
> > =
> > > > > tim@
> > > > >
> > > > > > > > > > Complete email hygeine and business continuity
> solution
> > > > > available from http://www.tigranetworks.co.uk
> > > > >
> > > > > > > > > >
> > > > >
> > > > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > >
> > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ------------------------------------
> > > > >
> > > > >
> > > > >
> > > > > For more information see http://ASCOM-Standards.org/.
> > > > >
> > > > >
> > > > >
> > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT
> > YOU
> > > > USED
> > > > > TO SUBSCRIBE(!) to:
> > > > >
> > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > > >
> > > > >
> > > > >
> > > > > Yahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > > > >
> > > > >
> > > > >
> > > > >     Individual Email | Traditional
> > > > >
> > > > >
> > > > >
> > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > > > >
> > > > >     (Yahoo! ID required)
> > > > >
> > > > >
> > > > >
> > > > >     ASCOM-Talk-digest@yahoogroups.com
> > > > >
> > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > > > >
> > > > >
> > > > >
> > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > > > >
> > > > >
> > > > >
> > > > >     http://docs.yahoo.com/info/terms/
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > ExchangeDefender Message Security: Click below to verify
> > > > > authenticity
> > > > >
> > > >
> > http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from=
> > ti
> > > > m@
> > > > .
> > > > > Complete email hygeine and business continuity solution
> available
> > > > > from
> > > > http://www.tigranetworks.co.uk
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > For more information see http://ASCOM-Standards.org/.
> > > >
> > > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> > > > USED TO SUBSCRIBE(!) to:
> > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > >
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > ExchangeDefender Message Security: Click below to verify
> > > > authenticity
> > > >
> > http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from=
> > ti
> > > > m@ Complete email hygeine and business continuity solution
> available
> > > > from http://www.tigranetworks.co.uk
> > > >
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > For more information see http://ASCOM-Standards.org/.
> >
> > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> > USED TO SUBSCRIBE(!) to:
> > ASCOM-Talk-unsubscribe@yahoogroups.com
> >
> > Yahoo! Groups Links
> >
> >
> >
>
> --
> ExchangeDefender Message Security: Click below to verify authenticity
> http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=tim@...
> Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
>

#21185 From: "Tim Long" <Tim@...>
Date: Thu Jul 1, 2010 7:55 pm
Subject: RE: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
t_p_long
Send Email Send Email
 

OK, let me try this one more time. I have double checked all of this and I am 100% certain this is accurate. Let me be clear that I am talking about the RELEASED platform 5.5 and not anything that came from subversion.

 


There is no assembly called ASCOM.Interfaces.dll1 in Platform 5.5, it should not be in your filesystem anywhere2,3.

                                                                                          

The ASCOM Interfaces are COM objects and are obtained from the COM tab in the references dialog. You’ll note that what you are actually referencing is the type library, thus:

There is no bug, there should be no DLL file.

 

OK, now for the footnotes J

 


1 In fact, technically the interfaces are defined in a special type of .NET assembly – a Primary Interop Assembly – which is created by importing the type library (.tlb) file, is installed in the GAC (not the filesystem) and is given special treatment by visual studio. For all intents and purposes, it appears to be a COM object in Visual Studio and that’s how you should reference it.

2 In fact, items in the GAC are also in the filesystem, but their location is obfuscated and direct access is verboten. If you examine the folder c:\windows\assembly (in Windows Explorer) you’ll see that the assembly is indeed listed:

However, all it contains is a thin veneer of metadata that makes IntelliSense work properly. The actual interfaces are defined in the type library, which in turn is generated from an IDL file.

3 If you’ve checked out the code base from Subversion, then you’ll have the DLL file in your filesystem – but I’m ignoring that situation because it’s fairly uncommon for end users at the moment.

 

--Tim

 

> -----Original Message-----

> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> Talk@yahoogroups.com] On Behalf Of robt2112

> Sent: 01 July 2010 20:18

> To: ASCOM-Talk@yahoogroups.com

> Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

>

> The related issue then is if it is not there then you cant reference the

> interfaces in Visual Studio. It doesn't exist anywhere searching the entire c

> drive of the VM. The file is required for development in Visual Studio.

>

> Robert

>

> --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:

> >

> > I wouldn't necessarily expect it to be there. Let me try the same

> > thing myself and I'll get back to you.

> > --Tim

> >

> > > -----Original Message-----

> > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> > > Talk@yahoogroups.com] On Behalf Of robt2112

> > > Sent: 01 July 2010 18:06

> > > To: ASCOM-Talk@yahoogroups.com

> > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

> > >

> > > Just for completeness of testing this issue I started a VM with win

> > xp. Never

> > > had anything ascom related. Installed 5.0b. The C:\Program

> > Files\Common

> > > Files\ASCOM\.net is created with just the .vsi template in it.

> > >

> > > Install 5.5.1 update. The following is the contents of the .net

> > > folder

> > after

> > > install. ASCOM.Interfaces.dll is missing.

> > >

> > > Robert

> > >

> > >

> > >

> > > Directory of C:\Program Files\Common Files\ASCOM\.net

> > >

> > > 7/01/2010  01:02 PM    <DIR>          .

> > > 7/01/2010  01:02 PM    <DIR>          ..

> > > 1/21/2009  11:30 PM           523,264 ASCOM Diagnostics.exe

> > > 1/21/2009  11:30 PM           212,480 ASCOM Diagnostics.pdb

> > > 1/24/2009  09:50 PM           540,160 ASCOM.Astrometry.dll

> > > 1/24/2009  09:50 PM           249,344 ASCOM.Astrometry.pdb

> > > 7/01/2010  01:02 PM            28,824 ASCOM.Astrometry.tlb

> > > 1/24/2009  09:50 PM           247,602 ASCOM.Astrometry.xml

> > > 1/24/2009  09:49 PM             5,632 ASCOM.Attributes.dll

> > > 1/24/2009  09:49 PM            13,824 ASCOM.Attributes.pdb

> > > 7/10/2008  02:21 PM            53,248 ASCOM.DriverAccess.dll

> > > 7/10/2008  02:21 PM           105,984 ASCOM.DriverAccess.pdb

> > > 7/10/2008  02:21 PM           105,045 ASCOM.DriverAccess.XML

> > > 1/20/2009  08:24 AM             9,216 ASCOM.Exceptions.dll

> > > 1/20/2009  08:24 AM            21,933 ASCOM.Exceptions.XML

> > > 8/01/2009  04:33 PM           125,783 ASCOM.ico

> > > 1/20/2009  08:24 AM            14,336 ASCOM.IConform.dll

> > > 1/20/2009  08:24 AM            34,304 ASCOM.IConform.pdb

> > > 7/01/2010  01:02 PM             3,808 ASCOM.IConform.tlb

> > > 1/20/2009  08:24 AM             9,589 ASCOM.IConform.xml

> > > 1/24/2009  09:49 PM           251,392 ASCOM.Utilities.dll

> > > 1/24/2009  09:49 PM           214,528 ASCOM.Utilities.pdb

> > > 7/01/2010  01:02 PM            21,216 ASCOM.Utilities.tlb

> > > 1/24/2009  09:49 PM           171,112 ASCOM.Utilities.xml

> > > 1/17/2009  06:28 PM           397,566 ASCOMDriverTemplates.vsi

> > > 4/15/2009  11:58 PM               489 driveraccess.config

> > > 1/20/2009  08:25 AM            12,288 FusionLib.dll

> > > 1/20/2009  08:25 AM            15,872 FusionLib.pdb

> > > 1/20/2009  08:25 AM            15,360 GACInstall.exe

> > > 8/01/2009  04:33 PM            37,376 NOVAS-C.dll

> > > 8/01/2009  04:33 PM           207,872 NOVAS-C.pdb

> > > 8/01/2009  04:33 PM            52,224 NOVAS-C64.dll

> > > 8/01/2009  04:33 PM           199,680 NOVAS-C64.pdb

> > > 4/15/2009  11:58 PM             3,072

> > policy.1.0.ASCOM.DriverAccess.dll

> > > 1/17/2009  09:10 AM             3,584 policy.5.5.ASCOM.Astrometry.dll

> > > 1/17/2009  09:10 AM             3,584 policy.5.5.ASCOM.Utilities.dll

> > > 1/17/2009  09:10 AM               741 PublisherPolicy.xml

> > > 9/23/2009  10:13 PM               683 ReadMe55.txt

> > >              36 File(s)      3,913,015 bytes

> > >               2 Dir(s)  80,084,582,400 bytes free

> > >

> > > :\Program Files\Common Files\ASCOM\.net>

> > >

> > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:

> > > >

> > > > This was a fresh computer nothing installed. 5.0b first then

> > > > update

> > to 5.5.1.

> > > The COM interfaces were installed with the tlb file in the ASCOM

> > folder. The

> > > .net dll was missing in the .net folder.

> > > >

> > > > Robert

> > > >

> > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:

> > > > >

> > > > > I find it hard to believe that the problem is what you say it is.

> > > > > The interfaces PIA is so fundamental to ASCOM that we would have

> > > > > caught that a long time ago. Can we please be clear about

> > > > > version numbers - when you say "the installer" which version are

> > > > > you

> > talking

> > > about?

> > > > >

> > > > > To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not both).

> > > > > The 5.0a/b installer includes and installs the interfaces PIA in

> > the

> > > > > GAC, I am 100% certain that works correctly because it has been

> > > > > tested to death on many different systems, by all the ASCOM

> > > > > developers and beta testers and on many end user systems.

> > > > >

> > > > > Something about this incident doesn't make sense. I would like

> > > > > to get to the bottom of it, but I don't think it is a bug in the

> > installer.

> > > > >

> > > > > Regards,

> > > > > --Tim Long

> > > > >

> > > > >

> > > > > -----Original Message-----

> > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> > > Talk@yahoogroups.com]

> > > > > On Behalf Of robt2112

> > > > > Sent: 01 July 2010 14:57

> > > > > To: ASCOM-Talk@yahoogroups.com

> > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

> > > > >

> > > > > This was just a verification that it is a bug in the installer.

> > The

> > > > > file should have been installed. I verified that the file was

> > > > > missing and that putting the file in place solves the problem.

> > This

> > > > > should be fixed in the installation.

> > > > >

> > > > > Robert

> > > > >

> > > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:

> > > > > >

> > > > > > If you do that... you're on your own! We've got to be very

> > careful

> > > > > about

> > > > > > letting users do stuff like that because it will create

> > confusion

> > > > > > and

> > > > > a

> > > > > > support nightmare.

> > > > > >

> > > > > >

> > > > > >

> > > > > > ASCOM interfaces is (currently) a COM object that lives in the

> > > > > > GAC. It should be installed by the platform installer and

> > > > > > referenced from the COM tab of the references dialog.

> > > > > >

> > > > > > --Tim

> > > > > >

> > > > > >

> > > > > >

> > > > > > -----Original Message-----

> > > > > > From: ASCOM-Talk@yahoogroups.com

> > > > > > [mailto:ASCOM-Talk@yahoogroups.com]

> > > > > On

> > > > > > Behalf Of robt2112

> > > > > > Sent: 01 July 2010 02:20

> > > > > > To: ASCOM-Talk@yahoogroups.com

> > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

> > > > > >

> > > > > >

> > > > > >

> > > > > > Well... If I copy the dll from my svn download to common

> > > > > > files\ascom\.net then it shows up on my .NET references tab in

> > VS.

> > > > > > So

> > > > > I

> > > > > > think the problem is the dll is not included in the install.

> > > > > >

> > > > > >

> > > > > >

> > > > > > Robert

> > > > > >

> > > > > >

> > > > > >

> > > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@>

> > > wrote:

> > > > > >

> > > > > > >

> > > > > >

> > > > > > > Yes in windows\assembly it shows ASCOM.Interfaces that

> > > > > > > points

> > to

> > > > > > ASCOM.Interfaces.dll. The only thing that shows up in Visual

> > > > > > Studio is

> > > > > a

> > > > > > reference in COM to the tlb located in Program Files\Common

> > > > > > Files\ASCOM\Interfaces.

> > > > > >

> > > > > > >

> > > > > >

> > > > > > > I do have a copy of the dll in the Platform Dependancies

> > folder

> > > > > > > of

> > > > > the

> > > > > > ASCOM platform Drivers and Simulators that I downloaded from

> > SVN.

> > > > > > The dll doesn't seem to get installed with the platform install.

> > > > > >

> > > > > > >

> > > > > >

> > > > > > > Robert

> > > > > >

> > > > > > >

> > > > > >

> > > > > > > --- In ASCOM-Talk@yahoogroups.com, "paulkccd" <yh@> wrote:

> > > > > >

> > > > > > > >

> > > > > >

> > > > > > > > As far as I can tell, platform 5 installs

> > ASCOM.Interface.dll

> > > > > > > > in

> > > > > > GAC, not in Common Files\ASCOM. Check Windows\Assembly

> folder

> > > > > > to see

> > > > > if

> > > > > > it's there.

> > > > > >

> > > > > > > >

> > > > > >

> > > > > > > > Regards,

> > > > > >

> > > > > > > >

> > > > > >

> > > > > > > >     -Paul

> > > > > >

> > > > > > > >

> > > > > >

> > > > > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112"

> <robt2112@>

> > > wrote:

> > > > > >

> > > > > > > > >

> > > > > >

> > > > > > > > > Slight correction. I installed Platform 5.0b then

> > > > > > > > > updated

> > to

> > > > > > 5.5.1. Both show installed in programs and features.

> > > > > >

> > > > > > > > >

> > > > > >

> > > > > > > > > Robert

> > > > > >

> > > > > > > > >

> > > > > >

> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com, "robt2112"

> > > > > > > > > <robt2112@>

> > > wrote:

> > > > > >

> > > > > > > > > >

> > > > > >

> > > > > > > > > > Well I think what is wrong is the installer for 5.5.1.

> > > > > > > > > > This is

> > > > > a

> > > > > > brand new install. I havent installed any previous versions

> > which

> > > > > > are not available on the website. I just installed the latest

> > > > > > version. The Interfaces dll was not installed.

> > > > > >

> > > > > > > > > >

> > > > > >

> > > > > > > > > > I believe if you had installed a previous platform

> > version

> > > > > that

> > > > > > dll would be there. Since I installed fresh it didn't get on

> > > > > > my

> > > > > machine.

> > > > > >

> > > > > > > > > >

> > > > > >

> > > > > > > > > > Robert

> > > > > >

> > > > > > > > > >

> > > > > >

> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@>

> > > wrote:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform 5.5.

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > Paul is correct that it's a .NET assembly, but it is

> > > > > > > > > > > also a

> > > > > > COM Primary

> > > > > >

> > > > > > > > > > > Interop Assembly (PIA) so (confusingly) it show up

> > under

> > > > > > > > > > > the

> > > > > > COM tab as

> > > > > >

> > > > > > > > > > > shown here:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > So reference that, and also from the .NET tab, bring

> > in

> > > > > > > > > > > the

> > > > > >

> > > > > > > > > > > ASCOM.DriverAccess namespace thus:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > Your project's references would then look something

> > like

> > > > > this

> > > > > > (I'm using

> > > > > >

> > > > > > > > > > > C# in VS2010, yours may appear differently):

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > Then in visual studio, you can use some code like

> > > > > > > > > > > this to

> > > > > > test:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > using System;

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > using ASCOM.DriverAccess;

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > namespace ConsoleApplication1

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > {

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >     class Program

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >     {

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >         static void Main(string[] args)

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >         {

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >             var userChoice =

> > > > > > > > > > > Telescope.Choose(String.Empty);

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >             var scope = new Telescope(userChoice);

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >             scope.Connected = true;

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >             scope.Park();

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >             scope.Connected = false;

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >             scope.Dispose();

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >             scope = null;

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >         }

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >     }

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > }

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > This code does work, I just ran it. If you can't get

> > > > > > > > > > > this to

> > > > > > work, then

> > > > > >

> > > > > > > > > > > something is badly wrong and needs sorting out.

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > --Tim

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > -----Original Message-----

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > Talk@yahoogroups.com] On Behalf Of robt2112

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > Sent: 30 June 2010 20:53

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > To: ASCOM-Talk@yahoogroups.com

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM

> > driver

> > > > > > > > > > > > in

> > > > > > .NET

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > It should be, but its not on my .NET assembly tab

> > > > > > > > > > > > in

> > > > > visual

> > > > > > studio. I

> > > > > >

> > > > > > > > > > > only see it

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > on the COM tab. Looks like the install didnt not

> > > > > > > > > > > > register

> > > > > > something.

> > > > > >

> > > > > > > > > > > This is a

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > new Win7 machine with a brand new ASCOM install.

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > Robert

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > > > > > <mailto:ASCOM-Talk@yahoogroups.com>

> > > > > >

> > > > > > > > > > > , "paulkccd" <yh@ <mailto:yh@> > wrote:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM.

> > > > > > > > > > > > > You can

> > > > > add

> > > > > > a

> > > > > >

> > > > > > > > > > > reference

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > to it from the .NET tab in Visual Studio Add

> > > > > > > > > > > > References

> > > > > > dialog.

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > Regards,

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > >     -Paul

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > > > > >

> > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"

> > > > > > > > > > > <robt2112@>

> > > > > > wrote:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > That is what I was trying. I cant get access

> > > > > > > > > > > > > > to

> > > > > > ITelescope. I

> > > > > >

> > > > > > > > > > > added a

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > reference to DriverAccess and it complained that

> > > > > > > > > > > > the

> > > > > > interfaces were

> > > > > >

> > > > > > > > > > > defined

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > in ASCOM.Interfaces. I added that reference from

> > COM,

> > > > > > > > > > > > but

> > > > > > dont see a

> > > > > >

> > > > > > > > > > > .NET

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > version. When I try to use ASCOM.ITelescope it

> > > > > > > > > > > > complains

> > > > > it

> > > > > > doesn't

> > > > > >

> > > > > > > > > > > exist.

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > It won't let you create an instance with Type

> > > > > Telescope.

> > > > > > It says I

> > > > > >

> > > > > > > > > > > must use

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > ITelescope.

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > Robert

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > > > > >

> > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd"

> > > > > > > > > > > <yh@>

> > > > > wrote:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > And this is how I'd do it in C#:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >      ITelescope g;

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >      g =

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > .Gemin\

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > iTelescope.Telescope"));

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >      g.Connected = true;

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > Regards,

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >       -Paul

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > > > > >

> > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd"

> > > > > > > > > > > <yh@>

> > > > > wrote:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > Rob, what error do you get? Here's sample

> > > > > > > > > > > > > > > > VB.Net

> > > > > > code I sent

> > > > > >

> > > > > > > > > > > to

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > a

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > Gemini

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > user:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > CreateObject("ASCOM.GeminiTelescope.Telescope"

> > > > > > > > > > > > > > > > )

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > g.Connected = True

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > You just need to add a reference

> > > > > > > > > > > > > > > > ASCOM.Interfaces

> > > > > > assembly.

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > Does this not work for you?

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > Regards,

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > -Paul

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > > > > >

> > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"

> > > > > > > > > > > robt2112@

> > > > > > wrote:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > > So this is basic question. How do I

> > > > > > > > > > > > > > > > > access and

> > > > > use

> > > > > > an ASCOM

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > > driver

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > in

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > .NET code. I keep running into cant create

> > > > > instances

> > > > > > that

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > represent

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > COM

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > components.

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > > Robert

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > ------------------------------------

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > For more information see

> > > > > > > > > > > > http://ASCOM-Standards.org/

> > > > > >

> > > > > > > > > > > <http://ASCOM-Standards.org/> .

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > To unsubscribe from this group, send an email FROM

> > THE

> > > > > > ACCOUNT YOU

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > USED TO SUBSCRIBE(!) to:

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > > > > >

> > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > > Yahoo! Groups Links

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/

> > > > > >

> > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/>

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >     Individual Email | Traditional

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join

> > > > > >

> > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join>

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >     (Yahoo! ID required)

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com

> > > > > >

> > > > > > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com>

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com

> > > > > >

> > > > > > > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com

> > > > > >

> > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > >     http://docs.yahoo.com/info/terms/

> > > > > >

> > > > > > > > > > > <http://docs.yahoo.com/info/terms/>

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > > > --

> > > > > >

> > > > > > > > > > > ExchangeDefender Message Security: Click below to

> > verify

> > > > > > authenticity

> > > > > >

> > > > > > > > > > >

> > > > > >

> > >

> http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from

> > > =

> > > > > > tim@

> > > > > >

> > > > > > > > > > > Complete email hygeine and business continuity

> > solution

> > > > > > available from http://www.tigranetworks.co.uk

> > > > > >

> > > > > > > > > > >

> > > > > >

> > > > > > > > > >

> > > > > >

> > > > > > > > >

> > > > > >

> > > > > > > >

> > > > > >

> > > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > > ------------------------------------

> > > > > >

> > > > > >

> > > > > >

> > > > > > For more information see http://ASCOM-Standards.org/.

> > > > > >

> > > > > >

> > > > > >

> > > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT

> > > YOU

> > > > > USED

> > > > > > TO SUBSCRIBE(!) to:

> > > > > >

> > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > > > > >

> > > > > >

> > > > > >

> > > > > > Yahoo! Groups Links

> > > > > >

> > > > > >

> > > > > >

> > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/

> > > > > >

> > > > > >

> > > > > >

> > > > > >     Individual Email | Traditional

> > > > > >

> > > > > >

> > > > > >

> > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join

> > > > > >

> > > > > >     (Yahoo! ID required)

> > > > > >

> > > > > >

> > > > > >

> > > > > >     ASCOM-Talk-digest@yahoogroups.com

> > > > > >

> > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com

> > > > > >

> > > > > >

> > > > > >

> > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com

> > > > > >

> > > > > >

> > > > > >

> > > > > >     http://docs.yahoo.com/info/terms/

> > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > > --

> > > > > > ExchangeDefender Message Security: Click below to verify

> > > > > > authenticity

> > > > > >

> > > > >

> > >

> http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from=

> > > ti

> > > > > m@

> > > > > .

> > > > > > Complete email hygeine and business continuity solution

> > available

> > > > > > from

> > > > > http://www.tigranetworks.co.uk

> > > > > >

> > > > >

> > > > >

> > > > >

> > > > >

> > > > > ------------------------------------

> > > > >

> > > > > For more information see http://ASCOM-Standards.org/.

> > > > >

> > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT

> > > > > YOU USED TO SUBSCRIBE(!) to:

> > > > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > > > >

> > > > > Yahoo! Groups Links

> > > > >

> > > > >

> > > > >

> > > > >

> > > > > --

> > > > > ExchangeDefender Message Security: Click below to verify

> > > > > authenticity

> > > > >

> > >

> http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from=

> > > ti

> > > > > m@ Complete email hygeine and business continuity solution

> > available

> > > > > from http://www.tigranetworks.co.uk

> > > > >

> > > >

> > >

> > >

> > >

> > >

> > > ------------------------------------

> > >

> > > For more information see http://ASCOM-Standards.org/.

> > >

> > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU

> > > USED TO SUBSCRIBE(!) to:

> > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > >

> > > Yahoo! Groups Links

> > >

> > >

> > >

> >

> > --

> > ExchangeDefender Message Security: Click below to verify authenticity

> >

> http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=t

> im@...

> > Complete email hygeine and business continuity solution available from

> > http://www.tigranetworks.co.uk

> >

>

>

>

>

> ------------------------------------

>

> For more information see http://ASCOM-Standards.org/.

>

> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU

> USED TO SUBSCRIBE(!) to:

> ASCOM-Talk-unsubscribe@yahoogroups.com

>

> Yahoo! Groups Links

>

> <*> To visit your group on the web, go to:

>     http://groups.yahoo.com/group/ASCOM-Talk/

>

> <*> Your email settings:

>     Individual Email | Traditional

>

> <*> To change settings online go to:

>     http://groups.yahoo.com/group/ASCOM-Talk/join

>     (Yahoo! ID required)

>

> <*> To change settings via email:

>     ASCOM-Talk-digest@yahoogroups.com

>     ASCOM-Talk-fullfeatured@yahoogroups.com

>

> <*> To unsubscribe from this group, send an email to:

>     ASCOM-Talk-unsubscribe@yahoogroups.com

>

> <*> Your use of Yahoo! Groups is subject to:

>     http://docs.yahoo.com/info/terms/

 


ExchangeDefender Message Security: Check Authenticity
Complete email hygeine and business continuity solution available from TiGra Networks


#21186 From: "robt2112" <robt2112@...>
Date: Thu Jul 1, 2010 8:32 pm
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
robt2112
Send Email Send Email
 
Well unfortunately if you try to develop with platform 5.5 it doesnt work unless
you have the dll. Visual Studio complains that you must add a reference to
ASCOM.Interfaces when you add DriverAcess. The message the interface are defined
in ASCOM.Interfaces and must be referenced in the project.

The only way to actually develop in .NET with platform 5.5 is to include the
ghost ASCOM.Interfaces.dll. Now also if you look in the GAC ASCOM.Interfaces.dll
is registered, but there is no actual file. Look at windows/assembly you will
see ASCOM.Interfaces and the Original Filename property points to
ASCOM.Interfaces.dll. This file exists nowhere on the system.

So in platform 5.5 dependencies in SVN the mystery dll is there and is part of
the dependent assemblies. So without it you can't develop a driver. So if you
want to see further put visual studio express in your clean vm and try to write
a .NET driver that references one of the interfaces.


Robert




--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> OK, let me try this one more time. I have double checked all of this and
> I am 100% certain this is accurate. Let me be clear that I am talking
> about the RELEASED platform 5.5 and not anything that came from
> subversion.
>
>
>
>
> There is no assembly called ASCOM.Interfaces.dll1 in Platform 5.5, it
> should not be in your filesystem anywhere2,3.
>
>
>
>
>
>
> The ASCOM Interfaces are COM objects and are obtained from the COM tab
> in the references dialog. You'll note that what you are actually
> referencing is the type library, thus:
>
>
>
> There is no bug, there should be no DLL file.
>
>
>
> OK, now for the footnotes J
>
>
>
> ________________________________
>
> 1 In fact, technically the interfaces are defined in a special type of
> .NET assembly - a Primary Interop Assembly - which is created by
> importing the type library (.tlb) file, is installed in the GAC (not the
> filesystem) and is given special treatment by visual studio. For all
> intents and purposes, it appears to be a COM object in Visual Studio and
> that's how you should reference it.
>
> 2 In fact, items in the GAC are also in the filesystem, but their
> location is obfuscated and direct access is verboten. If you examine the
> folder c:\windows\assembly (in Windows Explorer) you'll see that the
> assembly is indeed listed:
>
> However, all it contains is a thin veneer of metadata that makes
> IntelliSense work properly. The actual interfaces are defined in the
> type library, which in turn is generated from an IDL file.
>
> 3 If you've checked out the code base from Subversion, then you'll have
> the DLL file in your filesystem - but I'm ignoring that situation
> because it's fairly uncommon for end users at the moment.
>
>
>
> --Tim
>
>
>
> > -----Original Message-----
>
> > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > Talk@yahoogroups.com] On Behalf Of robt2112
>
> > Sent: 01 July 2010 20:18
>
> > To: ASCOM-Talk@yahoogroups.com
>
> > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
> >
>
> > The related issue then is if it is not there then you cant reference
> the
>
> > interfaces in Visual Studio. It doesn't exist anywhere searching the
> entire c
>
> > drive of the VM. The file is required for development in Visual
> Studio.
>
> >
>
> > Robert
>
> >
>
> > --- In ASCOM-Talk@yahoogroups.com <mailto:ASCOM-Talk@yahoogroups.com>
> , "Tim Long" <Tim@ <mailto:Tim@> > wrote:
>
> > >
>
> > > I wouldn't necessarily expect it to be there. Let me try the same
>
> > > thing myself and I'll get back to you.
>
> > > --Tim
>
> > >
>
> > > > -----Original Message-----
>
> > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > > > Talk@yahoogroups.com] On Behalf Of robt2112
>
> > > > Sent: 01 July 2010 18:06
>
> > > > To: ASCOM-Talk@yahoogroups.com
>
> > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
> > > >
>
> > > > Just for completeness of testing this issue I started a VM with
> win
>
> > > xp. Never
>
> > > > had anything ascom related. Installed 5.0b. The C:\Program
>
> > > Files\Common
>
> > > > Files\ASCOM\.net is created with just the .vsi template in it.
>
> > > >
>
> > > > Install 5.5.1 update. The following is the contents of the .net
>
> > > > folder
>
> > > after
>
> > > > install. ASCOM.Interfaces.dll is missing.
>
> > > >
>
> > > > Robert
>
> > > >
>
> > > >
>
> > > >
>
> > > > Directory of C:\Program Files\Common Files\ASCOM\.net
>
> > > >
>
> > > > 7/01/2010  01:02 PM    <DIR>          .
>
> > > > 7/01/2010  01:02 PM    <DIR>          ..
>
> > > > 1/21/2009  11:30 PM           523,264 ASCOM Diagnostics.exe
>
> > > > 1/21/2009  11:30 PM           212,480 ASCOM Diagnostics.pdb
>
> > > > 1/24/2009  09:50 PM           540,160 ASCOM.Astrometry.dll
>
> > > > 1/24/2009  09:50 PM           249,344 ASCOM.Astrometry.pdb
>
> > > > 7/01/2010  01:02 PM            28,824 ASCOM.Astrometry.tlb
>
> > > > 1/24/2009  09:50 PM           247,602 ASCOM.Astrometry.xml
>
> > > > 1/24/2009  09:49 PM             5,632 ASCOM.Attributes.dll
>
> > > > 1/24/2009  09:49 PM            13,824 ASCOM.Attributes.pdb
>
> > > > 7/10/2008  02:21 PM            53,248 ASCOM.DriverAccess.dll
>
> > > > 7/10/2008  02:21 PM           105,984 ASCOM.DriverAccess.pdb
>
> > > > 7/10/2008  02:21 PM           105,045 ASCOM.DriverAccess.XML
>
> > > > 1/20/2009  08:24 AM             9,216 ASCOM.Exceptions.dll
>
> > > > 1/20/2009  08:24 AM            21,933 ASCOM.Exceptions.XML
>
> > > > 8/01/2009  04:33 PM           125,783 ASCOM.ico
>
> > > > 1/20/2009  08:24 AM            14,336 ASCOM.IConform.dll
>
> > > > 1/20/2009  08:24 AM            34,304 ASCOM.IConform.pdb
>
> > > > 7/01/2010  01:02 PM             3,808 ASCOM.IConform.tlb
>
> > > > 1/20/2009  08:24 AM             9,589 ASCOM.IConform.xml
>
> > > > 1/24/2009  09:49 PM           251,392 ASCOM.Utilities.dll
>
> > > > 1/24/2009  09:49 PM           214,528 ASCOM.Utilities.pdb
>
> > > > 7/01/2010  01:02 PM            21,216 ASCOM.Utilities.tlb
>
> > > > 1/24/2009  09:49 PM           171,112 ASCOM.Utilities.xml
>
> > > > 1/17/2009  06:28 PM           397,566 ASCOMDriverTemplates.vsi
>
> > > > 4/15/2009  11:58 PM               489 driveraccess.config
>
> > > > 1/20/2009  08:25 AM            12,288 FusionLib.dll
>
> > > > 1/20/2009  08:25 AM            15,872 FusionLib.pdb
>
> > > > 1/20/2009  08:25 AM            15,360 GACInstall.exe
>
> > > > 8/01/2009  04:33 PM            37,376 NOVAS-C.dll
>
> > > > 8/01/2009  04:33 PM           207,872 NOVAS-C.pdb
>
> > > > 8/01/2009  04:33 PM            52,224 NOVAS-C64.dll
>
> > > > 8/01/2009  04:33 PM           199,680 NOVAS-C64.pdb
>
> > > > 4/15/2009  11:58 PM             3,072
>
> > > policy.1.0.ASCOM.DriverAccess.dll
>
> > > > 1/17/2009  09:10 AM             3,584
> policy.5.5.ASCOM.Astrometry.dll
>
> > > > 1/17/2009  09:10 AM             3,584
> policy.5.5.ASCOM.Utilities.dll
>
> > > > 1/17/2009  09:10 AM               741 PublisherPolicy.xml
>
> > > > 9/23/2009  10:13 PM               683 ReadMe55.txt
>
> > > >              36 File(s)      3,913,015 bytes
>
> > > >               2 Dir(s)  80,084,582,400 bytes free
>
> > > >
>
> > > > :\Program Files\Common Files\ASCOM\.net>
>
> > > >
>
> > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@> wrote:
>
> > > > >
>
> > > > > This was a fresh computer nothing installed. 5.0b first then
>
> > > > > update
>
> > > to 5.5.1.
>
> > > > The COM interfaces were installed with the tlb file in the ASCOM
>
> > > folder. The
>
> > > > .net dll was missing in the .net folder.
>
> > > > >
>
> > > > > Robert
>
> > > > >
>
> > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@> wrote:
>
> > > > > >
>
> > > > > > I find it hard to believe that the problem is what you say it
> is.
>
> > > > > > The interfaces PIA is so fundamental to ASCOM that we would
> have
>
> > > > > > caught that a long time ago. Can we please be clear about
>
> > > > > > version numbers - when you say "the installer" which version
> are
>
> > > > > > you
>
> > > talking
>
> > > > about?
>
> > > > > >
>
> > > > > > To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not
> both).
>
> > > > > > The 5.0a/b installer includes and installs the interfaces PIA
> in
>
> > > the
>
> > > > > > GAC, I am 100% certain that works correctly because it has
> been
>
> > > > > > tested to death on many different systems, by all the ASCOM
>
> > > > > > developers and beta testers and on many end user systems.
>
> > > > > >
>
> > > > > > Something about this incident doesn't make sense. I would like
>
> > > > > > to get to the bottom of it, but I don't think it is a bug in
> the
>
> > > installer.
>
> > > > > >
>
> > > > > > Regards,
>
> > > > > > --Tim Long
>
> > > > > >
>
> > > > > >
>
> > > > > > -----Original Message-----
>
> > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > > > Talk@yahoogroups.com]
>
> > > > > > On Behalf Of robt2112
>
> > > > > > Sent: 01 July 2010 14:57
>
> > > > > > To: ASCOM-Talk@yahoogroups.com
>
> > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
> > > > > >
>
> > > > > > This was just a verification that it is a bug in the
> installer.
>
> > > The
>
> > > > > > file should have been installed. I verified that the file was
>
> > > > > > missing and that putting the file in place solves the problem.
>
> > > This
>
> > > > > > should be fixed in the installation.
>
> > > > > >
>
> > > > > > Robert
>
> > > > > >
>
> > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@> wrote:
>
> > > > > > >
>
> > > > > > > If you do that... you're on your own! We've got to be very
>
> > > careful
>
> > > > > > about
>
> > > > > > > letting users do stuff like that because it will create
>
> > > confusion
>
> > > > > > > and
>
> > > > > > a
>
> > > > > > > support nightmare.
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > ASCOM interfaces is (currently) a COM object that lives in
> the
>
> > > > > > > GAC. It should be installed by the platform installer and
>
> > > > > > > referenced from the COM tab of the references dialog.
>
> > > > > > >
>
> > > > > > > --Tim
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > -----Original Message-----
>
> > > > > > > From: ASCOM-Talk@yahoogroups.com
>
> > > > > > > [mailto:ASCOM-Talk@yahoogroups.com]
>
> > > > > > On
>
> > > > > > > Behalf Of robt2112
>
> > > > > > > Sent: 01 July 2010 02:20
>
> > > > > > > To: ASCOM-Talk@yahoogroups.com
>
> > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in
> .NET
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > Well... If I copy the dll from my svn download to common
>
> > > > > > > files\ascom\.net then it shows up on my .NET references tab
> in
>
> > > VS.
>
> > > > > > > So
>
> > > > > > I
>
> > > > > > > think the problem is the dll is not included in the install.
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > Robert
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@>
>
> > > > wrote:
>
> > > > > > >
>
> > > > > > > >
>
> > > > > > >
>
> > > > > > > > Yes in windows\assembly it shows ASCOM.Interfaces that
>
> > > > > > > > points
>
> > > to
>
> > > > > > > ASCOM.Interfaces.dll. The only thing that shows up in Visual
>
> > > > > > > Studio is
>
> > > > > > a
>
> > > > > > > reference in COM to the tlb located in Program Files\Common
>
> > > > > > > Files\ASCOM\Interfaces.
>
> > > > > > >
>
> > > > > > > >
>
> > > > > > >
>
> > > > > > > > I do have a copy of the dll in the Platform Dependancies
>
> > > folder
>
> > > > > > > > of
>
> > > > > > the
>
> > > > > > > ASCOM platform Drivers and Simulators that I downloaded from
>
> > > SVN.
>
> > > > > > > The dll doesn't seem to get installed with the platform
> install.
>
> > > > > > >
>
> > > > > > > >
>
> > > > > > >
>
> > > > > > > > Robert
>
> > > > > > >
>
> > > > > > > >
>
> > > > > > >
>
> > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:
>
> > > > > > >
>
> > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > As far as I can tell, platform 5 installs
>
> > > ASCOM.Interface.dll
>
> > > > > > > > > in
>
> > > > > > > GAC, not in Common Files\ASCOM. Check Windows\Assembly
>
> > folder
>
> > > > > > > to see
>
> > > > > > if
>
> > > > > > > it's there.
>
> > > > > > >
>
> > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > Regards,
>
> > > > > > >
>
> > > > > > > > >
>
> > > > > > >
>
> > > > > > > > >     -Paul
>
> > > > > > >
>
> > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
>
> > <robt2112@>
>
> > > > wrote:
>
> > > > > > >
>
> > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > Slight correction. I installed Platform 5.0b then
>
> > > > > > > > > > updated
>
> > > to
>
> > > > > > > 5.5.1. Both show installed in programs and features.
>
> > > > > > >
>
> > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > Robert
>
> > > > > > >
>
> > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
>
> > > > > > > > > > <robt2112@>
>
> > > > wrote:
>
> > > > > > >
>
> > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > Well I think what is wrong is the installer for
> 5.5.1.
>
> > > > > > > > > > > This is
>
> > > > > > a
>
> > > > > > > brand new install. I havent installed any previous versions
>
> > > which
>
> > > > > > > are not available on the website. I just installed the
> latest
>
> > > > > > > version. The Interfaces dll was not installed.
>
> > > > > > >
>
> > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > I believe if you had installed a previous platform
>
> > > version
>
> > > > > > that
>
> > > > > > > dll would be there. Since I installed fresh it didn't get on
>
> > > > > > > my
>
> > > > > > machine.
>
> > > > > > >
>
> > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > Robert
>
> > > > > > >
>
> > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@>
>
> > > > wrote:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform
> 5.5.
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > Paul is correct that it's a .NET assembly, but it
> is
>
> > > > > > > > > > > > also a
>
> > > > > > > COM Primary
>
> > > > > > >
>
> > > > > > > > > > > > Interop Assembly (PIA) so (confusingly) it show up
>
> > > under
>
> > > > > > > > > > > > the
>
> > > > > > > COM tab as
>
> > > > > > >
>
> > > > > > > > > > > > shown here:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > So reference that, and also from the .NET tab,
> bring
>
> > > in
>
> > > > > > > > > > > > the
>
> > > > > > >
>
> > > > > > > > > > > > ASCOM.DriverAccess namespace thus:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > Your project's references would then look
> something
>
> > > like
>
> > > > > > this
>
> > > > > > > (I'm using
>
> > > > > > >
>
> > > > > > > > > > > > C# in VS2010, yours may appear differently):
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > Then in visual studio, you can use some code like
>
> > > > > > > > > > > > this to
>
> > > > > > > test:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > using System;
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > using ASCOM.DriverAccess;
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > namespace ConsoleApplication1
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > {
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >     class Program
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >     {
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >         static void Main(string[] args)
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >         {
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >             var userChoice =
>
> > > > > > > > > > > > Telescope.Choose(String.Empty);
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >             var scope = new Telescope(userChoice);
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >             scope.Connected = true;
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >             scope.Park();
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >             scope.Connected = false;
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >             scope.Dispose();
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >             scope = null;
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >         }
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >     }
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > }
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > This code does work, I just ran it. If you can't
> get
>
> > > > > > > > > > > > this to
>
> > > > > > > work, then
>
> > > > > > >
>
> > > > > > > > > > > > something is badly wrong and needs sorting out.
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > --Tim
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > -----Original Message-----
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > Talk@yahoogroups.com
> <mailto:Talk@yahoogroups.com> ] On Behalf Of robt2112
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > Sent: 30 June 2010 20:53
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > To: ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM
>
> > > driver
>
> > > > > > > > > > > > > in
>
> > > > > > > .NET
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > It should be, but its not on my .NET assembly
> tab
>
> > > > > > > > > > > > > in
>
> > > > > > visual
>
> > > > > > > studio. I
>
> > > > > > >
>
> > > > > > > > > > > > only see it
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > on the COM tab. Looks like the install didnt not
>
> > > > > > > > > > > > > register
>
> > > > > > > something.
>
> > > > > > >
>
> > > > > > > > > > > > This is a
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > new Win7 machine with a brand new ASCOM install.
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > Robert
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> >
>
> > > > > > >
>
> > > > > > > > > > > > , "paulkccd" <yh@ <mailto:yh@ <mailto:yh@> > >
> wrote:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM.
>
> > > > > > > > > > > > > > You can
>
> > > > > > add
>
> > > > > > > a
>
> > > > > > >
>
> > > > > > > > > > > > reference
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > to it from the .NET tab in Visual Studio Add
>
> > > > > > > > > > > > > References
>
> > > > > > > dialog.
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > Regards,
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > >     -Paul
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > > > > >
>
> > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"
>
> > > > > > > > > > > > <robt2112@>
>
> > > > > > > wrote:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > That is what I was trying. I cant get access
>
> > > > > > > > > > > > > > > to
>
> > > > > > > ITelescope. I
>
> > > > > > >
>
> > > > > > > > > > > > added a
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > reference to DriverAccess and it complained that
>
> > > > > > > > > > > > > the
>
> > > > > > > interfaces were
>
> > > > > > >
>
> > > > > > > > > > > > defined
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > in ASCOM.Interfaces. I added that reference from
>
> > > COM,
>
> > > > > > > > > > > > > but
>
> > > > > > > dont see a
>
> > > > > > >
>
> > > > > > > > > > > > .NET
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > version. When I try to use ASCOM.ITelescope it
>
> > > > > > > > > > > > > complains
>
> > > > > > it
>
> > > > > > > doesn't
>
> > > > > > >
>
> > > > > > > > > > > > exist.
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > It won't let you create an instance with
> Type
>
> > > > > > Telescope.
>
> > > > > > > It says I
>
> > > > > > >
>
> > > > > > > > > > > > must use
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > ITelescope.
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > Robert
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > > > > >
>
> > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "paulkccd"
>
> > > > > > > > > > > > <yh@>
>
> > > > > > wrote:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > And this is how I'd do it in C#:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >      ITelescope g;
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >      g =
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > .Gemin\
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > iTelescope.Telescope"));
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >      g.Connected = true;
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > Regards,
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >       -Paul
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > > > > >
>
> > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "paulkccd"
>
> > > > > > > > > > > > <yh@>
>
> > > > > > wrote:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > Rob, what error do you get? Here's
> sample
>
> > > > > > > > > > > > > > > > > VB.Net
>
> > > > > > > code I sent
>
> > > > > > >
>
> > > > > > > > > > > > to
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > a
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > Gemini
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > user:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > CreateObject("ASCOM.GeminiTelescope.Telescope"
>
> > > > > > > > > > > > > > > > > )
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > g.Connected = True
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > You just need to add a reference
>
> > > > > > > > > > > > > > > > > ASCOM.Interfaces
>
> > > > > > > assembly.
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > Does this not work for you?
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > Regards,
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > -Paul
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > > > > >
>
> > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"
>
> > > > > > > > > > > > robt2112@
>
> > > > > > > wrote:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > > So this is basic question. How do I
>
> > > > > > > > > > > > > > > > > > access and
>
> > > > > > use
>
> > > > > > > an ASCOM
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > > driver
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > in
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > .NET code. I keep running into cant
> create
>
> > > > > > instances
>
> > > > > > > that
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > represent
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > COM
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > components.
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > > Robert
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > ------------------------------------
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > For more information see
>
> > > > > > > > > > > > > http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/>
>
> > > > > > >
>
> > > > > > > > > > > > <http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/> > .
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > To unsubscribe from this group, send an email
> FROM
>
> > > THE
>
> > > > > > > ACCOUNT YOU
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > USED TO SUBSCRIBE(!) to:
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > > > > >
>
> > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > > Yahoo! Groups Links
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> > > > > > >
>
> > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/> >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >     Individual Email | Traditional
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
> http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> > > > > > >
>
> > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join> >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >     (Yahoo! ID required)
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> > > > > > >
>
> > > > > > > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com> >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> > > > > > >
>
> > > > > > > > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com> >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > > > > >
>
> > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > >     http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/>
>
> > > > > > >
>
> > > > > > > > > > > > <http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/> >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > > > --
>
> > > > > > >
>
> > > > > > > > > > > > ExchangeDefender Message Security: Click below to
>
> > > verify
>
> > > > > > > authenticity
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > >
>
> > http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from
> <http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from>
>
> > > > =
>
> > > > > > > tim@
>
> > > > > > >
>
> > > > > > > > > > > > Complete email hygeine and business continuity
>
> > > solution
>
> > > > > > > available from http://www.tigranetworks.co.uk
> <http://www.tigranetworks.co.uk>
>
> > > > > > >
>
> > > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > > >
>
> > > > > > >
>
> > > > > > > > >
>
> > > > > > >
>
> > > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > ------------------------------------
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/> .
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > To unsubscribe from this group, send an email FROM THE
> ACCOUNT
>
> > > > YOU
>
> > > > > > USED
>
> > > > > > > TO SUBSCRIBE(!) to:
>
> > > > > > >
>
> > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > Yahoo! Groups Links
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >     Individual Email | Traditional
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> > > > > > >
>
> > > > > > >     (Yahoo! ID required)
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> > > > > > >
>
> > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >     http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/>
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > >
>
> > > > > > > --
>
> > > > > > > ExchangeDefender Message Security: Click below to verify
>
> > > > > > > authenticity
>
> > > > > > >
>
> > > > > >
>
> > > >
>
> > http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from
> <http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from> =
>
> > > > ti
>
> > > > > > m@
>
> > > > > > .
>
> > > > > > > Complete email hygeine and business continuity solution
>
> > > available
>
> > > > > > > from
>
> > > > > > http://www.tigranetworks.co.uk
> <http://www.tigranetworks.co.uk>
>
> > > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > ------------------------------------
>
> > > > > >
>
> > > > > > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/> .
>
> > > > > >
>
> > > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT
>
> > > > > > YOU USED TO SUBSCRIBE(!) to:
>
> > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > > > >
>
> > > > > > Yahoo! Groups Links
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > >
>
> > > > > > --
>
> > > > > > ExchangeDefender Message Security: Click below to verify
>
> > > > > > authenticity
>
> > > > > >
>
> > > >
>
> > http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from
> <http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from> =
>
> > > > ti
>
> > > > > > m@ Complete email hygeine and business continuity solution
>
> > > available
>
> > > > > > from http://www.tigranetworks.co.uk
> <http://www.tigranetworks.co.uk>
>
> > > > > >
>
> > > > >
>
> > > >
>
> > > >
>
> > > >
>
> > > >
>
> > > > ------------------------------------
>
> > > >
>
> > > > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/> .
>
> > > >
>
> > > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
>
> > > > USED TO SUBSCRIBE(!) to:
>
> > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > >
>
> > > > Yahoo! Groups Links
>
> > > >
>
> > > >
>
> > > >
>
> > >
>
> > > --
>
> > > ExchangeDefender Message Security: Click below to verify
> authenticity
>
> > >
>
> > http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=t
> <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=tim@>
>
>
> > im@
> <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=tim@>
> ...
>
> > > Complete email hygeine and business continuity solution available
> from
>
> > > http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk>
>
> > >
>
> >
>
> >
>
> >
>
> >
>
> > ------------------------------------
>
> >
>
> > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/> .
>
> >
>
> > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
>
> > USED TO SUBSCRIBE(!) to:
>
> > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> >
>
> > Yahoo! Groups Links
>
> >
>
> >     http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> >
>
> >     Individual Email | Traditional
>
> >
>
> >     http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> >     (Yahoo! ID required)
>
> >
>
> >     ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> >     ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> >
>
> >     ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> >
>
> >     http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/>
>
>
>
>
> --
> ExchangeDefender Message Security: Click below to verify authenticity
> http://www.exchangedefender.com/verify.asp?id=o61JtsK5023776&from=tim@...
> Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
>

#21187 From: "paulkccd" <yh@...>
Date: Thu Jul 1, 2010 8:47 pm
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
paulkccd
Send Email Send Email
 
Robert, check under Windows\Assembly\GAC_MSIL\ASCOM.Interfaces\. You should be
able to see a folder that starts with 1.0.0.0_... and contains the actual DLL.
This is installed by platform 5.0 install.

At least that's where the 5.0b installer put it on my clean XP VM.

Regards,

     -Paul


--- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@...> wrote:
>
> Well unfortunately if you try to develop with platform 5.5 it doesnt work
unless you have the dll. Visual Studio complains that you must add a reference
to ASCOM.Interfaces when you add DriverAcess. The message the interface are
defined in ASCOM.Interfaces and must be referenced in the project.
>
> The only way to actually develop in .NET with platform 5.5 is to include the
ghost ASCOM.Interfaces.dll. Now also if you look in the GAC ASCOM.Interfaces.dll
is registered, but there is no actual file. Look at windows/assembly you will
see ASCOM.Interfaces and the Original Filename property points to
ASCOM.Interfaces.dll. This file exists nowhere on the system.
>
> So in platform 5.5 dependencies in SVN the mystery dll is there and is part of
the dependent assemblies. So without it you can't develop a driver. So if you
want to see further put visual studio express in your clean vm and try to write
a .NET driver that references one of the interfaces.
>
>
> Robert
>
>
>
>
> --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> >
> > OK, let me try this one more time. I have double checked all of this and
> > I am 100% certain this is accurate. Let me be clear that I am talking
> > about the RELEASED platform 5.5 and not anything that came from
> > subversion.
> >
> >
> >
> >
> > There is no assembly called ASCOM.Interfaces.dll1 in Platform 5.5, it
> > should not be in your filesystem anywhere2,3.
> >
> >
> >
> >
> >
> >
> > The ASCOM Interfaces are COM objects and are obtained from the COM tab
> > in the references dialog. You'll note that what you are actually
> > referencing is the type library, thus:
> >
> >
> >
> > There is no bug, there should be no DLL file.
> >
> >
> >
> > OK, now for the footnotes J
> >
> >
> >
> > ________________________________
> >
> > 1 In fact, technically the interfaces are defined in a special type of
> > .NET assembly - a Primary Interop Assembly - which is created by
> > importing the type library (.tlb) file, is installed in the GAC (not the
> > filesystem) and is given special treatment by visual studio. For all
> > intents and purposes, it appears to be a COM object in Visual Studio and
> > that's how you should reference it.
> >
> > 2 In fact, items in the GAC are also in the filesystem, but their
> > location is obfuscated and direct access is verboten. If you examine the
> > folder c:\windows\assembly (in Windows Explorer) you'll see that the
> > assembly is indeed listed:
> >
> > However, all it contains is a thin veneer of metadata that makes
> > IntelliSense work properly. The actual interfaces are defined in the
> > type library, which in turn is generated from an IDL file.
> >
> > 3 If you've checked out the code base from Subversion, then you'll have
> > the DLL file in your filesystem - but I'm ignoring that situation
> > because it's fairly uncommon for end users at the moment.
> >
> >
> >
> > --Tim
> >
> >
> >
> > > -----Original Message-----
> >
> > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> >
> > > Talk@yahoogroups.com] On Behalf Of robt2112
> >
> > > Sent: 01 July 2010 20:18
> >
> > > To: ASCOM-Talk@yahoogroups.com
> >
> > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> >
> > >
> >
> > > The related issue then is if it is not there then you cant reference
> > the
> >
> > > interfaces in Visual Studio. It doesn't exist anywhere searching the
> > entire c
> >
> > > drive of the VM. The file is required for development in Visual
> > Studio.
> >
> > >
> >
> > > Robert
> >
> > >
> >
> > > --- In ASCOM-Talk@yahoogroups.com <mailto:ASCOM-Talk@yahoogroups.com>
> > , "Tim Long" <Tim@ <mailto:Tim@> > wrote:
> >
> > > >
> >
> > > > I wouldn't necessarily expect it to be there. Let me try the same
> >
> > > > thing myself and I'll get back to you.
> >
> > > > --Tim
> >
> > > >
> >
> > > > > -----Original Message-----
> >
> > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> >
> > > > > Talk@yahoogroups.com] On Behalf Of robt2112
> >
> > > > > Sent: 01 July 2010 18:06
> >
> > > > > To: ASCOM-Talk@yahoogroups.com
> >
> > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> >
> > > > >
> >
> > > > > Just for completeness of testing this issue I started a VM with
> > win
> >
> > > > xp. Never
> >
> > > > > had anything ascom related. Installed 5.0b. The C:\Program
> >
> > > > Files\Common
> >
> > > > > Files\ASCOM\.net is created with just the .vsi template in it.
> >
> > > > >
> >
> > > > > Install 5.5.1 update. The following is the contents of the .net
> >
> > > > > folder
> >
> > > > after
> >
> > > > > install. ASCOM.Interfaces.dll is missing.
> >
> > > > >
> >
> > > > > Robert
> >
> > > > >
> >
> > > > >
> >
> > > > >
> >
> > > > > Directory of C:\Program Files\Common Files\ASCOM\.net
> >
> > > > >
> >
> > > > > 7/01/2010  01:02 PM    <DIR>          .
> >
> > > > > 7/01/2010  01:02 PM    <DIR>          ..
> >
> > > > > 1/21/2009  11:30 PM           523,264 ASCOM Diagnostics.exe
> >
> > > > > 1/21/2009  11:30 PM           212,480 ASCOM Diagnostics.pdb
> >
> > > > > 1/24/2009  09:50 PM           540,160 ASCOM.Astrometry.dll
> >
> > > > > 1/24/2009  09:50 PM           249,344 ASCOM.Astrometry.pdb
> >
> > > > > 7/01/2010  01:02 PM            28,824 ASCOM.Astrometry.tlb
> >
> > > > > 1/24/2009  09:50 PM           247,602 ASCOM.Astrometry.xml
> >
> > > > > 1/24/2009  09:49 PM             5,632 ASCOM.Attributes.dll
> >
> > > > > 1/24/2009  09:49 PM            13,824 ASCOM.Attributes.pdb
> >
> > > > > 7/10/2008  02:21 PM            53,248 ASCOM.DriverAccess.dll
> >
> > > > > 7/10/2008  02:21 PM           105,984 ASCOM.DriverAccess.pdb
> >
> > > > > 7/10/2008  02:21 PM           105,045 ASCOM.DriverAccess.XML
> >
> > > > > 1/20/2009  08:24 AM             9,216 ASCOM.Exceptions.dll
> >
> > > > > 1/20/2009  08:24 AM            21,933 ASCOM.Exceptions.XML
> >
> > > > > 8/01/2009  04:33 PM           125,783 ASCOM.ico
> >
> > > > > 1/20/2009  08:24 AM            14,336 ASCOM.IConform.dll
> >
> > > > > 1/20/2009  08:24 AM            34,304 ASCOM.IConform.pdb
> >
> > > > > 7/01/2010  01:02 PM             3,808 ASCOM.IConform.tlb
> >
> > > > > 1/20/2009  08:24 AM             9,589 ASCOM.IConform.xml
> >
> > > > > 1/24/2009  09:49 PM           251,392 ASCOM.Utilities.dll
> >
> > > > > 1/24/2009  09:49 PM           214,528 ASCOM.Utilities.pdb
> >
> > > > > 7/01/2010  01:02 PM            21,216 ASCOM.Utilities.tlb
> >
> > > > > 1/24/2009  09:49 PM           171,112 ASCOM.Utilities.xml
> >
> > > > > 1/17/2009  06:28 PM           397,566 ASCOMDriverTemplates.vsi
> >
> > > > > 4/15/2009  11:58 PM               489 driveraccess.config
> >
> > > > > 1/20/2009  08:25 AM            12,288 FusionLib.dll
> >
> > > > > 1/20/2009  08:25 AM            15,872 FusionLib.pdb
> >
> > > > > 1/20/2009  08:25 AM            15,360 GACInstall.exe
> >
> > > > > 8/01/2009  04:33 PM            37,376 NOVAS-C.dll
> >
> > > > > 8/01/2009  04:33 PM           207,872 NOVAS-C.pdb
> >
> > > > > 8/01/2009  04:33 PM            52,224 NOVAS-C64.dll
> >
> > > > > 8/01/2009  04:33 PM           199,680 NOVAS-C64.pdb
> >
> > > > > 4/15/2009  11:58 PM             3,072
> >
> > > > policy.1.0.ASCOM.DriverAccess.dll
> >
> > > > > 1/17/2009  09:10 AM             3,584
> > policy.5.5.ASCOM.Astrometry.dll
> >
> > > > > 1/17/2009  09:10 AM             3,584
> > policy.5.5.ASCOM.Utilities.dll
> >
> > > > > 1/17/2009  09:10 AM               741 PublisherPolicy.xml
> >
> > > > > 9/23/2009  10:13 PM               683 ReadMe55.txt
> >
> > > > >              36 File(s)      3,913,015 bytes
> >
> > > > >               2 Dir(s)  80,084,582,400 bytes free
> >
> > > > >
> >
> > > > > :\Program Files\Common Files\ASCOM\.net>
> >
> > > > >
> >
> > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@> wrote:
> >
> > > > > >
> >
> > > > > > This was a fresh computer nothing installed. 5.0b first then
> >
> > > > > > update
> >
> > > > to 5.5.1.
> >
> > > > > The COM interfaces were installed with the tlb file in the ASCOM
> >
> > > > folder. The
> >
> > > > > .net dll was missing in the .net folder.
> >
> > > > > >
> >
> > > > > > Robert
> >
> > > > > >
> >
> > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@> wrote:
> >
> > > > > > >
> >
> > > > > > > I find it hard to believe that the problem is what you say it
> > is.
> >
> > > > > > > The interfaces PIA is so fundamental to ASCOM that we would
> > have
> >
> > > > > > > caught that a long time ago. Can we please be clear about
> >
> > > > > > > version numbers - when you say "the installer" which version
> > are
> >
> > > > > > > you
> >
> > > > talking
> >
> > > > > about?
> >
> > > > > > >
> >
> > > > > > > To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not
> > both).
> >
> > > > > > > The 5.0a/b installer includes and installs the interfaces PIA
> > in
> >
> > > > the
> >
> > > > > > > GAC, I am 100% certain that works correctly because it has
> > been
> >
> > > > > > > tested to death on many different systems, by all the ASCOM
> >
> > > > > > > developers and beta testers and on many end user systems.
> >
> > > > > > >
> >
> > > > > > > Something about this incident doesn't make sense. I would like
> >
> > > > > > > to get to the bottom of it, but I don't think it is a bug in
> > the
> >
> > > > installer.
> >
> > > > > > >
> >
> > > > > > > Regards,
> >
> > > > > > > --Tim Long
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > -----Original Message-----
> >
> > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> >
> > > > > Talk@yahoogroups.com]
> >
> > > > > > > On Behalf Of robt2112
> >
> > > > > > > Sent: 01 July 2010 14:57
> >
> > > > > > > To: ASCOM-Talk@yahoogroups.com
> >
> > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> >
> > > > > > >
> >
> > > > > > > This was just a verification that it is a bug in the
> > installer.
> >
> > > > The
> >
> > > > > > > file should have been installed. I verified that the file was
> >
> > > > > > > missing and that putting the file in place solves the problem.
> >
> > > > This
> >
> > > > > > > should be fixed in the installation.
> >
> > > > > > >
> >
> > > > > > > Robert
> >
> > > > > > >
> >
> > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@> wrote:
> >
> > > > > > > >
> >
> > > > > > > > If you do that... you're on your own! We've got to be very
> >
> > > > careful
> >
> > > > > > > about
> >
> > > > > > > > letting users do stuff like that because it will create
> >
> > > > confusion
> >
> > > > > > > > and
> >
> > > > > > > a
> >
> > > > > > > > support nightmare.
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > ASCOM interfaces is (currently) a COM object that lives in
> > the
> >
> > > > > > > > GAC. It should be installed by the platform installer and
> >
> > > > > > > > referenced from the COM tab of the references dialog.
> >
> > > > > > > >
> >
> > > > > > > > --Tim
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > -----Original Message-----
> >
> > > > > > > > From: ASCOM-Talk@yahoogroups.com
> >
> > > > > > > > [mailto:ASCOM-Talk@yahoogroups.com]
> >
> > > > > > > On
> >
> > > > > > > > Behalf Of robt2112
> >
> > > > > > > > Sent: 01 July 2010 02:20
> >
> > > > > > > > To: ASCOM-Talk@yahoogroups.com
> >
> > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in
> > .NET
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > Well... If I copy the dll from my svn download to common
> >
> > > > > > > > files\ascom\.net then it shows up on my .NET references tab
> > in
> >
> > > > VS.
> >
> > > > > > > > So
> >
> > > > > > > I
> >
> > > > > > > > think the problem is the dll is not included in the install.
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > Robert
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@>
> >
> > > > > wrote:
> >
> > > > > > > >
> >
> > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > Yes in windows\assembly it shows ASCOM.Interfaces that
> >
> > > > > > > > > points
> >
> > > > to
> >
> > > > > > > > ASCOM.Interfaces.dll. The only thing that shows up in Visual
> >
> > > > > > > > Studio is
> >
> > > > > > > a
> >
> > > > > > > > reference in COM to the tlb located in Program Files\Common
> >
> > > > > > > > Files\ASCOM\Interfaces.
> >
> > > > > > > >
> >
> > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > I do have a copy of the dll in the Platform Dependancies
> >
> > > > folder
> >
> > > > > > > > > of
> >
> > > > > > > the
> >
> > > > > > > > ASCOM platform Drivers and Simulators that I downloaded from
> >
> > > > SVN.
> >
> > > > > > > > The dll doesn't seem to get installed with the platform
> > install.
> >
> > > > > > > >
> >
> > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > Robert
> >
> > > > > > > >
> >
> > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:
> >
> > > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > As far as I can tell, platform 5 installs
> >
> > > > ASCOM.Interface.dll
> >
> > > > > > > > > > in
> >
> > > > > > > > GAC, not in Common Files\ASCOM. Check Windows\Assembly
> >
> > > folder
> >
> > > > > > > > to see
> >
> > > > > > > if
> >
> > > > > > > > it's there.
> >
> > > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > Regards,
> >
> > > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > >     -Paul
> >
> > > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
> >
> > > <robt2112@>
> >
> > > > > wrote:
> >
> > > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > Slight correction. I installed Platform 5.0b then
> >
> > > > > > > > > > > updated
> >
> > > > to
> >
> > > > > > > > 5.5.1. Both show installed in programs and features.
> >
> > > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > Robert
> >
> > > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
> >
> > > > > > > > > > > <robt2112@>
> >
> > > > > wrote:
> >
> > > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > Well I think what is wrong is the installer for
> > 5.5.1.
> >
> > > > > > > > > > > > This is
> >
> > > > > > > a
> >
> > > > > > > > brand new install. I havent installed any previous versions
> >
> > > > which
> >
> > > > > > > > are not available on the website. I just installed the
> > latest
> >
> > > > > > > > version. The Interfaces dll was not installed.
> >
> > > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > I believe if you had installed a previous platform
> >
> > > > version
> >
> > > > > > > that
> >
> > > > > > > > dll would be there. Since I installed fresh it didn't get on
> >
> > > > > > > > my
> >
> > > > > > > machine.
> >
> > > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > Robert
> >
> > > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@>
> >
> > > > > wrote:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform
> > 5.5.
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > Paul is correct that it's a .NET assembly, but it
> > is
> >
> > > > > > > > > > > > > also a
> >
> > > > > > > > COM Primary
> >
> > > > > > > >
> >
> > > > > > > > > > > > > Interop Assembly (PIA) so (confusingly) it show up
> >
> > > > under
> >
> > > > > > > > > > > > > the
> >
> > > > > > > > COM tab as
> >
> > > > > > > >
> >
> > > > > > > > > > > > > shown here:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > So reference that, and also from the .NET tab,
> > bring
> >
> > > > in
> >
> > > > > > > > > > > > > the
> >
> > > > > > > >
> >
> > > > > > > > > > > > > ASCOM.DriverAccess namespace thus:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > Your project's references would then look
> > something
> >
> > > > like
> >
> > > > > > > this
> >
> > > > > > > > (I'm using
> >
> > > > > > > >
> >
> > > > > > > > > > > > > C# in VS2010, yours may appear differently):
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > Then in visual studio, you can use some code like
> >
> > > > > > > > > > > > > this to
> >
> > > > > > > > test:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > using System;
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > using ASCOM.DriverAccess;
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > namespace ConsoleApplication1
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > {
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >     class Program
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >     {
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >         static void Main(string[] args)
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >         {
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >             var userChoice =
> >
> > > > > > > > > > > > > Telescope.Choose(String.Empty);
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >             var scope = new Telescope(userChoice);
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >             scope.Connected = true;
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >             scope.Park();
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >             scope.Connected = false;
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >             scope.Dispose();
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >             scope = null;
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >         }
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >     }
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > }
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > This code does work, I just ran it. If you can't
> > get
> >
> > > > > > > > > > > > > this to
> >
> > > > > > > > work, then
> >
> > > > > > > >
> >
> > > > > > > > > > > > > something is badly wrong and needs sorting out.
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > --Tim
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > -----Original Message-----
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > Talk@yahoogroups.com
> > <mailto:Talk@yahoogroups.com> ] On Behalf Of robt2112
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > Sent: 30 June 2010 20:53
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > To: ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM
> >
> > > > driver
> >
> > > > > > > > > > > > > > in
> >
> > > > > > > > .NET
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > It should be, but its not on my .NET assembly
> > tab
> >
> > > > > > > > > > > > > > in
> >
> > > > > > > visual
> >
> > > > > > > > studio. I
> >
> > > > > > > >
> >
> > > > > > > > > > > > > only see it
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > on the COM tab. Looks like the install didnt not
> >
> > > > > > > > > > > > > > register
> >
> > > > > > > > something.
> >
> > > > > > > >
> >
> > > > > > > > > > > > > This is a
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > new Win7 machine with a brand new ASCOM install.
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > Robert
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com>
> >
> > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > , "paulkccd" <yh@ <mailto:yh@ <mailto:yh@> > >
> > wrote:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM.
> >
> > > > > > > > > > > > > > > You can
> >
> > > > > > > add
> >
> > > > > > > > a
> >
> > > > > > > >
> >
> > > > > > > > > > > > > reference
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > to it from the .NET tab in Visual Studio Add
> >
> > > > > > > > > > > > > > References
> >
> > > > > > > > dialog.
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > Regards,
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > >     -Paul
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"
> >
> > > > > > > > > > > > > <robt2112@>
> >
> > > > > > > > wrote:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > That is what I was trying. I cant get access
> >
> > > > > > > > > > > > > > > > to
> >
> > > > > > > > ITelescope. I
> >
> > > > > > > >
> >
> > > > > > > > > > > > > added a
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > reference to DriverAccess and it complained that
> >
> > > > > > > > > > > > > > the
> >
> > > > > > > > interfaces were
> >
> > > > > > > >
> >
> > > > > > > > > > > > > defined
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > in ASCOM.Interfaces. I added that reference from
> >
> > > > COM,
> >
> > > > > > > > > > > > > > but
> >
> > > > > > > > dont see a
> >
> > > > > > > >
> >
> > > > > > > > > > > > > .NET
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > version. When I try to use ASCOM.ITelescope it
> >
> > > > > > > > > > > > > > complains
> >
> > > > > > > it
> >
> > > > > > > > doesn't
> >
> > > > > > > >
> >
> > > > > > > > > > > > > exist.
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > It won't let you create an instance with
> > Type
> >
> > > > > > > Telescope.
> >
> > > > > > > > It says I
> >
> > > > > > > >
> >
> > > > > > > > > > > > > must use
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > ITelescope.
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > Robert
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> > , "paulkccd"
> >
> > > > > > > > > > > > > <yh@>
> >
> > > > > > > wrote:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > And this is how I'd do it in C#:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >      ITelescope g;
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >      g =
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > .Gemin\
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > iTelescope.Telescope"));
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >      g.Connected = true;
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > Regards,
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >       -Paul
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> > , "paulkccd"
> >
> > > > > > > > > > > > > <yh@>
> >
> > > > > > > wrote:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > Rob, what error do you get? Here's
> > sample
> >
> > > > > > > > > > > > > > > > > > VB.Net
> >
> > > > > > > > code I sent
> >
> > > > > > > >
> >
> > > > > > > > > > > > > to
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > a
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > Gemini
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > user:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > CreateObject("ASCOM.GeminiTelescope.Telescope"
> >
> > > > > > > > > > > > > > > > > > )
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > g.Connected = True
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > You just need to add a reference
> >
> > > > > > > > > > > > > > > > > > ASCOM.Interfaces
> >
> > > > > > > > assembly.
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > Does this not work for you?
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > Regards,
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > -Paul
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"
> >
> > > > > > > > > > > > > robt2112@
> >
> > > > > > > > wrote:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > > So this is basic question. How do I
> >
> > > > > > > > > > > > > > > > > > > access and
> >
> > > > > > > use
> >
> > > > > > > > an ASCOM
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > > driver
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > in
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > .NET code. I keep running into cant
> > create
> >
> > > > > > > instances
> >
> > > > > > > > that
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > represent
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > COM
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > components.
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > > Robert
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > ------------------------------------
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > For more information see
> >
> > > > > > > > > > > > > > http://ASCOM-Standards.org/
> > <http://ASCOM-Standards.org/>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <http://ASCOM-Standards.org/
> > <http://ASCOM-Standards.org/> > .
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > To unsubscribe from this group, send an email
> > FROM
> >
> > > > THE
> >
> > > > > > > > ACCOUNT YOU
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > USED TO SUBSCRIBE(!) to:
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > > Yahoo! Groups Links
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > <http://groups.yahoo.com/group/ASCOM-Talk/>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/
> > <http://groups.yahoo.com/group/ASCOM-Talk/> >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >     Individual Email | Traditional
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> > http://groups.yahoo.com/group/ASCOM-Talk/join
> > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join
> > <http://groups.yahoo.com/group/ASCOM-Talk/join> >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >     (Yahoo! ID required)
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com
> > <mailto:ASCOM-Talk-digest@yahoogroups.com> >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com
> > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com> >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > >     http://docs.yahoo.com/info/terms/
> > <http://docs.yahoo.com/info/terms/>
> >
> > > > > > > >
> >
> > > > > > > > > > > > > <http://docs.yahoo.com/info/terms/
> > <http://docs.yahoo.com/info/terms/> >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > > > --
> >
> > > > > > > >
> >
> > > > > > > > > > > > > ExchangeDefender Message Security: Click below to
> >
> > > > verify
> >
> > > > > > > > authenticity
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > >
> >
> > > http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from
> > <http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from>
> >
> > > > > =
> >
> > > > > > > > tim@
> >
> > > > > > > >
> >
> > > > > > > > > > > > > Complete email hygeine and business continuity
> >
> > > > solution
> >
> > > > > > > > available from http://www.tigranetworks.co.uk
> > <http://www.tigranetworks.co.uk>
> >
> > > > > > > >
> >
> > > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > ------------------------------------
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > For more information see http://ASCOM-Standards.org/
> > <http://ASCOM-Standards.org/> .
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > To unsubscribe from this group, send an email FROM THE
> > ACCOUNT
> >
> > > > > YOU
> >
> > > > > > > USED
> >
> > > > > > > > TO SUBSCRIBE(!) to:
> >
> > > > > > > >
> >
> > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > Yahoo! Groups Links
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > <http://groups.yahoo.com/group/ASCOM-Talk/>
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >     Individual Email | Traditional
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> >
> > > > > > > >
> >
> > > > > > > >     (Yahoo! ID required)
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >     http://docs.yahoo.com/info/terms/
> > <http://docs.yahoo.com/info/terms/>
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > >
> >
> > > > > > > > --
> >
> > > > > > > > ExchangeDefender Message Security: Click below to verify
> >
> > > > > > > > authenticity
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > >
> >
> > > http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from
> > <http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from> =
> >
> > > > > ti
> >
> > > > > > > m@
> >
> > > > > > > .
> >
> > > > > > > > Complete email hygeine and business continuity solution
> >
> > > > available
> >
> > > > > > > > from
> >
> > > > > > > http://www.tigranetworks.co.uk
> > <http://www.tigranetworks.co.uk>
> >
> > > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > ------------------------------------
> >
> > > > > > >
> >
> > > > > > > For more information see http://ASCOM-Standards.org/
> > <http://ASCOM-Standards.org/> .
> >
> > > > > > >
> >
> > > > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT
> >
> > > > > > > YOU USED TO SUBSCRIBE(!) to:
> >
> > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > > > > > >
> >
> > > > > > > Yahoo! Groups Links
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > >
> >
> > > > > > > --
> >
> > > > > > > ExchangeDefender Message Security: Click below to verify
> >
> > > > > > > authenticity
> >
> > > > > > >
> >
> > > > >
> >
> > > http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from
> > <http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from> =
> >
> > > > > ti
> >
> > > > > > > m@ Complete email hygeine and business continuity solution
> >
> > > > available
> >
> > > > > > > from http://www.tigranetworks.co.uk
> > <http://www.tigranetworks.co.uk>
> >
> > > > > > >
> >
> > > > > >
> >
> > > > >
> >
> > > > >
> >
> > > > >
> >
> > > > >
> >
> > > > > ------------------------------------
> >
> > > > >
> >
> > > > > For more information see http://ASCOM-Standards.org/
> > <http://ASCOM-Standards.org/> .
> >
> > > > >
> >
> > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> >
> > > > > USED TO SUBSCRIBE(!) to:
> >
> > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > > > >
> >
> > > > > Yahoo! Groups Links
> >
> > > > >
> >
> > > > >
> >
> > > > >
> >
> > > >
> >
> > > > --
> >
> > > > ExchangeDefender Message Security: Click below to verify
> > authenticity
> >
> > > >
> >
> > > http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=t
> > <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=tim@>
> >
> >
> > > im@
> > <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=tim@>
> > ...
> >
> > > > Complete email hygeine and business continuity solution available
> > from
> >
> > > > http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk>
> >
> > > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > > ------------------------------------
> >
> > >
> >
> > > For more information see http://ASCOM-Standards.org/
> > <http://ASCOM-Standards.org/> .
> >
> > >
> >
> > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> >
> > > USED TO SUBSCRIBE(!) to:
> >
> > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > >
> >
> > > Yahoo! Groups Links
> >
> > >
> >
> > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > <http://groups.yahoo.com/group/ASCOM-Talk/>
> >
> > >
> >
> > >     Individual Email | Traditional
> >
> > >
> >
> > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> >
> > >     (Yahoo! ID required)
> >
> > >
> >
> > >     ASCOM-Talk-digest@yahoogroups.com
> > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> >
> > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> >
> > >
> >
> > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> >
> > >
> >
> > >     http://docs.yahoo.com/info/terms/
> > <http://docs.yahoo.com/info/terms/>
> >
> >
> >
> >
> > --
> > ExchangeDefender Message Security: Click below to verify authenticity
> > http://www.exchangedefender.com/verify.asp?id=o61JtsK5023776&from=tim@
> > Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
> >
>

#21188 From: "Tim Long" <Tim@...>
Date: Thu Jul 1, 2010 8:59 pm
Subject: RE: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
t_p_long
Send Email Send Email
 

Rob, I think you may have some wrong version of a DLL somewhere (THIS is why I strongly discourage manual installation of DLLs). I can build a solution just fine without ever referencing the interfaces DLL, which doesn’t exist on my system. Even when I reference DriverAccess.

 

Rob, I can see why you might think that – I just had the same error message myself. But what you actually need to reference is the “ASCOM Master Interfaces for COM and .NET” from the COM tab. It works. There’s no DLL needed.

 

I’m not sure that we have documented this anywhere, despite Peter’s herculean efforts updating the developer documentation in Platform 5.5.1, the driver templates of course have this already wired up, so it’s never a problem.

 

So the best I can offer is: “Reference the Interfaces component in the COM tab”. Please don’t manually copy DLLs anywhere, that’s just masking the real issue.

 

--Tim

 

> -----Original Message-----

> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> Talk@yahoogroups.com] On Behalf Of robt2112

> Sent: 01 July 2010 21:32

> To: ASCOM-Talk@yahoogroups.com

> Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

>

> Well unfortunately if you try to develop with platform 5.5 it doesnt work

> unless you have the dll. Visual Studio complains that you must add a

> reference to ASCOM.Interfaces when you add DriverAcess. The message the

> interface are defined in ASCOM.Interfaces and must be referenced in the

> project.

>

> The only way to actually develop in .NET with platform 5.5 is to include the

> ghost ASCOM.Interfaces.dll. Now also if you look in the GAC

> ASCOM.Interfaces.dll is registered, but there is no actual file. Look at

> windows/assembly you will see ASCOM.Interfaces and the Original Filename

> property points to ASCOM.Interfaces.dll. This file exists nowhere on the

> system.

>

> So in platform 5.5 dependencies in SVN the mystery dll is there and is part of

> the dependent assemblies. So without it you can't develop a driver. So if you

> want to see further put visual studio express in your clean vm and try to write

> a .NET driver that references one of the interfaces.

>

>

> Robert

>

>

>

>

> --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:

> >

> > OK, let me try this one more time. I have double checked all of this

> > and I am 100% certain this is accurate. Let me be clear that I am

> > talking about the RELEASED platform 5.5 and not anything that came

> > from subversion.

> >

> >

> >

> >

> > There is no assembly called ASCOM.Interfaces.dll1 in Platform 5.5, it

> > should not be in your filesystem anywhere2,3.

> >

> >

> >

> >

> >

> >

> > The ASCOM Interfaces are COM objects and are obtained from the COM

> tab

> > in the references dialog. You'll note that what you are actually

> > referencing is the type library, thus:

> >

> >

> >

> > There is no bug, there should be no DLL file.

> >

> >

> >

> > OK, now for the footnotes J

> >

> >

> >

> > ________________________________

> >

> > 1 In fact, technically the interfaces are defined in a special type of

> > .NET assembly - a Primary Interop Assembly - which is created by

> > importing the type library (.tlb) file, is installed in the GAC (not

> > the

> > filesystem) and is given special treatment by visual studio. For all

> > intents and purposes, it appears to be a COM object in Visual Studio

> > and that's how you should reference it.

> >

> > 2 In fact, items in the GAC are also in the filesystem, but their

> > location is obfuscated and direct access is verboten. If you examine

> > the folder c:\windows\assembly (in Windows Explorer) you'll see that

> > the assembly is indeed listed:

> >

> > However, all it contains is a thin veneer of metadata that makes

> > IntelliSense work properly. The actual interfaces are defined in the

> > type library, which in turn is generated from an IDL file.

> >

> > 3 If you've checked out the code base from Subversion, then you'll

> > have the DLL file in your filesystem - but I'm ignoring that situation

> > because it's fairly uncommon for end users at the moment.

> >

> >

> >

> > --Tim

> >

> >

> >

> > > -----Original Message-----

> >

> > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> >

> > > Talk@yahoogroups.com] On Behalf Of robt2112

> >

> > > Sent: 01 July 2010 20:18

> >

> > > To: ASCOM-Talk@yahoogroups.com

> >

> > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

> >

> > >

> >

> > > The related issue then is if it is not there then you cant reference

> > the

> >

> > > interfaces in Visual Studio. It doesn't exist anywhere searching the

> > entire c

> >

> > > drive of the VM. The file is required for development in Visual

> > Studio.

> >

> > >

> >

> > > Robert

> >

> > >

> >

> > > --- In ASCOM-Talk@yahoogroups.com

> > > <mailto:ASCOM-Talk@yahoogroups.com>

> > , "Tim Long" <Tim@ <mailto:Tim@> > wrote:

> >

> > > >

> >

> > > > I wouldn't necessarily expect it to be there. Let me try the same

> >

> > > > thing myself and I'll get back to you.

> >

> > > > --Tim

> >

> > > >

> >

> > > > > -----Original Message-----

> >

> > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> >

> > > > > Talk@yahoogroups.com] On Behalf Of robt2112

> >

> > > > > Sent: 01 July 2010 18:06

> >

> > > > > To: ASCOM-Talk@yahoogroups.com

> >

> > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

> >

> > > > >

> >

> > > > > Just for completeness of testing this issue I started a VM with

> > win

> >

> > > > xp. Never

> >

> > > > > had anything ascom related. Installed 5.0b. The C:\Program

> >

> > > > Files\Common

> >

> > > > > Files\ASCOM\.net is created with just the .vsi template in it.

> >

> > > > >

> >

> > > > > Install 5.5.1 update. The following is the contents of the .net

> >

> > > > > folder

> >

> > > > after

> >

> > > > > install. ASCOM.Interfaces.dll is missing.

> >

> > > > >

> >

> > > > > Robert

> >

> > > > >

> >

> > > > >

> >

> > > > >

> >

> > > > > Directory of C:\Program Files\Common Files\ASCOM\.net

> >

> > > > >

> >

> > > > > 7/01/2010  01:02 PM    <DIR>          .

> >

> > > > > 7/01/2010  01:02 PM    <DIR>          ..

> >

> > > > > 1/21/2009  11:30 PM           523,264 ASCOM Diagnostics.exe

> >

> > > > > 1/21/2009  11:30 PM           212,480 ASCOM Diagnostics.pdb

> >

> > > > > 1/24/2009  09:50 PM           540,160 ASCOM.Astrometry.dll

> >

> > > > > 1/24/2009  09:50 PM           249,344 ASCOM.Astrometry.pdb

> >

> > > > > 7/01/2010  01:02 PM            28,824 ASCOM.Astrometry.tlb

> >

> > > > > 1/24/2009  09:50 PM           247,602 ASCOM.Astrometry.xml

> >

> > > > > 1/24/2009  09:49 PM             5,632 ASCOM.Attributes.dll

> >

> > > > > 1/24/2009  09:49 PM            13,824 ASCOM.Attributes.pdb

> >

> > > > > 7/10/2008  02:21 PM            53,248 ASCOM.DriverAccess.dll

> >

> > > > > 7/10/2008  02:21 PM           105,984 ASCOM.DriverAccess.pdb

> >

> > > > > 7/10/2008  02:21 PM           105,045 ASCOM.DriverAccess.XML

> >

> > > > > 1/20/2009  08:24 AM             9,216 ASCOM.Exceptions.dll

> >

> > > > > 1/20/2009  08:24 AM            21,933 ASCOM.Exceptions.XML

> >

> > > > > 8/01/2009  04:33 PM           125,783 ASCOM.ico

> >

> > > > > 1/20/2009  08:24 AM            14,336 ASCOM.IConform.dll

> >

> > > > > 1/20/2009  08:24 AM            34,304 ASCOM.IConform.pdb

> >

> > > > > 7/01/2010  01:02 PM             3,808 ASCOM.IConform.tlb

> >

> > > > > 1/20/2009  08:24 AM             9,589 ASCOM.IConform.xml

> >

> > > > > 1/24/2009  09:49 PM           251,392 ASCOM.Utilities.dll

> >

> > > > > 1/24/2009  09:49 PM           214,528 ASCOM.Utilities.pdb

> >

> > > > > 7/01/2010  01:02 PM            21,216 ASCOM.Utilities.tlb

> >

> > > > > 1/24/2009  09:49 PM           171,112 ASCOM.Utilities.xml

> >

> > > > > 1/17/2009  06:28 PM           397,566 ASCOMDriverTemplates.vsi

> >

> > > > > 4/15/2009  11:58 PM               489 driveraccess.config

> >

> > > > > 1/20/2009  08:25 AM            12,288 FusionLib.dll

> >

> > > > > 1/20/2009  08:25 AM            15,872 FusionLib.pdb

> >

> > > > > 1/20/2009  08:25 AM            15,360 GACInstall.exe

> >

> > > > > 8/01/2009  04:33 PM            37,376 NOVAS-C.dll

> >

> > > > > 8/01/2009  04:33 PM           207,872 NOVAS-C.pdb

> >

> > > > > 8/01/2009  04:33 PM            52,224 NOVAS-C64.dll

> >

> > > > > 8/01/2009  04:33 PM           199,680 NOVAS-C64.pdb

> >

> > > > > 4/15/2009  11:58 PM             3,072

> >

> > > > policy.1.0.ASCOM.DriverAccess.dll

> >

> > > > > 1/17/2009  09:10 AM             3,584

> > policy.5.5.ASCOM.Astrometry.dll

> >

> > > > > 1/17/2009  09:10 AM             3,584

> > policy.5.5.ASCOM.Utilities.dll

> >

> > > > > 1/17/2009  09:10 AM               741 PublisherPolicy.xml

> >

> > > > > 9/23/2009  10:13 PM               683 ReadMe55.txt

> >

> > > > >              36 File(s)      3,913,015 bytes

> >

> > > > >               2 Dir(s)  80,084,582,400 bytes free

> >

> > > > >

> >

> > > > > :\Program Files\Common Files\ASCOM\.net>

> >

> > > > >

> >

> > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@>

> wrote:

> >

> > > > > >

> >

> > > > > > This was a fresh computer nothing installed. 5.0b first then

> >

> > > > > > update

> >

> > > > to 5.5.1.

> >

> > > > > The COM interfaces were installed with the tlb file in the ASCOM

> >

> > > > folder. The

> >

> > > > > .net dll was missing in the .net folder.

> >

> > > > > >

> >

> > > > > > Robert

> >

> > > > > >

> >

> > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@> wrote:

> >

> > > > > > >

> >

> > > > > > > I find it hard to believe that the problem is what you say

> > > > > > > it

> > is.

> >

> > > > > > > The interfaces PIA is so fundamental to ASCOM that we would

> > have

> >

> > > > > > > caught that a long time ago. Can we please be clear about

> >

> > > > > > > version numbers - when you say "the installer" which version

> > are

> >

> > > > > > > you

> >

> > > > talking

> >

> > > > > about?

> >

> > > > > > >

> >

> > > > > > > To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not

> > both).

> >

> > > > > > > The 5.0a/b installer includes and installs the interfaces

> > > > > > > PIA

> > in

> >

> > > > the

> >

> > > > > > > GAC, I am 100% certain that works correctly because it has

> > been

> >

> > > > > > > tested to death on many different systems, by all the ASCOM

> >

> > > > > > > developers and beta testers and on many end user systems.

> >

> > > > > > >

> >

> > > > > > > Something about this incident doesn't make sense. I would

> > > > > > > like

> >

> > > > > > > to get to the bottom of it, but I don't think it is a bug in

> > the

> >

> > > > installer.

> >

> > > > > > >

> >

> > > > > > > Regards,

> >

> > > > > > > --Tim Long

> >

> > > > > > >

> >

> > > > > > >

> >

> > > > > > > -----Original Message-----

> >

> > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> >

> > > > > Talk@yahoogroups.com]

> >

> > > > > > > On Behalf Of robt2112

> >

> > > > > > > Sent: 01 July 2010 14:57

> >

> > > > > > > To: ASCOM-Talk@yahoogroups.com

> >

> > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in

> > > > > > > .NET

> >

> > > > > > >

> >

> > > > > > > This was just a verification that it is a bug in the

> > installer.

> >

> > > > The

> >

> > > > > > > file should have been installed. I verified that the file

> > > > > > > was

> >

> > > > > > > missing and that putting the file in place solves the problem.

> >

> > > > This

> >

> > > > > > > should be fixed in the installation.

> >

> > > > > > >

> >

> > > > > > > Robert

> >

> > > > > > >

> >

> > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@> wrote:

> >

> > > > > > > >

> >

> > > > > > > > If you do that... you're on your own! We've got to be very

> >

> > > > careful

> >

> > > > > > > about

> >

> > > > > > > > letting users do stuff like that because it will create

> >

> > > > confusion

> >

> > > > > > > > and

> >

> > > > > > > a

> >

> > > > > > > > support nightmare.

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > ASCOM interfaces is (currently) a COM object that lives in

> > the

> >

> > > > > > > > GAC. It should be installed by the platform installer and

> >

> > > > > > > > referenced from the COM tab of the references dialog.

> >

> > > > > > > >

> >

> > > > > > > > --Tim

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > -----Original Message-----

> >

> > > > > > > > From: ASCOM-Talk@yahoogroups.com

> >

> > > > > > > > [mailto:ASCOM-Talk@yahoogroups.com]

> >

> > > > > > > On

> >

> > > > > > > > Behalf Of robt2112

> >

> > > > > > > > Sent: 01 July 2010 02:20

> >

> > > > > > > > To: ASCOM-Talk@yahoogroups.com

> >

> > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in

> > .NET

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > Well... If I copy the dll from my svn download to common

> >

> > > > > > > > files\ascom\.net then it shows up on my .NET references

> > > > > > > > tab

> > in

> >

> > > > VS.

> >

> > > > > > > > So

> >

> > > > > > > I

> >

> > > > > > > > think the problem is the dll is not included in the install.

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > Robert

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@>

> >

> > > > > wrote:

> >

> > > > > > > >

> >

> > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > Yes in windows\assembly it shows ASCOM.Interfaces that

> >

> > > > > > > > > points

> >

> > > > to

> >

> > > > > > > > ASCOM.Interfaces.dll. The only thing that shows up in

> > > > > > > > Visual

> >

> > > > > > > > Studio is

> >

> > > > > > > a

> >

> > > > > > > > reference in COM to the tlb located in Program

> > > > > > > > Files\Common

> >

> > > > > > > > Files\ASCOM\Interfaces.

> >

> > > > > > > >

> >

> > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > I do have a copy of the dll in the Platform Dependancies

> >

> > > > folder

> >

> > > > > > > > > of

> >

> > > > > > > the

> >

> > > > > > > > ASCOM platform Drivers and Simulators that I downloaded

> > > > > > > > from

> >

> > > > SVN.

> >

> > > > > > > > The dll doesn't seem to get installed with the platform

> > install.

> >

> > > > > > > >

> >

> > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > Robert

> >

> > > > > > > >

> >

> > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:

> >

> > > > > > > >

> >

> > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > As far as I can tell, platform 5 installs

> >

> > > > ASCOM.Interface.dll

> >

> > > > > > > > > > in

> >

> > > > > > > > GAC, not in Common Files\ASCOM. Check Windows\Assembly

> >

> > > folder

> >

> > > > > > > > to see

> >

> > > > > > > if

> >

> > > > > > > > it's there.

> >

> > > > > > > >

> >

> > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > Regards,

> >

> > > > > > > >

> >

> > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > >     -Paul

> >

> > > > > > > >

> >

> > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"

> >

> > > <robt2112@>

> >

> > > > > wrote:

> >

> > > > > > > >

> >

> > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > Slight correction. I installed Platform 5.0b then

> >

> > > > > > > > > > > updated

> >

> > > > to

> >

> > > > > > > > 5.5.1. Both show installed in programs and features.

> >

> > > > > > > >

> >

> > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > Robert

> >

> > > > > > > >

> >

> > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"

> >

> > > > > > > > > > > <robt2112@>

> >

> > > > > wrote:

> >

> > > > > > > >

> >

> > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > Well I think what is wrong is the installer for

> > 5.5.1.

> >

> > > > > > > > > > > > This is

> >

> > > > > > > a

> >

> > > > > > > > brand new install. I havent installed any previous

> > > > > > > > versions

> >

> > > > which

> >

> > > > > > > > are not available on the website. I just installed the

> > latest

> >

> > > > > > > > version. The Interfaces dll was not installed.

> >

> > > > > > > >

> >

> > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > I believe if you had installed a previous platform

> >

> > > > version

> >

> > > > > > > that

> >

> > > > > > > > dll would be there. Since I installed fresh it didn't get

> > > > > > > > on

> >

> > > > > > > > my

> >

> > > > > > > machine.

> >

> > > > > > > >

> >

> > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > Robert

> >

> > > > > > > >

> >

> > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@>

> >

> > > > > wrote:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > I'm assuming you have .NET 3.5 and ASCOM

> > > > > > > > > > > > > Platform

> > 5.5.

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > Paul is correct that it's a .NET assembly, but

> > > > > > > > > > > > > it

> > is

> >

> > > > > > > > > > > > > also a

> >

> > > > > > > > COM Primary

> >

> > > > > > > >

> >

> > > > > > > > > > > > > Interop Assembly (PIA) so (confusingly) it show

> > > > > > > > > > > > > up

> >

> > > > under

> >

> > > > > > > > > > > > > the

> >

> > > > > > > > COM tab as

> >

> > > > > > > >

> >

> > > > > > > > > > > > > shown here:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > So reference that, and also from the .NET tab,

> > bring

> >

> > > > in

> >

> > > > > > > > > > > > > the

> >

> > > > > > > >

> >

> > > > > > > > > > > > > ASCOM.DriverAccess namespace thus:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > Your project's references would then look

> > something

> >

> > > > like

> >

> > > > > > > this

> >

> > > > > > > > (I'm using

> >

> > > > > > > >

> >

> > > > > > > > > > > > > C# in VS2010, yours may appear differently):

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > Then in visual studio, you can use some code

> > > > > > > > > > > > > like

> >

> > > > > > > > > > > > > this to

> >

> > > > > > > > test:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > using System;

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > using ASCOM.DriverAccess;

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > namespace ConsoleApplication1

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > {

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >     class Program

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >     {

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >         static void Main(string[] args)

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >         {

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >             var userChoice =

> >

> > > > > > > > > > > > > Telescope.Choose(String.Empty);

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >             var scope = new

> > > > > > > > > > > > > Telescope(userChoice);

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >             scope.Connected = true;

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >             scope.Park();

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >             scope.Connected = false;

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >             scope.Dispose();

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >             scope = null;

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >         }

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >     }

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > }

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > This code does work, I just ran it. If you can't

> > get

> >

> > > > > > > > > > > > > this to

> >

> > > > > > > > work, then

> >

> > > > > > > >

> >

> > > > > > > > > > > > > something is badly wrong and needs sorting out.

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > --Tim

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > -----Original Message-----

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > From: ASCOM-Talk@yahoogroups.com

> > > > > > > > > > > > > > [mailto:ASCOM-

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > Talk@yahoogroups.com

> > <mailto:Talk@yahoogroups.com> ] On Behalf Of robt2112

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > Sent: 30 June 2010 20:53

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > To: ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > Subject: [ASCOM] Re: Creating Instance to

> > > > > > > > > > > > > > ASCOM

> >

> > > > driver

> >

> > > > > > > > > > > > > > in

> >

> > > > > > > > .NET

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > It should be, but its not on my .NET assembly

> > tab

> >

> > > > > > > > > > > > > > in

> >

> > > > > > > visual

> >

> > > > > > > > studio. I

> >

> > > > > > > >

> >

> > > > > > > > > > > > > only see it

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > on the COM tab. Looks like the install didnt

> > > > > > > > > > > > > > not

> >

> > > > > > > > > > > > > > register

> >

> > > > > > > > something.

> >

> > > > > > > >

> >

> > > > > > > > > > > > > This is a

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > new Win7 machine with a brand new ASCOM install.

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > Robert

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com>

> >

> > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > , "paulkccd" <yh@ <mailto:yh@ <mailto:yh@> > >

> > wrote:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM.

> >

> > > > > > > > > > > > > > > You can

> >

> > > > > > > add

> >

> > > > > > > > a

> >

> > > > > > > >

> >

> > > > > > > > > > > > > reference

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > to it from the .NET tab in Visual Studio Add

> >

> > > > > > > > > > > > > > References

> >

> > > > > > > > dialog.

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > Regards,

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > >     -Paul

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"

> >

> > > > > > > > > > > > > <robt2112@>

> >

> > > > > > > > wrote:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > That is what I was trying. I cant get

> > > > > > > > > > > > > > > > access

> >

> > > > > > > > > > > > > > > > to

> >

> > > > > > > > ITelescope. I

> >

> > > > > > > >

> >

> > > > > > > > > > > > > added a

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > reference to DriverAccess and it complained

> > > > > > > > > > > > > > that

> >

> > > > > > > > > > > > > > the

> >

> > > > > > > > interfaces were

> >

> > > > > > > >

> >

> > > > > > > > > > > > > defined

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > in ASCOM.Interfaces. I added that reference

> > > > > > > > > > > > > > from

> >

> > > > COM,

> >

> > > > > > > > > > > > > > but

> >

> > > > > > > > dont see a

> >

> > > > > > > >

> >

> > > > > > > > > > > > > .NET

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > version. When I try to use ASCOM.ITelescope it

> >

> > > > > > > > > > > > > > complains

> >

> > > > > > > it

> >

> > > > > > > > doesn't

> >

> > > > > > > >

> >

> > > > > > > > > > > > > exist.

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > It won't let you create an instance with

> > Type

> >

> > > > > > > Telescope.

> >

> > > > > > > > It says I

> >

> > > > > > > >

> >

> > > > > > > > > > > > > must use

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > ITelescope.

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > Robert

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> > , "paulkccd"

> >

> > > > > > > > > > > > > <yh@>

> >

> > > > > > > wrote:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > And this is how I'd do it in C#:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >      ITelescope g;

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >      g =

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASC

> > > > > OM

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > .Gemin\

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > iTelescope.Telescope"));

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >      g.Connected = true;

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > Regards,

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >       -Paul

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> > , "paulkccd"

> >

> > > > > > > > > > > > > <yh@>

> >

> > > > > > > wrote:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > Rob, what error do you get? Here's

> > sample

> >

> > > > > > > > > > > > > > > > > > VB.Net

> >

> > > > > > > > code I sent

> >

> > > > > > > >

> >

> > > > > > > > > > > > > to

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > a

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > Gemini

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > user:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g

> > > > > > > > > > > > > > > > > > =

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > CreateObject("ASCOM.GeminiTelescope.Telescope"

> >

> > > > > > > > > > > > > > > > > > )

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > g.Connected = True

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > You just need to add a reference

> >

> > > > > > > > > > > > > > > > > > ASCOM.Interfaces

> >

> > > > > > > > assembly.

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > Does this not work for you?

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > Regards,

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > -Paul

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com

> > <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"

> >

> > > > > > > > > > > > > robt2112@

> >

> > > > > > > > wrote:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > > So this is basic question. How do I

> >

> > > > > > > > > > > > > > > > > > > access and

> >

> > > > > > > use

> >

> > > > > > > > an ASCOM

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > > driver

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > in

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > .NET code. I keep running into cant

> > create

> >

> > > > > > > instances

> >

> > > > > > > > that

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > represent

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > COM

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > components.

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > > Robert

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > ------------------------------------

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > For more information see

> >

> > > > > > > > > > > > > > http://ASCOM-Standards.org/

> > <http://ASCOM-Standards.org/>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <http://ASCOM-Standards.org/

> > <http://ASCOM-Standards.org/> > .

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > To unsubscribe from this group, send an email

> > FROM

> >

> > > > THE

> >

> > > > > > > > ACCOUNT YOU

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > USED TO SUBSCRIBE(!) to:

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > > Yahoo! Groups Links

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/

> > <http://groups.yahoo.com/group/ASCOM-Talk/>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/

> > <http://groups.yahoo.com/group/ASCOM-Talk/> >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >     Individual Email | Traditional

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> > http://groups.yahoo.com/group/ASCOM-Talk/join

> > <http://groups.yahoo.com/group/ASCOM-Talk/join>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join

> > <http://groups.yahoo.com/group/ASCOM-Talk/join> >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >     (Yahoo! ID required)

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com

> > <mailto:ASCOM-Talk-digest@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com

> > <mailto:ASCOM-Talk-digest@yahoogroups.com> >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com

> > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com

> > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com> >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > >     http://docs.yahoo.com/info/terms/

> > <http://docs.yahoo.com/info/terms/>

> >

> > > > > > > >

> >

> > > > > > > > > > > > > <http://docs.yahoo.com/info/terms/

> > <http://docs.yahoo.com/info/terms/> >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > > > --

> >

> > > > > > > >

> >

> > > > > > > > > > > > > ExchangeDefender Message Security: Click below

> > > > > > > > > > > > > to

> >

> > > > verify

> >

> > > > > > > > authenticity

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > >

> >

> > >

> http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from

> >

> <http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&fro

> m>

> >

> > > > > =

> >

> > > > > > > > tim@

> >

> > > > > > > >

> >

> > > > > > > > > > > > > Complete email hygeine and business continuity

> >

> > > > solution

> >

> > > > > > > > available from http://www.tigranetworks.co.uk

> > <http://www.tigranetworks.co.uk>

> >

> > > > > > > >

> >

> > > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > ------------------------------------

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > For more information see http://ASCOM-Standards.org/

> > <http://ASCOM-Standards.org/> .

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > To unsubscribe from this group, send an email FROM THE

> > ACCOUNT

> >

> > > > > YOU

> >

> > > > > > > USED

> >

> > > > > > > > TO SUBSCRIBE(!) to:

> >

> > > > > > > >

> >

> > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > Yahoo! Groups Links

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/

> > <http://groups.yahoo.com/group/ASCOM-Talk/>

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >     Individual Email | Traditional

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join

> > <http://groups.yahoo.com/group/ASCOM-Talk/join>

> >

> > > > > > > >

> >

> > > > > > > >     (Yahoo! ID required)

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >     ASCOM-Talk-digest@yahoogroups.com

> > <mailto:ASCOM-Talk-digest@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com

> > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >     http://docs.yahoo.com/info/terms/

> > <http://docs.yahoo.com/info/terms/>

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > >

> >

> > > > > > > > --

> >

> > > > > > > > ExchangeDefender Message Security: Click below to verify

> >

> > > > > > > > authenticity

> >

> > > > > > > >

> >

> > > > > > >

> >

> > > > >

> >

> > >

> http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from

> >

> <http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from

> > =

> >

> > > > > ti

> >

> > > > > > > m@

> >

> > > > > > > .

> >

> > > > > > > > Complete email hygeine and business continuity solution

> >

> > > > available

> >

> > > > > > > > from

> >

> > > > > > > http://www.tigranetworks.co.uk

> > <http://www.tigranetworks.co.uk>

> >

> > > > > > > >

> >

> > > > > > >

> >

> > > > > > >

> >

> > > > > > >

> >

> > > > > > >

> >

> > > > > > > ------------------------------------

> >

> > > > > > >

> >

> > > > > > > For more information see http://ASCOM-Standards.org/

> > <http://ASCOM-Standards.org/> .

> >

> > > > > > >

> >

> > > > > > > To unsubscribe from this group, send an email FROM THE

> > > > > > > ACCOUNT

> >

> > > > > > > YOU USED TO SUBSCRIBE(!) to:

> >

> > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> >

> > > > > > >

> >

> > > > > > > Yahoo! Groups Links

> >

> > > > > > >

> >

> > > > > > >

> >

> > > > > > >

> >

> > > > > > >

> >

> > > > > > > --

> >

> > > > > > > ExchangeDefender Message Security: Click below to verify

> >

> > > > > > > authenticity

> >

> > > > > > >

> >

> > > > >

> >

> > >

> http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from

> >

> <http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from

> > =

> >

> > > > > ti

> >

> > > > > > > m@ Complete email hygeine and business continuity solution

> >

> > > > available

> >

> > > > > > > from http://www.tigranetworks.co.uk

> > <http://www.tigranetworks.co.uk>

> >

> > > > > > >

> >

> > > > > >

> >

> > > > >

> >

> > > > >

> >

> > > > >

> >

> > > > >

> >

> > > > > ------------------------------------

> >

> > > > >

> >

> > > > > For more information see http://ASCOM-Standards.org/

> > <http://ASCOM-Standards.org/> .

> >

> > > > >

> >

> > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT

> > > > > YOU

> >

> > > > > USED TO SUBSCRIBE(!) to:

> >

> > > > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> >

> > > > >

> >

> > > > > Yahoo! Groups Links

> >

> > > > >

> >

> > > > >

> >

> > > > >

> >

> > > >

> >

> > > > --

> >

> > > > ExchangeDefender Message Security: Click below to verify

> > authenticity

> >

> > > >

> >

> > >

> http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=t

> >

> <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from

> =tim

> > @>

> >

> >

> > > im@

> >

> <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from

> =tim

> > @>

> > ...

> >

> > > > Complete email hygeine and business continuity solution available

> > from

> >

> > > > http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk>

> >

> > > >

> >

> > >

> >

> > >

> >

> > >

> >

> > >

> >

> > > ------------------------------------

> >

> > >

> >

> > > For more information see http://ASCOM-Standards.org/

> > <http://ASCOM-Standards.org/> .

> >

> > >

> >

> > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU

> >

> > > USED TO SUBSCRIBE(!) to:

> >

> > > ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> >

> > >

> >

> > > Yahoo! Groups Links

> >

> > >

> >

> > >     http://groups.yahoo.com/group/ASCOM-Talk/

> > <http://groups.yahoo.com/group/ASCOM-Talk/>

> >

> > >

> >

> > >     Individual Email | Traditional

> >

> > >

> >

> > >     http://groups.yahoo.com/group/ASCOM-Talk/join

> > <http://groups.yahoo.com/group/ASCOM-Talk/join>

> >

> > >     (Yahoo! ID required)

> >

> > >

> >

> > >     ASCOM-Talk-digest@yahoogroups.com

> > <mailto:ASCOM-Talk-digest@yahoogroups.com>

> >

> > >     ASCOM-Talk-fullfeatured@yahoogroups.com

> > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>

> >

> > >

> >

> > >     ASCOM-Talk-unsubscribe@yahoogroups.com

> > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>

> >

> > >

> >

> > >     http://docs.yahoo.com/info/terms/

> > <http://docs.yahoo.com/info/terms/>

> >

> >

> >

> >

> > --

> > ExchangeDefender Message Security: Click below to verify authenticity

> >

> http://www.exchangedefender.com/verify.asp?id=o61JtsK5023776&from=ti

> m@...

> > Complete email hygeine and business continuity solution available from

> > http://www.tigranetworks.co.uk

> >

>

>

>

>

> ------------------------------------

>

> For more information see http://ASCOM-Standards.org/.

>

> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU

> USED TO SUBSCRIBE(!) to:

> ASCOM-Talk-unsubscribe@yahoogroups.com

>

> Yahoo! Groups Links

>

> <*> To visit your group on the web, go to:

>     http://groups.yahoo.com/group/ASCOM-Talk/

>

> <*> Your email settings:

>     Individual Email | Traditional

>

> <*> To change settings online go to:

>     http://groups.yahoo.com/group/ASCOM-Talk/join

>     (Yahoo! ID required)

>

> <*> To change settings via email:

>     ASCOM-Talk-digest@yahoogroups.com

>     ASCOM-Talk-fullfeatured@yahoogroups.com

>

> <*> To unsubscribe from this group, send an email to:

>     ASCOM-Talk-unsubscribe@yahoogroups.com

>

> <*> Your use of Yahoo! Groups is subject to:

>     http://docs.yahoo.com/info/terms/

 


ExchangeDefender Message Security: Check Authenticity
Complete email hygeine and business continuity solution available from TiGra Networks


#21189 From: "robt2112" <robt2112@...>
Date: Thu Jul 1, 2010 9:06 pm
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
robt2112
Send Email Send Email
 
Paul,

Ok I see I have to go to the cmd to get to it. Its not browesable by explorer.
The problem still is I cannot use it unless it exists in Common
Files\ASCOM\.net. Putting the file there allows me to access ASCOM.Interfaces.

Robert
--- In ASCOM-Talk@yahoogroups.com, "paulkccd" <yh@...> wrote:
>
> Robert, check under Windows\Assembly\GAC_MSIL\ASCOM.Interfaces\. You should be
able to see a folder that starts with 1.0.0.0_... and contains the actual DLL.
This is installed by platform 5.0 install.
>
> At least that's where the 5.0b installer put it on my clean XP VM.
>
> Regards,
>
>     -Paul
>
>
> --- In ASCOM-Talk@yahoogroups.com, "robt2112" <robt2112@> wrote:
> >
> > Well unfortunately if you try to develop with platform 5.5 it doesnt work
unless you have the dll. Visual Studio complains that you must add a reference
to ASCOM.Interfaces when you add DriverAcess. The message the interface are
defined in ASCOM.Interfaces and must be referenced in the project.
> >
> > The only way to actually develop in .NET with platform 5.5 is to include the
ghost ASCOM.Interfaces.dll. Now also if you look in the GAC ASCOM.Interfaces.dll
is registered, but there is no actual file. Look at windows/assembly you will
see ASCOM.Interfaces and the Original Filename property points to
ASCOM.Interfaces.dll. This file exists nowhere on the system.
> >
> > So in platform 5.5 dependencies in SVN the mystery dll is there and is part
of the dependent assemblies. So without it you can't develop a driver. So if you
want to see further put visual studio express in your clean vm and try to write
a .NET driver that references one of the interfaces.
> >
> >
> > Robert
> >
> >
> >
> >
> > --- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@> wrote:
> > >
> > > OK, let me try this one more time. I have double checked all of this and
> > > I am 100% certain this is accurate. Let me be clear that I am talking
> > > about the RELEASED platform 5.5 and not anything that came from
> > > subversion.
> > >
> > >
> > >
> > >
> > > There is no assembly called ASCOM.Interfaces.dll1 in Platform 5.5, it
> > > should not be in your filesystem anywhere2,3.
> > >
> > >
> > >
> > >
> > >
> > >
> > > The ASCOM Interfaces are COM objects and are obtained from the COM tab
> > > in the references dialog. You'll note that what you are actually
> > > referencing is the type library, thus:
> > >
> > >
> > >
> > > There is no bug, there should be no DLL file.
> > >
> > >
> > >
> > > OK, now for the footnotes J
> > >
> > >
> > >
> > > ________________________________
> > >
> > > 1 In fact, technically the interfaces are defined in a special type of
> > > .NET assembly - a Primary Interop Assembly - which is created by
> > > importing the type library (.tlb) file, is installed in the GAC (not the
> > > filesystem) and is given special treatment by visual studio. For all
> > > intents and purposes, it appears to be a COM object in Visual Studio and
> > > that's how you should reference it.
> > >
> > > 2 In fact, items in the GAC are also in the filesystem, but their
> > > location is obfuscated and direct access is verboten. If you examine the
> > > folder c:\windows\assembly (in Windows Explorer) you'll see that the
> > > assembly is indeed listed:
> > >
> > > However, all it contains is a thin veneer of metadata that makes
> > > IntelliSense work properly. The actual interfaces are defined in the
> > > type library, which in turn is generated from an IDL file.
> > >
> > > 3 If you've checked out the code base from Subversion, then you'll have
> > > the DLL file in your filesystem - but I'm ignoring that situation
> > > because it's fairly uncommon for end users at the moment.
> > >
> > >
> > >
> > > --Tim
> > >
> > >
> > >
> > > > -----Original Message-----
> > >
> > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > >
> > > > Talk@yahoogroups.com] On Behalf Of robt2112
> > >
> > > > Sent: 01 July 2010 20:18
> > >
> > > > To: ASCOM-Talk@yahoogroups.com
> > >
> > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> > >
> > > >
> > >
> > > > The related issue then is if it is not there then you cant reference
> > > the
> > >
> > > > interfaces in Visual Studio. It doesn't exist anywhere searching the
> > > entire c
> > >
> > > > drive of the VM. The file is required for development in Visual
> > > Studio.
> > >
> > > >
> > >
> > > > Robert
> > >
> > > >
> > >
> > > > --- In ASCOM-Talk@yahoogroups.com <mailto:ASCOM-Talk@yahoogroups.com>
> > > , "Tim Long" <Tim@ <mailto:Tim@> > wrote:
> > >
> > > > >
> > >
> > > > > I wouldn't necessarily expect it to be there. Let me try the same
> > >
> > > > > thing myself and I'll get back to you.
> > >
> > > > > --Tim
> > >
> > > > >
> > >
> > > > > > -----Original Message-----
> > >
> > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > >
> > > > > > Talk@yahoogroups.com] On Behalf Of robt2112
> > >
> > > > > > Sent: 01 July 2010 18:06
> > >
> > > > > > To: ASCOM-Talk@yahoogroups.com
> > >
> > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> > >
> > > > > >
> > >
> > > > > > Just for completeness of testing this issue I started a VM with
> > > win
> > >
> > > > > xp. Never
> > >
> > > > > > had anything ascom related. Installed 5.0b. The C:\Program
> > >
> > > > > Files\Common
> > >
> > > > > > Files\ASCOM\.net is created with just the .vsi template in it.
> > >
> > > > > >
> > >
> > > > > > Install 5.5.1 update. The following is the contents of the .net
> > >
> > > > > > folder
> > >
> > > > > after
> > >
> > > > > > install. ASCOM.Interfaces.dll is missing.
> > >
> > > > > >
> > >
> > > > > > Robert
> > >
> > > > > >
> > >
> > > > > >
> > >
> > > > > >
> > >
> > > > > > Directory of C:\Program Files\Common Files\ASCOM\.net
> > >
> > > > > >
> > >
> > > > > > 7/01/2010  01:02 PM    <DIR>          .
> > >
> > > > > > 7/01/2010  01:02 PM    <DIR>          ..
> > >
> > > > > > 1/21/2009  11:30 PM           523,264 ASCOM Diagnostics.exe
> > >
> > > > > > 1/21/2009  11:30 PM           212,480 ASCOM Diagnostics.pdb
> > >
> > > > > > 1/24/2009  09:50 PM           540,160 ASCOM.Astrometry.dll
> > >
> > > > > > 1/24/2009  09:50 PM           249,344 ASCOM.Astrometry.pdb
> > >
> > > > > > 7/01/2010  01:02 PM            28,824 ASCOM.Astrometry.tlb
> > >
> > > > > > 1/24/2009  09:50 PM           247,602 ASCOM.Astrometry.xml
> > >
> > > > > > 1/24/2009  09:49 PM             5,632 ASCOM.Attributes.dll
> > >
> > > > > > 1/24/2009  09:49 PM            13,824 ASCOM.Attributes.pdb
> > >
> > > > > > 7/10/2008  02:21 PM            53,248 ASCOM.DriverAccess.dll
> > >
> > > > > > 7/10/2008  02:21 PM           105,984 ASCOM.DriverAccess.pdb
> > >
> > > > > > 7/10/2008  02:21 PM           105,045 ASCOM.DriverAccess.XML
> > >
> > > > > > 1/20/2009  08:24 AM             9,216 ASCOM.Exceptions.dll
> > >
> > > > > > 1/20/2009  08:24 AM            21,933 ASCOM.Exceptions.XML
> > >
> > > > > > 8/01/2009  04:33 PM           125,783 ASCOM.ico
> > >
> > > > > > 1/20/2009  08:24 AM            14,336 ASCOM.IConform.dll
> > >
> > > > > > 1/20/2009  08:24 AM            34,304 ASCOM.IConform.pdb
> > >
> > > > > > 7/01/2010  01:02 PM             3,808 ASCOM.IConform.tlb
> > >
> > > > > > 1/20/2009  08:24 AM             9,589 ASCOM.IConform.xml
> > >
> > > > > > 1/24/2009  09:49 PM           251,392 ASCOM.Utilities.dll
> > >
> > > > > > 1/24/2009  09:49 PM           214,528 ASCOM.Utilities.pdb
> > >
> > > > > > 7/01/2010  01:02 PM            21,216 ASCOM.Utilities.tlb
> > >
> > > > > > 1/24/2009  09:49 PM           171,112 ASCOM.Utilities.xml
> > >
> > > > > > 1/17/2009  06:28 PM           397,566 ASCOMDriverTemplates.vsi
> > >
> > > > > > 4/15/2009  11:58 PM               489 driveraccess.config
> > >
> > > > > > 1/20/2009  08:25 AM            12,288 FusionLib.dll
> > >
> > > > > > 1/20/2009  08:25 AM            15,872 FusionLib.pdb
> > >
> > > > > > 1/20/2009  08:25 AM            15,360 GACInstall.exe
> > >
> > > > > > 8/01/2009  04:33 PM            37,376 NOVAS-C.dll
> > >
> > > > > > 8/01/2009  04:33 PM           207,872 NOVAS-C.pdb
> > >
> > > > > > 8/01/2009  04:33 PM            52,224 NOVAS-C64.dll
> > >
> > > > > > 8/01/2009  04:33 PM           199,680 NOVAS-C64.pdb
> > >
> > > > > > 4/15/2009  11:58 PM             3,072
> > >
> > > > > policy.1.0.ASCOM.DriverAccess.dll
> > >
> > > > > > 1/17/2009  09:10 AM             3,584
> > > policy.5.5.ASCOM.Astrometry.dll
> > >
> > > > > > 1/17/2009  09:10 AM             3,584
> > > policy.5.5.ASCOM.Utilities.dll
> > >
> > > > > > 1/17/2009  09:10 AM               741 PublisherPolicy.xml
> > >
> > > > > > 9/23/2009  10:13 PM               683 ReadMe55.txt
> > >
> > > > > >              36 File(s)      3,913,015 bytes
> > >
> > > > > >               2 Dir(s)  80,084,582,400 bytes free
> > >
> > > > > >
> > >
> > > > > > :\Program Files\Common Files\ASCOM\.net>
> > >
> > > > > >
> > >
> > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@> wrote:
> > >
> > > > > > >
> > >
> > > > > > > This was a fresh computer nothing installed. 5.0b first then
> > >
> > > > > > > update
> > >
> > > > > to 5.5.1.
> > >
> > > > > > The COM interfaces were installed with the tlb file in the ASCOM
> > >
> > > > > folder. The
> > >
> > > > > > .net dll was missing in the .net folder.
> > >
> > > > > > >
> > >
> > > > > > > Robert
> > >
> > > > > > >
> > >
> > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@> wrote:
> > >
> > > > > > > >
> > >
> > > > > > > > I find it hard to believe that the problem is what you say it
> > > is.
> > >
> > > > > > > > The interfaces PIA is so fundamental to ASCOM that we would
> > > have
> > >
> > > > > > > > caught that a long time ago. Can we please be clear about
> > >
> > > > > > > > version numbers - when you say "the installer" which version
> > > are
> > >
> > > > > > > > you
> > >
> > > > > talking
> > >
> > > > > > about?
> > >
> > > > > > > >
> > >
> > > > > > > > To get ASCOM 5.5.1 you must first install 5.0a or 5.0b (not
> > > both).
> > >
> > > > > > > > The 5.0a/b installer includes and installs the interfaces PIA
> > > in
> > >
> > > > > the
> > >
> > > > > > > > GAC, I am 100% certain that works correctly because it has
> > > been
> > >
> > > > > > > > tested to death on many different systems, by all the ASCOM
> > >
> > > > > > > > developers and beta testers and on many end user systems.
> > >
> > > > > > > >
> > >
> > > > > > > > Something about this incident doesn't make sense. I would like
> > >
> > > > > > > > to get to the bottom of it, but I don't think it is a bug in
> > > the
> > >
> > > > > installer.
> > >
> > > > > > > >
> > >
> > > > > > > > Regards,
> > >
> > > > > > > > --Tim Long
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > -----Original Message-----
> > >
> > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > >
> > > > > > Talk@yahoogroups.com]
> > >
> > > > > > > > On Behalf Of robt2112
> > >
> > > > > > > > Sent: 01 July 2010 14:57
> > >
> > > > > > > > To: ASCOM-Talk@yahoogroups.com
> > >
> > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
> > >
> > > > > > > >
> > >
> > > > > > > > This was just a verification that it is a bug in the
> > > installer.
> > >
> > > > > The
> > >
> > > > > > > > file should have been installed. I verified that the file was
> > >
> > > > > > > > missing and that putting the file in place solves the problem.
> > >
> > > > > This
> > >
> > > > > > > > should be fixed in the installation.
> > >
> > > > > > > >
> > >
> > > > > > > > Robert
> > >
> > > > > > > >
> > >
> > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@> wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > If you do that... you're on your own! We've got to be very
> > >
> > > > > careful
> > >
> > > > > > > > about
> > >
> > > > > > > > > letting users do stuff like that because it will create
> > >
> > > > > confusion
> > >
> > > > > > > > > and
> > >
> > > > > > > > a
> > >
> > > > > > > > > support nightmare.
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > ASCOM interfaces is (currently) a COM object that lives in
> > > the
> > >
> > > > > > > > > GAC. It should be installed by the platform installer and
> > >
> > > > > > > > > referenced from the COM tab of the references dialog.
> > >
> > > > > > > > >
> > >
> > > > > > > > > --Tim
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > -----Original Message-----
> > >
> > > > > > > > > From: ASCOM-Talk@yahoogroups.com
> > >
> > > > > > > > > [mailto:ASCOM-Talk@yahoogroups.com]
> > >
> > > > > > > > On
> > >
> > > > > > > > > Behalf Of robt2112
> > >
> > > > > > > > > Sent: 01 July 2010 02:20
> > >
> > > > > > > > > To: ASCOM-Talk@yahoogroups.com
> > >
> > > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in
> > > .NET
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > Well... If I copy the dll from my svn download to common
> > >
> > > > > > > > > files\ascom\.net then it shows up on my .NET references tab
> > > in
> > >
> > > > > VS.
> > >
> > > > > > > > > So
> > >
> > > > > > > > I
> > >
> > > > > > > > > think the problem is the dll is not included in the install.
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > Robert
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112" <robt2112@>
> > >
> > > > > > wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > Yes in windows\assembly it shows ASCOM.Interfaces that
> > >
> > > > > > > > > > points
> > >
> > > > > to
> > >
> > > > > > > > > ASCOM.Interfaces.dll. The only thing that shows up in Visual
> > >
> > > > > > > > > Studio is
> > >
> > > > > > > > a
> > >
> > > > > > > > > reference in COM to the tlb located in Program Files\Common
> > >
> > > > > > > > > Files\ASCOM\Interfaces.
> > >
> > > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > I do have a copy of the dll in the Platform Dependancies
> > >
> > > > > folder
> > >
> > > > > > > > > > of
> > >
> > > > > > > > the
> > >
> > > > > > > > > ASCOM platform Drivers and Simulators that I downloaded from
> > >
> > > > > SVN.
> > >
> > > > > > > > > The dll doesn't seem to get installed with the platform
> > > install.
> > >
> > > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > Robert
> > >
> > > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> , "paulkccd" <yh@> wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > As far as I can tell, platform 5 installs
> > >
> > > > > ASCOM.Interface.dll
> > >
> > > > > > > > > > > in
> > >
> > > > > > > > > GAC, not in Common Files\ASCOM. Check Windows\Assembly
> > >
> > > > folder
> > >
> > > > > > > > > to see
> > >
> > > > > > > > if
> > >
> > > > > > > > > it's there.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > Regards,
> > >
> > > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > >     -Paul
> > >
> > > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
> > >
> > > > <robt2112@>
> > >
> > > > > > wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > Slight correction. I installed Platform 5.0b then
> > >
> > > > > > > > > > > > updated
> > >
> > > > > to
> > >
> > > > > > > > > 5.5.1. Both show installed in programs and features.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > Robert
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> , "robt2112"
> > >
> > > > > > > > > > > > <robt2112@>
> > >
> > > > > > wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > Well I think what is wrong is the installer for
> > > 5.5.1.
> > >
> > > > > > > > > > > > > This is
> > >
> > > > > > > > a
> > >
> > > > > > > > > brand new install. I havent installed any previous versions
> > >
> > > > > which
> > >
> > > > > > > > > are not available on the website. I just installed the
> > > latest
> > >
> > > > > > > > > version. The Interfaces dll was not installed.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > I believe if you had installed a previous platform
> > >
> > > > > version
> > >
> > > > > > > > that
> > >
> > > > > > > > > dll would be there. Since I installed fresh it didn't get on
> > >
> > > > > > > > > my
> > >
> > > > > > > > machine.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > Robert
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> , "Tim Long" <Tim@>
> > >
> > > > > > wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > I'm assuming you have .NET 3.5 and ASCOM Platform
> > > 5.5.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > Paul is correct that it's a .NET assembly, but it
> > > is
> > >
> > > > > > > > > > > > > > also a
> > >
> > > > > > > > > COM Primary
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > Interop Assembly (PIA) so (confusingly) it show up
> > >
> > > > > under
> > >
> > > > > > > > > > > > > > the
> > >
> > > > > > > > > COM tab as
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > shown here:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > So reference that, and also from the .NET tab,
> > > bring
> > >
> > > > > in
> > >
> > > > > > > > > > > > > > the
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > ASCOM.DriverAccess namespace thus:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > Your project's references would then look
> > > something
> > >
> > > > > like
> > >
> > > > > > > > this
> > >
> > > > > > > > > (I'm using
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > C# in VS2010, yours may appear differently):
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > Then in visual studio, you can use some code like
> > >
> > > > > > > > > > > > > > this to
> > >
> > > > > > > > > test:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > using System;
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > using ASCOM.DriverAccess;
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > namespace ConsoleApplication1
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > {
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >     class Program
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >     {
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >         static void Main(string[] args)
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >         {
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >             var userChoice =
> > >
> > > > > > > > > > > > > > Telescope.Choose(String.Empty);
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >             var scope = new Telescope(userChoice);
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >             scope.Connected = true;
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >             scope.Park();
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >             scope.Connected = false;
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >             scope.Dispose();
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >             scope = null;
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >         }
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >     }
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > }
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > This code does work, I just ran it. If you can't
> > > get
> > >
> > > > > > > > > > > > > > this to
> > >
> > > > > > > > > work, then
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > something is badly wrong and needs sorting out.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > --Tim
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > -----Original Message-----
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > Talk@yahoogroups.com
> > > <mailto:Talk@yahoogroups.com> ] On Behalf Of robt2112
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > Sent: 30 June 2010 20:53
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > To: ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM
> > >
> > > > > driver
> > >
> > > > > > > > > > > > > > > in
> > >
> > > > > > > > > .NET
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > It should be, but its not on my .NET assembly
> > > tab
> > >
> > > > > > > > > > > > > > > in
> > >
> > > > > > > > visual
> > >
> > > > > > > > > studio. I
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > only see it
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > on the COM tab. Looks like the install didnt not
> > >
> > > > > > > > > > > > > > > register
> > >
> > > > > > > > > something.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > This is a
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > new Win7 machine with a brand new ASCOM install.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > Robert
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com>
> > >
> > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > , "paulkccd" <yh@ <mailto:yh@ <mailto:yh@> > >
> > > wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > ASCOM.Interfaces is a .NET assembly, not COM.
> > >
> > > > > > > > > > > > > > > > You can
> > >
> > > > > > > > add
> > >
> > > > > > > > > a
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > reference
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > to it from the .NET tab in Visual Studio Add
> > >
> > > > > > > > > > > > > > > References
> > >
> > > > > > > > > dialog.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > Regards,
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > >     -Paul
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"
> > >
> > > > > > > > > > > > > > <robt2112@>
> > >
> > > > > > > > > wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > That is what I was trying. I cant get access
> > >
> > > > > > > > > > > > > > > > > to
> > >
> > > > > > > > > ITelescope. I
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > added a
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > reference to DriverAccess and it complained that
> > >
> > > > > > > > > > > > > > > the
> > >
> > > > > > > > > interfaces were
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > defined
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > in ASCOM.Interfaces. I added that reference from
> > >
> > > > > COM,
> > >
> > > > > > > > > > > > > > > but
> > >
> > > > > > > > > dont see a
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > .NET
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > version. When I try to use ASCOM.ITelescope it
> > >
> > > > > > > > > > > > > > > complains
> > >
> > > > > > > > it
> > >
> > > > > > > > > doesn't
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > exist.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > It won't let you create an instance with
> > > Type
> > >
> > > > > > > > Telescope.
> > >
> > > > > > > > > It says I
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > must use
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > ITelescope.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > Robert
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> > , "paulkccd"
> > >
> > > > > > > > > > > > > > <yh@>
> > >
> > > > > > > > wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > And this is how I'd do it in C#:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >      ITelescope g;
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >      g =
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASCOM
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > .Gemin\
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > iTelescope.Telescope"));
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >      g.Connected = true;
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > Regards,
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >       -Paul
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> > , "paulkccd"
> > >
> > > > > > > > > > > > > > <yh@>
> > >
> > > > > > > > wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > Rob, what error do you get? Here's
> > > sample
> > >
> > > > > > > > > > > > > > > > > > > VB.Net
> > >
> > > > > > > > > code I sent
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > to
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > a
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > Gemini
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > user:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope g =
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > CreateObject("ASCOM.GeminiTelescope.Telescope"
> > >
> > > > > > > > > > > > > > > > > > > )
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > g.Connected = True
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > You just need to add a reference
> > >
> > > > > > > > > > > > > > > > > > > ASCOM.Interfaces
> > >
> > > > > > > > > assembly.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > Does this not work for you?
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > Regards,
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > -Paul
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
> > > <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"
> > >
> > > > > > > > > > > > > > robt2112@
> > >
> > > > > > > > > wrote:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > > So this is basic question. How do I
> > >
> > > > > > > > > > > > > > > > > > > > access and
> > >
> > > > > > > > use
> > >
> > > > > > > > > an ASCOM
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > > driver
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > in
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > .NET code. I keep running into cant
> > > create
> > >
> > > > > > > > instances
> > >
> > > > > > > > > that
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > represent
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > COM
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > components.
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > > Robert
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > ------------------------------------
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > For more information see
> > >
> > > > > > > > > > > > > > > http://ASCOM-Standards.org/
> > > <http://ASCOM-Standards.org/>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <http://ASCOM-Standards.org/
> > > <http://ASCOM-Standards.org/> > .
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > To unsubscribe from this group, send an email
> > > FROM
> > >
> > > > > THE
> > >
> > > > > > > > > ACCOUNT YOU
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > USED TO SUBSCRIBE(!) to:
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > > Yahoo! Groups Links
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > > <http://groups.yahoo.com/group/ASCOM-Talk/>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/
> > > <http://groups.yahoo.com/group/ASCOM-Talk/> >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >     Individual Email | Traditional
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > > http://groups.yahoo.com/group/ASCOM-Talk/join
> > > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join
> > > <http://groups.yahoo.com/group/ASCOM-Talk/join> >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >     (Yahoo! ID required)
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> > > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com
> > > <mailto:ASCOM-Talk-digest@yahoogroups.com> >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com
> > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com> >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > >     http://docs.yahoo.com/info/terms/
> > > <http://docs.yahoo.com/info/terms/>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > <http://docs.yahoo.com/info/terms/
> > > <http://docs.yahoo.com/info/terms/> >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > --
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > ExchangeDefender Message Security: Click below to
> > >
> > > > > verify
> > >
> > > > > > > > > authenticity
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > >
> > >
> > > > http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from
> > > <http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from>
> > >
> > > > > > =
> > >
> > > > > > > > > tim@
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > > Complete email hygeine and business continuity
> > >
> > > > > solution
> > >
> > > > > > > > > available from http://www.tigranetworks.co.uk
> > > <http://www.tigranetworks.co.uk>
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > ------------------------------------
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > For more information see http://ASCOM-Standards.org/
> > > <http://ASCOM-Standards.org/> .
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > To unsubscribe from this group, send an email FROM THE
> > > ACCOUNT
> > >
> > > > > > YOU
> > >
> > > > > > > > USED
> > >
> > > > > > > > > TO SUBSCRIBE(!) to:
> > >
> > > > > > > > >
> > >
> > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > Yahoo! Groups Links
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > > <http://groups.yahoo.com/group/ASCOM-Talk/>
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >     Individual Email | Traditional
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> > >
> > > > > > > > >
> > >
> > > > > > > > >     (Yahoo! ID required)
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> > > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >     http://docs.yahoo.com/info/terms/
> > > <http://docs.yahoo.com/info/terms/>
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > >
> > >
> > > > > > > > > --
> > >
> > > > > > > > > ExchangeDefender Message Security: Click below to verify
> > >
> > > > > > > > > authenticity
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > >
> > >
> > > > http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from
> > > <http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from> =
> > >
> > > > > > ti
> > >
> > > > > > > > m@
> > >
> > > > > > > > .
> > >
> > > > > > > > > Complete email hygeine and business continuity solution
> > >
> > > > > available
> > >
> > > > > > > > > from
> > >
> > > > > > > > http://www.tigranetworks.co.uk
> > > <http://www.tigranetworks.co.uk>
> > >
> > > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > ------------------------------------
> > >
> > > > > > > >
> > >
> > > > > > > > For more information see http://ASCOM-Standards.org/
> > > <http://ASCOM-Standards.org/> .
> > >
> > > > > > > >
> > >
> > > > > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT
> > >
> > > > > > > > YOU USED TO SUBSCRIBE(!) to:
> > >
> > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > > > > > >
> > >
> > > > > > > > Yahoo! Groups Links
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > >
> > >
> > > > > > > > --
> > >
> > > > > > > > ExchangeDefender Message Security: Click below to verify
> > >
> > > > > > > > authenticity
> > >
> > > > > > > >
> > >
> > > > > >
> > >
> > > > http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from
> > > <http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from> =
> > >
> > > > > > ti
> > >
> > > > > > > > m@ Complete email hygeine and business continuity solution
> > >
> > > > > available
> > >
> > > > > > > > from http://www.tigranetworks.co.uk
> > > <http://www.tigranetworks.co.uk>
> > >
> > > > > > > >
> > >
> > > > > > >
> > >
> > > > > >
> > >
> > > > > >
> > >
> > > > > >
> > >
> > > > > >
> > >
> > > > > > ------------------------------------
> > >
> > > > > >
> > >
> > > > > > For more information see http://ASCOM-Standards.org/
> > > <http://ASCOM-Standards.org/> .
> > >
> > > > > >
> > >
> > > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> > >
> > > > > > USED TO SUBSCRIBE(!) to:
> > >
> > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > > > >
> > >
> > > > > > Yahoo! Groups Links
> > >
> > > > > >
> > >
> > > > > >
> > >
> > > > > >
> > >
> > > > >
> > >
> > > > > --
> > >
> > > > > ExchangeDefender Message Security: Click below to verify
> > > authenticity
> > >
> > > > >
> > >
> > > > http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=t
> > > <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=tim@>
> > >
> > >
> > > > im@
> > > <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=tim@>
> > > ...
> > >
> > > > > Complete email hygeine and business continuity solution available
> > > from
> > >
> > > > > http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk>
> > >
> > > > >
> > >
> > > >
> > >
> > > >
> > >
> > > >
> > >
> > > >
> > >
> > > > ------------------------------------
> > >
> > > >
> > >
> > > > For more information see http://ASCOM-Standards.org/
> > > <http://ASCOM-Standards.org/> .
> > >
> > > >
> > >
> > > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> > >
> > > > USED TO SUBSCRIBE(!) to:
> > >
> > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > >
> > >
> > > > Yahoo! Groups Links
> > >
> > > >
> > >
> > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> > > <http://groups.yahoo.com/group/ASCOM-Talk/>
> > >
> > > >
> > >
> > > >     Individual Email | Traditional
> > >
> > > >
> > >
> > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> > > <http://groups.yahoo.com/group/ASCOM-Talk/join>
> > >
> > > >     (Yahoo! ID required)
> > >
> > > >
> > >
> > > >     ASCOM-Talk-digest@yahoogroups.com
> > > <mailto:ASCOM-Talk-digest@yahoogroups.com>
> > >
> > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
> > >
> > > >
> > >
> > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
> > >
> > > >
> > >
> > > >     http://docs.yahoo.com/info/terms/
> > > <http://docs.yahoo.com/info/terms/>
> > >
> > >
> > >
> > >
> > > --
> > > ExchangeDefender Message Security: Click below to verify authenticity
> > > http://www.exchangedefender.com/verify.asp?id=o61JtsK5023776&from=tim@
> > > Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
> > >
> >
>

#21190 From: "robt2112" <robt2112@...>
Date: Thu Jul 1, 2010 9:37 pm
Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
robt2112
Send Email Send Email
 
I will say this again. I have no MANUAL installation of the any dll. This is
right out of the install on a fresh machine. So I am going through this again.

If you reference the COM Master Interfaces you CANNOT access ASCOM.Interface in
Visual Studio. You can reference it but you CANNOT use it. It allows you to user
Driver Access does not give you a way to implement any interface.


The SOLUTION to the problem is to put ASCOM.Interfaces.dll into the .net folder
of Common Files\ASCOM. When you do that and restart Visual Studio all of sudden
you can say ASCOM.Interface. whaterver. Without the file you CANNOT do that in a
BASE install.

The file IS referenced in the BASE 5.5 dependencies because it is sitting right
there in SVN in the folder. Delete it from SVN if it is not needed.

Robert

--- In ASCOM-Talk@yahoogroups.com, "Tim Long" <Tim@...> wrote:
>
> Rob, I think you may have some wrong version of a DLL somewhere (THIS is
> why I strongly discourage manual installation of DLLs). I can build a
> solution just fine without ever referencing the interfaces DLL, which
> doesn't exist on my system. Even when I reference DriverAccess.
>
>
>
> Rob, I can see why you might think that - I just had the same error
> message myself. But what you actually need to reference is the "ASCOM
> Master Interfaces for COM and .NET" from the COM tab. It works. There's
> no DLL needed.
>
>
>
> I'm not sure that we have documented this anywhere, despite Peter's
> herculean efforts updating the developer documentation in Platform
> 5.5.1, the driver templates of course have this already wired up, so
> it's never a problem.
>
>
>
> So the best I can offer is: "Reference the Interfaces component in the
> COM tab". Please don't manually copy DLLs anywhere, that's just masking
> the real issue.
>
>
>
> --Tim
>
>
>
> > -----Original Message-----
>
> > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > Talk@yahoogroups.com] On Behalf Of robt2112
>
> > Sent: 01 July 2010 21:32
>
> > To: ASCOM-Talk@yahoogroups.com
>
> > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
> >
>
> > Well unfortunately if you try to develop with platform 5.5 it doesnt
> work
>
> > unless you have the dll. Visual Studio complains that you must add a
>
> > reference to ASCOM.Interfaces when you add DriverAcess. The message
> the
>
> > interface are defined in ASCOM.Interfaces and must be referenced in
> the
>
> > project.
>
> >
>
> > The only way to actually develop in .NET with platform 5.5 is to
> include the
>
> > ghost ASCOM.Interfaces.dll. Now also if you look in the GAC
>
> > ASCOM.Interfaces.dll is registered, but there is no actual file. Look
> at
>
> > windows/assembly you will see ASCOM.Interfaces and the Original
> Filename
>
> > property points to ASCOM.Interfaces.dll. This file exists nowhere on
> the
>
> > system.
>
> >
>
> > So in platform 5.5 dependencies in SVN the mystery dll is there and is
> part of
>
> > the dependent assemblies. So without it you can't develop a driver. So
> if you
>
> > want to see further put visual studio express in your clean vm and try
> to write
>
> > a .NET driver that references one of the interfaces.
>
> >
>
> >
>
> > Robert
>
> >
>
> >
>
> >
>
> >
>
> > --- In ASCOM-Talk@yahoogroups.com <mailto:ASCOM-Talk@yahoogroups.com>
> , "Tim Long" <Tim@ <mailto:Tim@> > wrote:
>
> > >
>
> > > OK, let me try this one more time. I have double checked all of this
>
> > > and I am 100% certain this is accurate. Let me be clear that I am
>
> > > talking about the RELEASED platform 5.5 and not anything that came
>
> > > from subversion.
>
> > >
>
> > >
>
> > >
>
> > >
>
> > > There is no assembly called ASCOM.Interfaces.dll1 in Platform 5.5,
> it
>
> > > should not be in your filesystem anywhere2,3.
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > > The ASCOM Interfaces are COM objects and are obtained from the COM
>
> > tab
>
> > > in the references dialog. You'll note that what you are actually
>
> > > referencing is the type library, thus:
>
> > >
>
> > >
>
> > >
>
> > > There is no bug, there should be no DLL file.
>
> > >
>
> > >
>
> > >
>
> > > OK, now for the footnotes J
>
> > >
>
> > >
>
> > >
>
> > > ________________________________
>
> > >
>
> > > 1 In fact, technically the interfaces are defined in a special type
> of
>
> > > .NET assembly - a Primary Interop Assembly - which is created by
>
> > > importing the type library (.tlb) file, is installed in the GAC (not
>
> > > the
>
> > > filesystem) and is given special treatment by visual studio. For all
>
> > > intents and purposes, it appears to be a COM object in Visual Studio
>
> > > and that's how you should reference it.
>
> > >
>
> > > 2 In fact, items in the GAC are also in the filesystem, but their
>
> > > location is obfuscated and direct access is verboten. If you examine
>
> > > the folder c:\windows\assembly (in Windows Explorer) you'll see that
>
> > > the assembly is indeed listed:
>
> > >
>
> > > However, all it contains is a thin veneer of metadata that makes
>
> > > IntelliSense work properly. The actual interfaces are defined in the
>
> > > type library, which in turn is generated from an IDL file.
>
> > >
>
> > > 3 If you've checked out the code base from Subversion, then you'll
>
> > > have the DLL file in your filesystem - but I'm ignoring that
> situation
>
> > > because it's fairly uncommon for end users at the moment.
>
> > >
>
> > >
>
> > >
>
> > > --Tim
>
> > >
>
> > >
>
> > >
>
> > > > -----Original Message-----
>
> > >
>
> > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > >
>
> > > > Talk@yahoogroups.com <mailto:Talk@yahoogroups.com> ] On Behalf Of
> robt2112
>
> > >
>
> > > > Sent: 01 July 2010 20:18
>
> > >
>
> > > > To: ASCOM-Talk@yahoogroups.com <mailto:ASCOM-Talk@yahoogroups.com>
>
>
> > >
>
> > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
> > >
>
> > > >
>
> > >
>
> > > > The related issue then is if it is not there then you cant
> reference
>
> > > the
>
> > >
>
> > > > interfaces in Visual Studio. It doesn't exist anywhere searching
> the
>
> > > entire c
>
> > >
>
> > > > drive of the VM. The file is required for development in Visual
>
> > > Studio.
>
> > >
>
> > > >
>
> > >
>
> > > > Robert
>
> > >
>
> > > >
>
> > >
>
> > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> >
>
> > > , "Tim Long" <Tim@ <mailto:Tim@ <mailto:Tim@> > > wrote:
>
> > >
>
> > > > >
>
> > >
>
> > > > > I wouldn't necessarily expect it to be there. Let me try the
> same
>
> > >
>
> > > > > thing myself and I'll get back to you.
>
> > >
>
> > > > > --Tim
>
> > >
>
> > > > >
>
> > >
>
> > > > > > -----Original Message-----
>
> > >
>
> > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > >
>
> > > > > > Talk@yahoogroups.com <mailto:Talk@yahoogroups.com> ] On Behalf
> Of robt2112
>
> > >
>
> > > > > > Sent: 01 July 2010 18:06
>
> > >
>
> > > > > > To: ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > >
>
> > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > Just for completeness of testing this issue I started a VM
> with
>
> > > win
>
> > >
>
> > > > > xp. Never
>
> > >
>
> > > > > > had anything ascom related. Installed 5.0b. The C:\Program
>
> > >
>
> > > > > Files\Common
>
> > >
>
> > > > > > Files\ASCOM\.net is created with just the .vsi template in it.
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > Install 5.5.1 update. The following is the contents of the
> .net
>
> > >
>
> > > > > > folder
>
> > >
>
> > > > > after
>
> > >
>
> > > > > > install. ASCOM.Interfaces.dll is missing.
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > Robert
>
> > >
>
> > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > Directory of C:\Program Files\Common Files\ASCOM\.net
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > 7/01/2010  01:02 PM    <DIR>          .
>
> > >
>
> > > > > > 7/01/2010  01:02 PM    <DIR>          ..
>
> > >
>
> > > > > > 1/21/2009  11:30 PM           523,264 ASCOM Diagnostics.exe
>
> > >
>
> > > > > > 1/21/2009  11:30 PM           212,480 ASCOM Diagnostics.pdb
>
> > >
>
> > > > > > 1/24/2009  09:50 PM           540,160 ASCOM.Astrometry.dll
>
> > >
>
> > > > > > 1/24/2009  09:50 PM           249,344 ASCOM.Astrometry.pdb
>
> > >
>
> > > > > > 7/01/2010  01:02 PM            28,824 ASCOM.Astrometry.tlb
>
> > >
>
> > > > > > 1/24/2009  09:50 PM           247,602 ASCOM.Astrometry.xml
>
> > >
>
> > > > > > 1/24/2009  09:49 PM             5,632 ASCOM.Attributes.dll
>
> > >
>
> > > > > > 1/24/2009  09:49 PM            13,824 ASCOM.Attributes.pdb
>
> > >
>
> > > > > > 7/10/2008  02:21 PM            53,248 ASCOM.DriverAccess.dll
>
> > >
>
> > > > > > 7/10/2008  02:21 PM           105,984 ASCOM.DriverAccess.pdb
>
> > >
>
> > > > > > 7/10/2008  02:21 PM           105,045 ASCOM.DriverAccess.XML
>
> > >
>
> > > > > > 1/20/2009  08:24 AM             9,216 ASCOM.Exceptions.dll
>
> > >
>
> > > > > > 1/20/2009  08:24 AM            21,933 ASCOM.Exceptions.XML
>
> > >
>
> > > > > > 8/01/2009  04:33 PM           125,783 ASCOM.ico
>
> > >
>
> > > > > > 1/20/2009  08:24 AM            14,336 ASCOM.IConform.dll
>
> > >
>
> > > > > > 1/20/2009  08:24 AM            34,304 ASCOM.IConform.pdb
>
> > >
>
> > > > > > 7/01/2010  01:02 PM             3,808 ASCOM.IConform.tlb
>
> > >
>
> > > > > > 1/20/2009  08:24 AM             9,589 ASCOM.IConform.xml
>
> > >
>
> > > > > > 1/24/2009  09:49 PM           251,392 ASCOM.Utilities.dll
>
> > >
>
> > > > > > 1/24/2009  09:49 PM           214,528 ASCOM.Utilities.pdb
>
> > >
>
> > > > > > 7/01/2010  01:02 PM            21,216 ASCOM.Utilities.tlb
>
> > >
>
> > > > > > 1/24/2009  09:49 PM           171,112 ASCOM.Utilities.xml
>
> > >
>
> > > > > > 1/17/2009  06:28 PM           397,566 ASCOMDriverTemplates.vsi
>
> > >
>
> > > > > > 4/15/2009  11:58 PM               489 driveraccess.config
>
> > >
>
> > > > > > 1/20/2009  08:25 AM            12,288 FusionLib.dll
>
> > >
>
> > > > > > 1/20/2009  08:25 AM            15,872 FusionLib.pdb
>
> > >
>
> > > > > > 1/20/2009  08:25 AM            15,360 GACInstall.exe
>
> > >
>
> > > > > > 8/01/2009  04:33 PM            37,376 NOVAS-C.dll
>
> > >
>
> > > > > > 8/01/2009  04:33 PM           207,872 NOVAS-C.pdb
>
> > >
>
> > > > > > 8/01/2009  04:33 PM            52,224 NOVAS-C64.dll
>
> > >
>
> > > > > > 8/01/2009  04:33 PM           199,680 NOVAS-C64.pdb
>
> > >
>
> > > > > > 4/15/2009  11:58 PM             3,072
>
> > >
>
> > > > > policy.1.0.ASCOM.DriverAccess.dll
>
> > >
>
> > > > > > 1/17/2009  09:10 AM             3,584
>
> > > policy.5.5.ASCOM.Astrometry.dll
>
> > >
>
> > > > > > 1/17/2009  09:10 AM             3,584
>
> > > policy.5.5.ASCOM.Utilities.dll
>
> > >
>
> > > > > > 1/17/2009  09:10 AM               741 PublisherPolicy.xml
>
> > >
>
> > > > > > 9/23/2009  10:13 PM               683 ReadMe55.txt
>
> > >
>
> > > > > >              36 File(s)      3,913,015 bytes
>
> > >
>
> > > > > >               2 Dir(s)  80,084,582,400 bytes free
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > :\Program Files\Common Files\ASCOM\.net>
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112" <robt2112@>
>
> > wrote:
>
> > >
>
> > > > > > >
>
> > >
>
> > > > > > > This was a fresh computer nothing installed. 5.0b first then
>
> > >
>
> > > > > > > update
>
> > >
>
> > > > > to 5.5.1.
>
> > >
>
> > > > > > The COM interfaces were installed with the tlb file in the
> ASCOM
>
> > >
>
> > > > > folder. The
>
> > >
>
> > > > > > .net dll was missing in the .net folder.
>
> > >
>
> > > > > > >
>
> > >
>
> > > > > > > Robert
>
> > >
>
> > > > > > >
>
> > >
>
> > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "Tim Long" <Tim@> wrote:
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > I find it hard to believe that the problem is what you say
>
> > > > > > > > it
>
> > > is.
>
> > >
>
> > > > > > > > The interfaces PIA is so fundamental to ASCOM that we
> would
>
> > > have
>
> > >
>
> > > > > > > > caught that a long time ago. Can we please be clear about
>
> > >
>
> > > > > > > > version numbers - when you say "the installer" which
> version
>
> > > are
>
> > >
>
> > > > > > > > you
>
> > >
>
> > > > > talking
>
> > >
>
> > > > > > about?
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > To get ASCOM 5.5.1 you must first install 5.0a or 5.0b
> (not
>
> > > both).
>
> > >
>
> > > > > > > > The 5.0a/b installer includes and installs the interfaces
>
> > > > > > > > PIA
>
> > > in
>
> > >
>
> > > > > the
>
> > >
>
> > > > > > > > GAC, I am 100% certain that works correctly because it has
>
> > > been
>
> > >
>
> > > > > > > > tested to death on many different systems, by all the
> ASCOM
>
> > >
>
> > > > > > > > developers and beta testers and on many end user systems.
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > Something about this incident doesn't make sense. I would
>
> > > > > > > > like
>
> > >
>
> > > > > > > > to get to the bottom of it, but I don't think it is a bug
> in
>
> > > the
>
> > >
>
> > > > > installer.
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > Regards,
>
> > >
>
> > > > > > > > --Tim Long
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > -----Original Message-----
>
> > >
>
> > > > > > > > From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-
>
> > >
>
> > > > > > Talk@yahoogroups.com <mailto:Talk@yahoogroups.com> ]
>
> > >
>
> > > > > > > > On Behalf Of robt2112
>
> > >
>
> > > > > > > > Sent: 01 July 2010 14:57
>
> > >
>
> > > > > > > > To: ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > >
>
> > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in
>
> > > > > > > > .NET
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > This was just a verification that it is a bug in the
>
> > > installer.
>
> > >
>
> > > > > The
>
> > >
>
> > > > > > > > file should have been installed. I verified that the file
>
> > > > > > > > was
>
> > >
>
> > > > > > > > missing and that putting the file in place solves the
> problem.
>
> > >
>
> > > > > This
>
> > >
>
> > > > > > > > should be fixed in the installation.
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > Robert
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "Tim Long" <Tim@> wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > If you do that... you're on your own! We've got to be
> very
>
> > >
>
> > > > > careful
>
> > >
>
> > > > > > > > about
>
> > >
>
> > > > > > > > > letting users do stuff like that because it will create
>
> > >
>
> > > > > confusion
>
> > >
>
> > > > > > > > > and
>
> > >
>
> > > > > > > > a
>
> > >
>
> > > > > > > > > support nightmare.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > ASCOM interfaces is (currently) a COM object that lives
> in
>
> > > the
>
> > >
>
> > > > > > > > > GAC. It should be installed by the platform installer
> and
>
> > >
>
> > > > > > > > > referenced from the COM tab of the references dialog.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > --Tim
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > -----Original Message-----
>
> > >
>
> > > > > > > > > From: ASCOM-Talk@yahoogroups.com
>
> > >
>
> > > > > > > > > [mailto:ASCOM-Talk@yahoogroups.com]
> <mailto:[mailto:ASCOM-Talk@yahoogroups.com]>
>
> > >
>
> > > > > > > > On
>
> > >
>
> > > > > > > > > Behalf Of robt2112
>
> > >
>
> > > > > > > > > Sent: 01 July 2010 02:20
>
> > >
>
> > > > > > > > > To: ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > >
>
> > > > > > > > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver
> in
>
> > > .NET
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > Well... If I copy the dll from my svn download to common
>
> > >
>
> > > > > > > > > files\ascom\.net then it shows up on my .NET references
>
> > > > > > > > > tab
>
> > > in
>
> > >
>
> > > > > VS.
>
> > >
>
> > > > > > > > > So
>
> > >
>
> > > > > > > > I
>
> > >
>
> > > > > > > > > think the problem is the dll is not included in the
> install.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > Robert
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112" <robt2112@>
>
> > >
>
> > > > > > wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > Yes in windows\assembly it shows ASCOM.Interfaces that
>
> > >
>
> > > > > > > > > > points
>
> > >
>
> > > > > to
>
> > >
>
> > > > > > > > > ASCOM.Interfaces.dll. The only thing that shows up in
>
> > > > > > > > > Visual
>
> > >
>
> > > > > > > > > Studio is
>
> > >
>
> > > > > > > > a
>
> > >
>
> > > > > > > > > reference in COM to the tlb located in Program
>
> > > > > > > > > Files\Common
>
> > >
>
> > > > > > > > > Files\ASCOM\Interfaces.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > I do have a copy of the dll in the Platform
> Dependancies
>
> > >
>
> > > > > folder
>
> > >
>
> > > > > > > > > > of
>
> > >
>
> > > > > > > > the
>
> > >
>
> > > > > > > > > ASCOM platform Drivers and Simulators that I downloaded
>
> > > > > > > > > from
>
> > >
>
> > > > > SVN.
>
> > >
>
> > > > > > > > > The dll doesn't seem to get installed with the platform
>
> > > install.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > Robert
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "paulkccd" <yh@> wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > As far as I can tell, platform 5 installs
>
> > >
>
> > > > > ASCOM.Interface.dll
>
> > >
>
> > > > > > > > > > > in
>
> > >
>
> > > > > > > > > GAC, not in Common Files\ASCOM. Check Windows\Assembly
>
> > >
>
> > > > folder
>
> > >
>
> > > > > > > > > to see
>
> > >
>
> > > > > > > > if
>
> > >
>
> > > > > > > > > it's there.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > Regards,
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > >     -Paul
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"
>
> > >
>
> > > > <robt2112@>
>
> > >
>
> > > > > > wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > Slight correction. I installed Platform 5.0b then
>
> > >
>
> > > > > > > > > > > > updated
>
> > >
>
> > > > > to
>
> > >
>
> > > > > > > > > 5.5.1. Both show installed in programs and features.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > Robert
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "robt2112"
>
> > >
>
> > > > > > > > > > > > <robt2112@>
>
> > >
>
> > > > > > wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > Well I think what is wrong is the installer for
>
> > > 5.5.1.
>
> > >
>
> > > > > > > > > > > > > This is
>
> > >
>
> > > > > > > > a
>
> > >
>
> > > > > > > > > brand new install. I havent installed any previous
>
> > > > > > > > > versions
>
> > >
>
> > > > > which
>
> > >
>
> > > > > > > > > are not available on the website. I just installed the
>
> > > latest
>
> > >
>
> > > > > > > > > version. The Interfaces dll was not installed.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > I believe if you had installed a previous
> platform
>
> > >
>
> > > > > version
>
> > >
>
> > > > > > > > that
>
> > >
>
> > > > > > > > > dll would be there. Since I installed fresh it didn't
> get
>
> > > > > > > > > on
>
> > >
>
> > > > > > > > > my
>
> > >
>
> > > > > > > > machine.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > Robert
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > , "Tim Long" <Tim@>
>
> > >
>
> > > > > > wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > I'm assuming you have .NET 3.5 and ASCOM
>
> > > > > > > > > > > > > > Platform
>
> > > 5.5.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > Paul is correct that it's a .NET assembly, but
>
> > > > > > > > > > > > > > it
>
> > > is
>
> > >
>
> > > > > > > > > > > > > > also a
>
> > >
>
> > > > > > > > > COM Primary
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > Interop Assembly (PIA) so (confusingly) it
> show
>
> > > > > > > > > > > > > > up
>
> > >
>
> > > > > under
>
> > >
>
> > > > > > > > > > > > > > the
>
> > >
>
> > > > > > > > > COM tab as
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > shown here:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > So reference that, and also from the .NET tab,
>
> > > bring
>
> > >
>
> > > > > in
>
> > >
>
> > > > > > > > > > > > > > the
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > ASCOM.DriverAccess namespace thus:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > Your project's references would then look
>
> > > something
>
> > >
>
> > > > > like
>
> > >
>
> > > > > > > > this
>
> > >
>
> > > > > > > > > (I'm using
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > C# in VS2010, yours may appear differently):
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > Then in visual studio, you can use some code
>
> > > > > > > > > > > > > > like
>
> > >
>
> > > > > > > > > > > > > > this to
>
> > >
>
> > > > > > > > > test:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > using System;
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > using ASCOM.DriverAccess;
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > namespace ConsoleApplication1
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > {
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >     class Program
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >     {
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >         static void Main(string[] args)
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >         {
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >             var userChoice =
>
> > >
>
> > > > > > > > > > > > > > Telescope.Choose(String.Empty);
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >             var scope = new
>
> > > > > > > > > > > > > > Telescope(userChoice);
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >             scope.Connected = true;
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >             scope.Park();
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >             scope.Connected = false;
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >             scope.Dispose();
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >             scope = null;
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >         }
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >     }
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > }
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > This code does work, I just ran it. If you
> can't
>
> > > get
>
> > >
>
> > > > > > > > > > > > > > this to
>
> > >
>
> > > > > > > > > work, then
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > something is badly wrong and needs sorting
> out.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > --Tim
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > -----Original Message-----
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > From: ASCOM-Talk@yahoogroups.com
>
> > > > > > > > > > > > > > > [mailto:ASCOM-
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > Talk@yahoogroups.com
> <mailto:Talk@yahoogroups.com>
>
> > > <mailto:Talk@yahoogroups.com <mailto:Talk@yahoogroups.com> > ] On
> Behalf Of robt2112
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > Sent: 30 June 2010 20:53
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > To: ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > Subject: [ASCOM] Re: Creating Instance to
>
> > > > > > > > > > > > > > > ASCOM
>
> > >
>
> > > > > driver
>
> > >
>
> > > > > > > > > > > > > > > in
>
> > >
>
> > > > > > > > > .NET
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > It should be, but its not on my .NET
> assembly
>
> > > tab
>
> > >
>
> > > > > > > > > > > > > > > in
>
> > >
>
> > > > > > > > visual
>
> > >
>
> > > > > > > > > studio. I
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > only see it
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > on the COM tab. Looks like the install didnt
>
> > > > > > > > > > > > > > > not
>
> > >
>
> > > > > > > > > > > > > > > register
>
> > >
>
> > > > > > > > > something.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > This is a
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > new Win7 machine with a brand new ASCOM
> install.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > Robert
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> >
>
> > >
>
> > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > , "paulkccd" <yh@ <mailto:yh@ <mailto:yh@
> <mailto:yh@%20%3cmailto:yh@> > > >
>
> > > wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > ASCOM.Interfaces is a .NET assembly, not
> COM.
>
> > >
>
> > > > > > > > > > > > > > > > You can
>
> > >
>
> > > > > > > > add
>
> > >
>
> > > > > > > > > a
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > reference
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > to it from the .NET tab in Visual Studio Add
>
> > >
>
> > > > > > > > > > > > > > > References
>
> > >
>
> > > > > > > > > dialog.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > Regards,
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > >     -Paul
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > > , "robt2112"
>
> > >
>
> > > > > > > > > > > > > > <robt2112@>
>
> > >
>
> > > > > > > > > wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > That is what I was trying. I cant get
>
> > > > > > > > > > > > > > > > > access
>
> > >
>
> > > > > > > > > > > > > > > > > to
>
> > >
>
> > > > > > > > > ITelescope. I
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > added a
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > reference to DriverAccess and it complained
>
> > > > > > > > > > > > > > > that
>
> > >
>
> > > > > > > > > > > > > > > the
>
> > >
>
> > > > > > > > > interfaces were
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > defined
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > in ASCOM.Interfaces. I added that reference
>
> > > > > > > > > > > > > > > from
>
> > >
>
> > > > > COM,
>
> > >
>
> > > > > > > > > > > > > > > but
>
> > >
>
> > > > > > > > > dont see a
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > .NET
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > version. When I try to use ASCOM.ITelescope
> it
>
> > >
>
> > > > > > > > > > > > > > > complains
>
> > >
>
> > > > > > > > it
>
> > >
>
> > > > > > > > > doesn't
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > exist.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > It won't let you create an instance with
>
> > > Type
>
> > >
>
> > > > > > > > Telescope.
>
> > >
>
> > > > > > > > > It says I
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > must use
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > ITelescope.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > Robert
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > > , "paulkccd"
>
> > >
>
> > > > > > > > > > > > > > <yh@>
>
> > >
>
> > > > > > > > wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > And this is how I'd do it in C#:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >      ITelescope g;
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >      g =
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > >
> (ITelescope)Activator.CreateInstance(Type.GetTypeFromProgID("ASC
>
> > > > > > OM
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > .Gemin\
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > iTelescope.Telescope"));
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >      g.Connected = true;
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > Regards,
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >       -Paul
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > > , "paulkccd"
>
> > >
>
> > > > > > > > > > > > > > <yh@>
>
> > >
>
> > > > > > > > wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > Rob, what error do you get? Here's
>
> > > sample
>
> > >
>
> > > > > > > > > > > > > > > > > > > VB.Net
>
> > >
>
> > > > > > > > > code I sent
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > to
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > a
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > Gemini
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > user:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > Dim g As ASCOM.Interface.ITelescope
> g
>
> > > > > > > > > > > > > > > > > > > =
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > CreateObject("ASCOM.GeminiTelescope.Telescope"
>
> > >
>
> > > > > > > > > > > > > > > > > > > )
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > g.Connected = True
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > You just need to add a reference
>
> > >
>
> > > > > > > > > > > > > > > > > > > ASCOM.Interfaces
>
> > >
>
> > > > > > > > > assembly.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > Does this not work for you?
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > Regards,
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > -Paul
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > --- In ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <mailto:ASCOM-Talk@yahoogroups.com
>
> > > <mailto:ASCOM-Talk@yahoogroups.com
> <mailto:ASCOM-Talk@yahoogroups.com> > > , "robt2112"
>
> > >
>
> > > > > > > > > > > > > > robt2112@
>
> > >
>
> > > > > > > > > wrote:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > > So this is basic question. How do
> I
>
> > >
>
> > > > > > > > > > > > > > > > > > > > access and
>
> > >
>
> > > > > > > > use
>
> > >
>
> > > > > > > > > an ASCOM
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > > driver
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > in
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > .NET code. I keep running into cant
>
> > > create
>
> > >
>
> > > > > > > > instances
>
> > >
>
> > > > > > > > > that
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > represent
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > COM
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > components.
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > > Robert
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > ------------------------------------
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > For more information see
>
> > >
>
> > > > > > > > > > > > > > > http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/>
>
> > > <http://ASCOM-Standards.org/ <http://ASCOM-Standards.org/> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <http://ASCOM-Standards.org/
>
> > > <http://ASCOM-Standards.org/ <http://ASCOM-Standards.org/> > > .
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > To unsubscribe from this group, send an
> email
>
> > > FROM
>
> > >
>
> > > > > THE
>
> > >
>
> > > > > > > > > ACCOUNT YOU
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > USED TO SUBSCRIBE(!) to:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > > Yahoo! Groups Links
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
> http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> > > <http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/
>
> > > <http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/> > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >     Individual Email | Traditional
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > > http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> > > <http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <http://groups.yahoo.com/group/ASCOM-Talk/join
>
> > > <http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join> > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >     (Yahoo! ID required)
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <mailto:ASCOM-Talk-digest@yahoogroups.com
>
> > > <mailto:ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com> > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com
>
> > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com> > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > >     http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/>
>
> > > <http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > <http://docs.yahoo.com/info/terms/
>
> > > <http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/> > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > --
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > ExchangeDefender Message Security: Click below
>
> > > > > > > > > > > > > > to
>
> > >
>
> > > > > verify
>
> > >
>
> > > > > > > > > authenticity
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > >
>
> > http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from
> <http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from>
>
> > >
>
> > <http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&fro
> <http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from>
>
> > m <http://www.exchangedefender.com/verify.asp?id=o5UMlMNa006131&from>
> >
>
> > >
>
> > > > > > =
>
> > >
>
> > > > > > > > > tim@
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > > Complete email hygeine and business continuity
>
> > >
>
> > > > > solution
>
> > >
>
> > > > > > > > > available from http://www.tigranetworks.co.uk
> <http://www.tigranetworks.co.uk>
>
> > > <http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > ------------------------------------
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/>
>
> > > <http://ASCOM-Standards.org/ <http://ASCOM-Standards.org/> > .
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > To unsubscribe from this group, send an email FROM THE
>
> > > ACCOUNT
>
> > >
>
> > > > > > YOU
>
> > >
>
> > > > > > > > USED
>
> > >
>
> > > > > > > > > TO SUBSCRIBE(!) to:
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > Yahoo! Groups Links
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> > > <http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >     Individual Email | Traditional
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> > > <http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >     (Yahoo! ID required)
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >     ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >     http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/>
>
> > > <http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > > > --
>
> > >
>
> > > > > > > > > ExchangeDefender Message Security: Click below to verify
>
> > >
>
> > > > > > > > > authenticity
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > >
>
> > http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from
> <http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from>
>
> > >
>
> > <http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from
> <http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from>
>
> > <http://www.exchangedefender.com/verify.asp?id=o61D0GSe023660&from> >
> =
>
> > >
>
> > > > > > ti
>
> > >
>
> > > > > > > > m@
>
> > >
>
> > > > > > > > .
>
> > >
>
> > > > > > > > > Complete email hygeine and business continuity solution
>
> > >
>
> > > > > available
>
> > >
>
> > > > > > > > > from
>
> > >
>
> > > > > > > > http://www.tigranetworks.co.uk
> <http://www.tigranetworks.co.uk>
>
> > > <http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk> >
>
> > >
>
> > > > > > > > >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > ------------------------------------
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/>
>
> > > <http://ASCOM-Standards.org/ <http://ASCOM-Standards.org/> > .
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > To unsubscribe from this group, send an email FROM THE
>
> > > > > > > > ACCOUNT
>
> > >
>
> > > > > > > > YOU USED TO SUBSCRIBE(!) to:
>
> > >
>
> > > > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > Yahoo! Groups Links
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > > > --
>
> > >
>
> > > > > > > > ExchangeDefender Message Security: Click below to verify
>
> > >
>
> > > > > > > > authenticity
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > >
>
> > http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from
> <http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from>
>
> > >
>
> > <http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from
> <http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from>
>
> > <http://www.exchangedefender.com/verify.asp?id=o61EjUNe003738&from> >
> =
>
> > >
>
> > > > > > ti
>
> > >
>
> > > > > > > > m@ Complete email hygeine and business continuity solution
>
> > >
>
> > > > > available
>
> > >
>
> > > > > > > > from http://www.tigranetworks.co.uk
> <http://www.tigranetworks.co.uk>
>
> > > <http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk> >
>
> > >
>
> > > > > > > >
>
> > >
>
> > > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > ------------------------------------
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/>
>
> > > <http://ASCOM-Standards.org/ <http://ASCOM-Standards.org/> > .
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > To unsubscribe from this group, send an email FROM THE ACCOUNT
>
> > > > > > YOU
>
> > >
>
> > > > > > USED TO SUBSCRIBE(!) to:
>
> > >
>
> > > > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > >
>
> > > > > >
>
> > >
>
> > > > > > Yahoo! Groups Links
>
> > >
>
> > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > > > >
>
> > >
>
> > > > >
>
> > >
>
> > > > > --
>
> > >
>
> > > > > ExchangeDefender Message Security: Click below to verify
>
> > > authenticity
>
> > >
>
> > > > >
>
> > >
>
> > > >
>
> > http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=t
> <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from=t>
>
> > >
>
> > <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from
>
> > =tim
>
> > > @>
>
> > >
>
> > >
>
> > > > im@
>
> > >
>
> > <http://www.exchangedefender.com/verify.asp?id=o61Ih4BV004614&from
>
> > =tim
>
> > > @>
>
> > > ...
>
> > >
>
> > > > > Complete email hygeine and business continuity solution
> available
>
> > > from
>
> > >
>
> > > > > http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk>
> <http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk> >
>
> > >
>
> > > > >
>
> > >
>
> > > >
>
> > >
>
> > > >
>
> > >
>
> > > >
>
> > >
>
> > > >
>
> > >
>
> > > > ------------------------------------
>
> > >
>
> > > >
>
> > >
>
> > > > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/>
>
> > > <http://ASCOM-Standards.org/ <http://ASCOM-Standards.org/> > .
>
> > >
>
> > > >
>
> > >
>
> > > > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
>
> > >
>
> > > > USED TO SUBSCRIBE(!) to:
>
> > >
>
> > > > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > >
>
> > > >
>
> > >
>
> > > > Yahoo! Groups Links
>
> > >
>
> > > >
>
> > >
>
> > > >     http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> > > <http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/> >
>
> > >
>
> > > >
>
> > >
>
> > > >     Individual Email | Traditional
>
> > >
>
> > > >
>
> > >
>
> > > >     http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> > > <http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join> >
>
> > >
>
> > > >     (Yahoo! ID required)
>
> > >
>
> > > >
>
> > >
>
> > > >     ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com> >
>
> > >
>
> > > >     ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com> >
>
> > >
>
> > > >
>
> > >
>
> > > >     ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> > > <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com> >
>
> > >
>
> > > >
>
> > >
>
> > > >     http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/>
>
> > > <http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/> >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > > --
>
> > > ExchangeDefender Message Security: Click below to verify
> authenticity
>
> > >
>
> > http://www.exchangedefender.com/verify.asp?id=o61JtsK5023776&from=ti
> <http://www.exchangedefender.com/verify.asp?id=o61JtsK5023776&from=tim@>
>
>
> > m@
> <http://www.exchangedefender.com/verify.asp?id=o61JtsK5023776&from=tim@>
> ...
>
> > > Complete email hygeine and business continuity solution available
> from
>
> > > http://www.tigranetworks.co.uk <http://www.tigranetworks.co.uk>
>
> > >
>
> >
>
> >
>
> >
>
> >
>
> > ------------------------------------
>
> >
>
> > For more information see http://ASCOM-Standards.org/
> <http://ASCOM-Standards.org/> .
>
> >
>
> > To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
>
> > USED TO SUBSCRIBE(!) to:
>
> > ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> >
>
> > Yahoo! Groups Links
>
> >
>
> >     http://groups.yahoo.com/group/ASCOM-Talk/
> <http://groups.yahoo.com/group/ASCOM-Talk/>
>
> >
>
> >     Individual Email | Traditional
>
> >
>
> >     http://groups.yahoo.com/group/ASCOM-Talk/join
> <http://groups.yahoo.com/group/ASCOM-Talk/join>
>
> >     (Yahoo! ID required)
>
> >
>
> >     ASCOM-Talk-digest@yahoogroups.com
> <mailto:ASCOM-Talk-digest@yahoogroups.com>
>
> >     ASCOM-Talk-fullfeatured@yahoogroups.com
> <mailto:ASCOM-Talk-fullfeatured@yahoogroups.com>
>
> >
>
> >     ASCOM-Talk-unsubscribe@yahoogroups.com
> <mailto:ASCOM-Talk-unsubscribe@yahoogroups.com>
>
> >
>
> >     http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/>
>
>
>
>
> --
> ExchangeDefender Message Security: Click below to verify authenticity
> http://www.exchangedefender.com/verify.asp?id=o61KxTUQ006640&from=tim@...
> Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk
>

#21191 From: Arlen Beiler <arlenbee@...>
Date: Thu Jul 1, 2010 10:33 pm
Subject: Documentation
arlenbee
Send Email Send Email
 
We should have a place for documentation that people can edit. Something like WikiBooks, maybe.

#21192 From: Arlen Beiler <arlenbee@...>
Date: Thu Jul 1, 2010 10:59 pm
Subject: Re: Documentation
arlenbee
Send Email Send Email
 
http://en.wikibooks.org/wiki/Ascom

On Thu, Jul 1, 2010 at 6:33 PM, Arlen Beiler <arlenbee@...> wrote:
We should have a place for documentation that people can edit. Something like WikiBooks, maybe.


#21193 From: "Tim Long" <Tim@...>
Date: Thu Jul 1, 2010 11:56 pm
Subject: RE: [ASCOM] Re: Creating Instance to ASCOM driver in .NET
t_p_long
Send Email Send Email
 

Oops, that first paragraph was meant to be replaced by the second para. Please disregard that. I could indeed build the solution but only because I hadn’t actually used the reference, once I used it I got the same error message as Rob.

--Tim

 

From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On Behalf Of Tim Long
Sent: 01 July 2010 21:59
To: ASCOM-Talk@yahoogroups.com
Subject: RE: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

 




Rob, I think you may have some wrong version of a DLL somewhere (THIS is why I strongly discourage manual installation of DLLs). I can build a solution just fine without ever referencing the interfaces DLL, which doesn’t exist on my system. Even when I reference DriverAccess.

 

Rob, I can see why you might think that – I just had the same error message myself. But what you actually need to reference is the “ASCOM Master Interfaces for COM and .NET” from the COM tab. It works. There’s no DLL needed.

 

I’m not sure that we have documented this anywhere, despite Peter’s herculean efforts updating the developer documentation in Platform 5.5.1, the driver templates of course have this already wired up, so it’s never a problem.

 

So the best I can offer is: “Reference the Interfaces component in the COM tab”. Please don’t manually copy DLLs anywhere, that’s just masking the real issue.

 

--Tim

 

> -----Original Message-----

> From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-

> Talk@yahoogroups.com] On Behalf Of robt2112

> Sent: 01 July 2010 21:32

> To: ASCOM-Talk! @yahoogroups.com

> Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

>

> Well unfortunately if you try to develop with platform 5.5 it doesnt work

> unless you have the dll. Visual Studio complains that you must add a

> reference to ASCOM.Interfaces when you add DriverAcess. The message the

> interface are defined in ASCOM.Interfaces and must be referenced in the

> project.

>

> The only way to actually develop in .NET with platform 5.5 is to include the

> ghost ASCOM.Interfaces.dll. Now also if you look in the GAC

> ASCOM.Interfaces.dll is registered, but there is no actual file. Look at

> windows/assembly you will see ASCOM.Interface! s and the Original Filename

> property points to ASCOM.Interfaces.dll. This file exists nowhere on the

> system.

>

> So in platform 5.5 dependencies in SVN the mystery dll is there and is part of

> the dependent assemblies. So without it you can't develop a driver. So if you

> want to see further put visual studio express in your clean vm and try to write

> a .NET driver that references one of the interfaces.

>

>

> Robert

>

>

>

>

> --- In ASCOM-Talk@yahoogroups! .com, "Tim Long" <Tim@...> wrote:

> >

> > OK, let me try this one more time. I have double checked all of this

> > and I am 100% certain this is accurate. Let me be clear that I am

> > talking about the RELEASED platform 5.5 and not anything that came

> > from subversion.

> >

> >

> >

> >

> > There is no assembly called ASCOM.Interfaces.dll1 in Platform 5.5, it

> > should not be in your filesystem anywhere2,3.

> >

> >

> >

> >

> >

> >

> > The ASCOM Interfaces are COM objects and are obtained from the COM

> tab

> > in the references dialog. You'll note that what you are actually

> > referencing is the type library, thus:

> >

> >

> >

> > There is no bug, there should be no DLL file.

> >

> >

> >

> > OK, now for the footnotes J

> >

> >

> >

> > ________________________________

> >

> > 1 In fact, technically the interfaces are defined in a specia! l type of

> > .NET assembly - a Primary Interop Assembly - which is created by

> > importing the type library (.tlb) file, is installed in the GAC (not

> > the

> > filesystem) and is given special treatment by visual studio. For all

> > intents and purposes, it appears to be a COM object in Visual Studio

> > and that's how you should reference it.

> >

> > 2 In fact, items in the GAC are also in the filesystem, but their

> > location is obfuscated and direct access is verboten. If you examine

> > the folder c:\windows\assembly (in Windows Explorer) you'll see that

> > the assembly is indeed listed:

> >

> > However, all it contains is a thin veneer o! f metadata that makes

> > IntelliSense work properly. The actual interfaces are defined in the

> > type library, which in turn is generated from an IDL file.

> >

> > 3 If you've checked out the code base from Subversion, then you'll

> > have the DLL file in your filesystem - but I'm ignoring that situation

> > because it's fairly uncommon for end users at the moment.

> >

> >

> >

> > --Tim

> >

> >

> >

> > > -----Original Message-----

> >

> > > From: ASCOM-Talk@yahoogroups.com [mailt! o:ASCOM-

> >

& gt; > > Talk@yahoogroups.com] On Behalf Of robt2112

> >

> > > Sent: 01 July 2010 20:18

> >

> > > To: ASCOM-Talk@yahoogroups.com

> >

> > > Subject: [ASCOM] Re: Creating Instance to ASCOM driver in .NET

> >

> > >

> >

> > > The related issue then is if it is not there then you cant reference

> > the

> >

> > > interfaces in Visual Studio. It doesn't exist ! anywhere searching the

> > entire c

> >

> > > drive of the VM. The file is required for development in Visual

> > Studio.

> >

> > >

> >

> > > Robert

> >

> > >

> >

> > > --- In ASCOM-Talk@yahoogroups.com

> > > <mailto:ASCOM-Talk@yahoogroups.com>

> > , "Tim Long" <Tim@ <mailto:Tim@> > wrote:

> >

> > > >

> >

> > > > I wouldn't necessarily expect it to be there. Let me try the same