I'm not an expert VB programmer, but I needed to be able to read the status of a device through COM1 (RS232) on the server computer for a web application. I cobbled together a simple program to read from a serial port and write out a status file. I used an RS232 vb.net class I found on the 'net and it works great. I monitor the serial port in a separate thread, and when it reads data, it calls a separate subroutine to read, and then re-write the status file using the StreamReader and StreamWriter classes.
The problem I'm running into is that if .NET Framework 3.5 isn't loaded, everything looks like it's running, but the text file never gets updated. I can see the last read status is updated on my status line, so the thread and the RS232 interface are running properly. The stream classes (as well as the Threads) all say they are supported in .Net 1.0, and I'm not getting any error messages or anything -- any exceptions are updated in the status bar too.
Of course, I discovered the failure when I flew to corporate HQ to demo the application and it wouldn't run properly on the computers there. I was still able to demo it by running it on my laptop. .NET 1.0 was already installed. I loaded .NET 2.0, then .NET 3.0 and it still wouldn't work. When I install .NET 3.5 it works fine.
Any ideas what could be wrong? Ever hear of anything like this?
--Bryan
The problem I'm running into is that if .NET Framework 3.5 isn't loaded, everything looks like it's running, but the text file never gets updated. I can see the last read status is updated on my status line, so the thread and the RS232 interface are running properly. The stream classes (as well as the Threads) all say they are supported in .Net 1.0, and I'm not getting any error messages or anything -- any exceptions are updated in the status bar too.
Of course, I discovered the failure when I flew to corporate HQ to demo the application and it wouldn't run properly on the computers there. I was still able to demo it by running it on my laptop. .NET 1.0 was already installed. I loaded .NET 2.0, then .NET 3.0 and it still wouldn't work. When I install .NET 3.5 it works fine.
Any ideas what could be wrong? Ever hear of anything like this?
--Bryan