M
moondaddy
I have a .net 2.0 winforms app which I'm deploying via clickonce.
Unfortunately one of the things that needs to be installed during the
clickonce is an MS Access mde application which uses a 3rd party control.
this 3rd party control is an 'ocx' file. In the old days I would install
this Access application using Installsheild which would install and register
the ocx file on the target machines. Now in the click once environment, how
do I get this ocx file installed? One thing I was thinking of was (if
clickonce can't install the ocx) would be to use InstallShield to build a
small install exe which would just install the ocx. then have clickonce
deploy this install.exe along with all the other files that are part of the
clickonce deployment. after everything is copied to the target machine and
before clickonce starts the .net app, it could run the install.exe which
would in turn install the ocx. In this case, how would I get clickonce to
run the install.exe?
any other ideas?
Thanks.
Unfortunately one of the things that needs to be installed during the
clickonce is an MS Access mde application which uses a 3rd party control.
this 3rd party control is an 'ocx' file. In the old days I would install
this Access application using Installsheild which would install and register
the ocx file on the target machines. Now in the click once environment, how
do I get this ocx file installed? One thing I was thinking of was (if
clickonce can't install the ocx) would be to use InstallShield to build a
small install exe which would just install the ocx. then have clickonce
deploy this install.exe along with all the other files that are part of the
clickonce deployment. after everything is copied to the target machine and
before clickonce starts the .net app, it could run the install.exe which
would in turn install the ocx. In this case, how would I get clickonce to
run the install.exe?
any other ideas?
Thanks.