Thanks to everyone for getting me over the bumpy parts. My first "real" .NET applicaiton is now ready for the test bed and then deployment. I installed the .NET 1.1 framework on a fresh machine, copied over the applicaiton files and started it up only to be greeted with errors. Can someone please tell me how to proceed?

The first message comes up in a "MedRecs Desktop.exe - Common Language Runtime Debugging Services" window and says, "Application has generated an exception that could not be handled. Process id=0x8b0(2224), Thread id=0x824(2084) Click OK to terminate the application. Click CANCEL to debug the applicaiton."

OK, C programmers aren't very good about making error messages descriptive... No big deal. Click CANCEL to start the debugger...

A "MedRecs Desktop.exe - No debugger found." window pops up that says, "Registered JIT debugger is not available. An attempt to launch a JIT debugger with the following command resulted in an error code of 0x2(2). Please check computer settings. cordbg.exe !a 0x854 Click on Retry to have the process wait while attaching a debugger manually. Click on Cancel to abort the JIT debug request."

I don't imaging the .NET Framework includes a debugger, so I opted to attach to it from my development box. Not an option I'd have in the real world, but at least it's something.

I click Retry and go to my dev box, and under the debug menu select Processes... I select the test bed machine and get a "Microsoft Development Environment" window that says, "Unable to connect to the machine 'TestBed'. The debugger is not properly installed. Run setup to install or repair the debugger."

Since I know the debugger on my dev box works in my dev environment, I assume the message is talking about installing a debugger on the remote machine. Is that correct? How do I go about doing that?

Help!

Mike