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

  • Thread starter Thread starter DraguVaso
  • Start date Start date
D

DraguVaso

Hi,

I have an VB.NET application that uses an OCX for some control. I integrated
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. Everything
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 some
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
 
Check the documentation under:

ms-help://MS.VSCC/MS.MSDNQTR.2004JAN.1033/vbcon/html/vboriInstallationCompon
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
 
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,
 
Great idea's!! Thanks guys!!!

wesley said:
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,
Click to expand...
 
Back
Top