
Best Answer Mike Hole, 07 August 2013 - 08:21 PM
Found it. Because the project started with the wrong framework (my bad) it had the following conditional compilation symbol:
TRACE,MF_FRAMEWORK_VERSION_V4_2
Once removed it started debugging again

![]() |
  | ||||||||||||||||||||||||||
![]() |
|
![]() |
|||||||||||||||||||||||||
![]() Windows 8.1 on Surface Pro. Debugging issue.
Started by Mike Hole, Aug 07 2013 04:18 PM
windows 8 debugging
![]() Best Answer Mike Hole, 07 August 2013 - 08:21 PM
Found it. Because the project started with the wrong framework (my bad) it had the following conditional compilation symbol:
TRACE,MF_FRAMEWORK_VERSION_V4_2
Once removed it started debugging again ![]()
4 replies to this topic
#1
Posted 07 August 2013 - 04:18 PM Hi,
I know one simple answer is serves you right trying preproduction software but...
I have a N+2 with MF 4.2.2.2 installed on it. If I plug this device into my desktop machine that is running Windows 8 everything works fine and I am able to debug code on the device in the normal fashion.
If I try the same on my Surface Pro with 8.1 preview installed on it I get the following error when trying to debug:
1>------ Deploy started: Project: MicroSerialization.BlueSMiRF.TestApp, Configuration: Debug Any CPU ------ 1>------ Deploy started: Project: MicroSerialization.BlueSMiRF.TestApp, Configuration: Debug Any CPU ------ 1>An error has occurred: please check your hardware. 1>DebugPort.GetDeviceProcess() called with no argument 1>Source: Microsoft.SPOT.Debugger.CorDebug 1>Stack : 1> at Microsoft.SPOT.Debugger.DebugPort.GetDeviceProcess(String deviceName) in d:SDcurrentclient_v4_3FrameworkCorDebugDebugPort.cs:line 290 1> at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.GetDeviceProcess() in d:SDcurrentclient_v4_3FrameworkCorDebugVsProjectFlavorCfg.cs:line 750 1> at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.Deploy(DebugPort port) in d:SDcurrentclient_v4_3FrameworkCorDebugVsProjectFlavorCfg.cs:line 827 1> at Microsoft.SPOT.Debugger.VsProjectFlavorCfg.<>c__DisplayClass2.<Microsoft.VisualStudio.Shell.Interop.IVsDeployableProjectCfg.StartDeploy>b__0() in d:SDcurrentclient_v4_3FrameworkCorDebugVsProjectFlavorCfg.cs:line 639 ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Has anybody else had this on Windows 8.1 or other systems and resolved it?
#2
Posted 07 August 2013 - 07:36 PM Does your ND appear in device manager?
I am unsure if the driver will work with the 8.1 preview, i personally havnt tried 8.1 due to the full reinstall needed once it goes RC.
Nak.
#3
Posted 07 August 2013 - 08:02 PM The device plays well with MFDeploy (pings connects debugger etc.) so the device drivers look ok but I can't say for sure.
#4
Posted 07 August 2013 - 08:21 PM Best Answer Found it. Because the project started with the wrong framework (my bad) it had the following conditional compilation symbol:
TRACE,MF_FRAMEWORK_VERSION_V4_2
Once removed it started debugging again
#5
Posted 07 August 2013 - 08:22 PM Very odd if MFDeploy works, have you tried changing the deployment method from USB to serial in your VS project settings, save the changes then change back to usb and save your project settings again, then try deploying.
Nak.
Ahh just saw you fixed it
Glad all is working for you now. Edited by nakchak, 07 August 2013 - 08:24 PM.
Also tagged with one or more of these keywords: windows 8, debugging
1 user(s) are reading this topic0 members, 1 guests, 0 anonymous users | |||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||
![]() |
|
![]() |
|||||||||||||||||||||||||
![]() |
This webpage is licensed under a Creative Commons Attribution-ShareAlike License. | ![]() |
|||||||||||||||||||||||||
![]() |