Like the idea behind TinyCLR OS but seems there are some issues yet. I am using Community VS 2017 on Windows 10. I have a .NET Micro Framework program running fine on a G30 TH module. Redid the program as a TinyCLR project. Debugging abilities is one of the biggest reasons to use a platform that can be programmed with VS. I was finding running on the G30 the first breakpoint would work and stepping into would work but if Continue was tried seemed like the program was being restarted and I get…
Looking for a device on transport ‘USB’.
Found device port ‘USB’ with ID ‘686db267-b4f4-417c-b612-558d0251492f’ for transport ‘Usb’.
Starting device deployment.
Attempting to connect to device ‘USB:G30’: iteration 0.
Opening port '\?..port
Attaching debugger engine.
Debugger engine attached.
Querying device assemblies.
- TinyCLR00 v188.8.131.52.
- mscorlib v0.5.0.0.
- GHIElectronics.TinyCLR.Devices v0.5.0.0.
Generating device specific assemblies.
- TinyCLR00 v184.108.40.206 with size 9,568 bytes at '…file
- mscorlib v0.5.0.0 with size 76,636 bytes at '…file
- GHIElectronics.TinyCLR.Devices v0.5.0.0 with size 39,492 bytes at '…file
Total deployment size is 125,696 bytes.
Incrementally deploying assemblies to the device:
All assemblies on the device are up to date. No deployment was necessary.
Attaching to device.
Waiting for device to initialize.
The debugger engine failed to receive any debug events from the debugging target
Also some code in the .NET micro platform that used a method referenced by type name keeps getting a null reference exception even if the exact same code was fine under NET micro