OT: BO w/Serial port and ASP.NET

OT: BO w/Serial port and ASP.NET

Old forum URL: forums.lhotka.net/forums/t/3756.aspx


esteban404 posted on Monday, October 22, 2007

I *thought* I'd run into issues accessing local hardware from an ASP.NET application so a winform client would have to run on the machine, but I can't find the resource to confirm it, so I'm bothering people here. I'm not an ASP.NET coder except BO stuff, but I am required to do UI stuff more frequently. I know .net 2 is better capable to do this, so I'll be writing some tests soon.

Using CSLA 3.x and .NET 2.0 I need to allow an ASP.NET client computer to open and read a serial port and send updates to a data store all within the same domain, no firewalls are transversed. I'm preparing for the actual programming portion of it, but didn't know if another (intermediate) service is required to get the data. (Win/Web service, etc.) Writing to the port is not required.

The requirement is simple from a winform perspective: a form's control to a  com port using INotifyPropertyChanged to detect voltage changes (current method) which indicate a count needs to increase. the count quantity is updated locally and sent to the data store for public access. The data stream from the port is consistent, and isn't required to be interpreted... just known to exist/not exist.

AFAIK, a property in a CSLA BO (or any class for that matter) cannot directly bind to a serial port. Only a [form] control can do that. Anyone have any experience doing this? Article to point me to.

Thanks in advance,

_E

Copyright (c) Marimer LLC