Way to download an activex on client silently and register it

[patrickdrd]

Hello all!

I have written a VB 6 project which validates an ini file and,
if it is well-formed, load it on a database table.

However, I am working on an asp.net project now
and I what I had in mind is:
turn the old project into an activex dll,
download that activex in the client's computer silently and register it
(if it does not exist or if it is old versioned),
and validate the ini using javascript (" ... new ActiveXObject ..."),
passing the client's local ini file and,
if everything is ok,
submit it to the server.

My question is:
how can I download the activex on the client's computer silently and register it
using asp.net?

Do I need to sign it? How?

Thanks in advance!

 

[ca8msm]

I don't think that will be possible. Imagine how insecure it would be to allow anyone to install anything they wanted on your pc...


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[patrickdrd]

It is on the internet and this process will be run only by adminstrators
(after the login)

Right now I was thinking of a setup,
if I navigate the user to a url that contains the setup, is this ok?
will the dialog "open/save/cancel" appear or do I have to give the asp.net account list folder contents permissions?

or tell me any other way,
I do not care so much about the silent thing,
let it be manual,
since, if the user refuses to install, I would check (with javascript) if the object can be created, and if not, the whole process thereafter won't run

 

[ca8msm]

Why not just allow the user to upload the INI file, validate it and if necessary, write the contents to the db?


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[patrickdrd]

Yes ca8msm, that's another solution,
but I was thinking of moving the traffic out of the server and do that on the client

(in that way I won't have to port my vb 6 code to asp .net as well ;-) - not tough though)