Com ports, FW2.0 and RemoteDesktop?

[belzona]

I have this small program that uses the serialports class in FW2.

When run in a remote session (WinXP, console connection, LocalAdminRights) everyting but the com-port parts seem to work (file and registry access). Accessing com-ports just halts the program, and on only EndProcess from TaskManager will kill it.

Running the program sitting in front of the computer there are no problems. Only the FW, no developer tools are installed (So no debugger?).

OK; security settings - AdministrativeTools\.NET configuration. No. Only for the FW1.1. Checked another machine - same thing. Only my development computer has the config-tools for 2.0.


So my 3 questions:

Is it security settings, that halts the program (no error msg)?
Where is the .NET2.0 settings on a non-develop computer?
I have looked through possible settings, but don't see anything I can relate to this problem?

[conipto]

Is the .NET 2.0 framework installed on the other machines?

The serialport class is new to 2.0, right? Wouldn't that break the program running under 1.1?

(On my machine it's here with the 1.1 - see pic)

Bill

[belzona]

Yes, the 2.0 FW is on the other machines. The program works when logged in with keyboard and screen directly attached.

My development PC has the same .NET entries under admin tools as yours, the two (that I've looked at so far) with only the 'runtimes' only has the two for .NET1.1.

I think my next move is remoting to my own PC, and running the program in the debugger.