T
TimRegan
Hi Folks,
Sorry if this is the wrong DL for this query. If it is wrong please
point me at the correct one.
I'm developing applications for the Pocket PC (the HP iPaq h5550)
using C# and the .Net Compact Framework and using eMbedded Visual C++
4
Recently my .Net Compact Framework application has consistently failed
to start from the IDE. When I hit F5, I get the following output,
including a long wait.
------ Build started: Project: TuneUsingMatsAPI, Configuration: Debug
Pocket PC ------
Preparing resources...
Updating references...
Performing main compilation...
Build complete -- 0 errors, 0 warnings
Building satellite assemblies...
Visual Studio is ready to deploy TuneUsingMatsAPI
------ Deploy started: Project: TuneUsingMatsAPI, Configuration: Debug
Pocket PC ------
Deploying to Pocket PC Device using TCP Connect Transport
Connected to Pocket PC Device (Pocket PC) running on ARMV4.
Copying files from 'C:\Documents and Settings\v-tregan\My
Documents\Visual Studio Projects\zcast\TuneUsingMatsAPI\bin\Debug' to
'\Program Files\TuneUsingMatsAPI'
Copying TuneUsingMatsAPI.exe
---------------------- Done ----------------------
Build: 1 succeeded, 0 failed, 0 skipped
Deploy: 1 succeeded, 0 failed, 0 skipped
Launching Application
Error while trying to run project: Unable to start debugging.
Unable to start program 'C:\Documents and Settings\v-tregan\My
Documents\Visual Studio
Projects\zcast\TuneUsingMatsAPI\bin\Debug\TuneUsingMatsAPI.exe'.
The application starts without problem if I start it on the device. At
first I thought it was one iPaq, because one would fail while the
other worked. Then they both started failing so I did a factory reset
on one of the iPaqs. This did not fix it! That suggested it was the
project settings so I tried a new wizard-built 'hallo world' project.
But that failed too.
Throughout this the projects built using eMbedded Visual C++ 4 have
deployed and run from the IDE onto the device without trouble.
What's going on and how do I fix it? I'm reduced to doing all my
debugging in the app not the IDE which is painful.
Cheers,
Tim.
Sorry if this is the wrong DL for this query. If it is wrong please
point me at the correct one.
I'm developing applications for the Pocket PC (the HP iPaq h5550)
using C# and the .Net Compact Framework and using eMbedded Visual C++
4
Recently my .Net Compact Framework application has consistently failed
to start from the IDE. When I hit F5, I get the following output,
including a long wait.
------ Build started: Project: TuneUsingMatsAPI, Configuration: Debug
Pocket PC ------
Preparing resources...
Updating references...
Performing main compilation...
Build complete -- 0 errors, 0 warnings
Building satellite assemblies...
Visual Studio is ready to deploy TuneUsingMatsAPI
------ Deploy started: Project: TuneUsingMatsAPI, Configuration: Debug
Pocket PC ------
Deploying to Pocket PC Device using TCP Connect Transport
Connected to Pocket PC Device (Pocket PC) running on ARMV4.
Copying files from 'C:\Documents and Settings\v-tregan\My
Documents\Visual Studio Projects\zcast\TuneUsingMatsAPI\bin\Debug' to
'\Program Files\TuneUsingMatsAPI'
Copying TuneUsingMatsAPI.exe
---------------------- Done ----------------------
Build: 1 succeeded, 0 failed, 0 skipped
Deploy: 1 succeeded, 0 failed, 0 skipped
Launching Application
Error while trying to run project: Unable to start debugging.
Unable to start program 'C:\Documents and Settings\v-tregan\My
Documents\Visual Studio
Projects\zcast\TuneUsingMatsAPI\bin\Debug\TuneUsingMatsAPI.exe'.
The application starts without problem if I start it on the device. At
first I thought it was one iPaq, because one would fail while the
other worked. Then they both started failing so I did a factory reset
on one of the iPaqs. This did not fix it! That suggested it was the
project settings so I tried a new wizard-built 'hallo world' project.
But that failed too.
Throughout this the projects built using eMbedded Visual C++ 4 have
deployed and run from the IDE onto the device without trouble.
What's going on and how do I fix it? I'm reduced to doing all my
debugging in the app not the IDE which is painful.
Cheers,
Tim.