how to control serial port of client in asp.net??

[Adrian Chen]

please help me! I come across a problem.
Now I develop a finger print management system which is based on B/S.When
users click a button in the web pages, a device connected to the COM1 serial
port of the client machine starts to work.
Now I wrote the code which is in charge of serial communication in the
..aspx.cx pages, but then I found that when uses click the button, it is the
server's serial port that starts to work,not the clients!!

who can tell me how I could control the serial port communication in client
through asp.net?

I am very nervous about it now!

Thank you very much!!!

 

[Jeroen Mostert]

Now I develop a finger print management system which is based on B/S.

Unfortunately, many real-world systems are based on BS...

When users click a button in the web pages, a device connected to the
COM1 serial port of the client machine starts to work. Now I wrote the
code which is in charge of serial communication in the .aspx.cx pages,
but then I found that when uses click the button, it is the server's
serial port that starts to work,not the clients!!

Yes, that's the general idea. Except for generated client-side script,
ASP.NET code runs on the server, not the client.

who can tell me how I could control the serial port communication in client
through asp.net?

You can't, at least not directly. You need a client-side application for
this, not a web page. You could deploy one through ClickOnce, for example.

You could alternatively repackage your code as an ActiveX control and use
that from the web page. This requires the use of IE and probably lowered
security settings.

A third alternative would be to use an off-the-shelf ActiveX control for
serial communication, but I don't think this is worth it as opposed to
repackaging your own code (which is easy enough to do). One possible
advantage is that the off-the-shelf code will probably not need the .NET
runtime.

 

[Adrian Chen]

Jeroen Mostert, thank you very much!

Unfortunately, many real-world systems are based on BS...

Yes, that's the general idea. Except for generated client-side script,
ASP.NET code runs on the server, not the client.

You can't, at least not directly. You need a client-side application for
this, not a web page. You could deploy one through ClickOnce, for example.

You could alternatively repackage your code as an ActiveX control and use
that from the web page. This requires the use of IE and probably lowered
security settings.

A third alternative would be to use an off-the-shelf ActiveX control for
serial communication, but I don't think this is worth it as opposed to
repackaging your own code (which is easy enough to do). One possible
advantage is that the off-the-shelf code will probably not need the .NET
runtime.