.NET Application Updater Component: how to handle an OCX?

Re: .NET Application Updater Component: how to handle an OCX?

Check the documentation under:

ms-help://MS.VSCC/MS.MSDNQTR.2004 JAN.1033/vbcon/html/vboriInstallati onCompon
ents.htm

Essentially you'll add a class that, after the installation of the
components, can manually register the component for you. The classes in the
..NET Framwork make this pretty easy to do.

Pete


"DraguVaso" <pietercoucke@h otmail.com> wrote in message
news:%238tOrfjS EHA.2408@tk2msf tngp13.phx.gbl. ..[color=blue]
> Hi,
>
> I have an VB.NET application that uses an OCX for some control. I[/color]
integrated[color=blue]
> the application with the .NET Application Updater Component
> (http://windowsforms.net/articles/appupdater.aspx) to copy automaticly new
> versions of the application to the clients.
>
> The problem is: it copies the OCX, but the OCX isn't registered.[/color]
Everything[color=blue]
> works fine until the the directory of the old version is deleted: The
> application doesn't find anymore a registered ocx, and therefore throws an
> error.
>
> Is there anyway how I could work aroudn this problem? Can I make it
> registered automaticly? Or make it in some way that it shouldn't be
> registered? Maybe be playing with the way I reference it in VS.NET? Or[/color]
some[color=blue]
> way I can put it in my first setup so I won't have this problem with other
> updates?
>
> Thanks a lot in advance,
>
> Pieter
>
>[/color]

Re: .NET Application Updater Component: how to handle an OCX?

Hi Dragu,

I had a similar problem. Basically you have to modify your application
launcher. This is called the AppStart in the updater application block. This
is the main process that will copy the downloaded files into the current
directory. As you see .ocx file you have to do your manual registration of
the component.

HTH,
[color=blue]
> Hi,
>
> I have an VB.NET application that uses an OCX for some control. I[/color]
integrated[color=blue]
> the application with the .NET Application Updater Component
> (http://windowsforms.net/articles/appupdater.aspx) to copy automaticly new
> versions of the application to the clients.
>
> The problem is: it copies the OCX, but the OCX isn't registered.[/color]
Everything[color=blue]
> works fine until the the directory of the old version is deleted: The
> application doesn't find anymore a registered ocx, and therefore throws an
> error.
>
> Is there anyway how I could work aroudn this problem? Can I make it
> registered automaticly? Or make it in some way that it shouldn't be
> registered? Maybe be playing with the way I reference it in VS.NET? Or[/color]
some[color=blue]
> way I can put it in my first setup so I won't have this problem with other
> updates?
>
> Thanks a lot in advance,
>
> Pieter
>
>[/color]

Re: .NET Application Updater Component: how to handle an OCX?

Great idea's!! Thanks guys!!!

"wesley" <wes@inthemix.c om.au> wrote in message
news:u7r$bIsSEH A.556@tk2msftng p13.phx.gbl...[color=blue]
> Hi Dragu,
>
> I had a similar problem. Basically you have to modify your application
> launcher. This is called the AppStart in the updater application block.[/color]
This[color=blue]
> is the main process that will copy the downloaded files into the current
> directory. As you see .ocx file you have to do your manual registration of
> the component.
>
> HTH,
>[color=green]
> > Hi,
> >
> > I have an VB.NET application that uses an OCX for some control. I[/color]
> integrated[color=green]
> > the application with the .NET Application Updater Component
> > (http://windowsforms.net/articles/appupdater.aspx) to copy automaticly[/color][/color]
new[color=blue][color=green]
> > versions of the application to the clients.
> >
> > The problem is: it copies the OCX, but the OCX isn't registered.[/color]
> Everything[color=green]
> > works fine until the the directory of the old version is deleted: The
> > application doesn't find anymore a registered ocx, and therefore throws[/color][/color]
an[color=blue][color=green]
> > error.
> >
> > Is there anyway how I could work aroudn this problem? Can I make it
> > registered automaticly? Or make it in some way that it shouldn't be
> > registered? Maybe be playing with the way I reference it in VS.NET? Or[/color]
> some[color=green]
> > way I can put it in my first setup so I won't have this problem with[/color][/color]
other[color=blue][color=green]
> > updates?
> >
> > Thanks a lot in advance,
> >
> > Pieter
> >
> >[/color]
>
>[/color]