Re: Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs

Thanks for all the replies!

Expanding on my question:

2. When trying to deploy a subproject that is part of an OS design it requires the runtime image to be regenerated and reloaded each time.

Not necessarily. You might not include the output of the subproject in a BIB file and, instead, arrange for the flat release folder to be the load source for that DLL or EXE. In that situation, when the DLL or EXE is to be loaded, and when it's not found built into the OS, the loader will get it from the flat release folder, transporting it over the debug connection to the device being debugged, where it will be loaded.

If I have an OS Design subproject that requires .reg, .db or .dat files does that pretty much mean that I will need to:

1. Build that subproject
2. Make the image
3. Reboot my device and select boot from development pc
4. Attach VS2005 and download image
5. Debug and test

I'm basically trying to find the fastest way to build and debug applications. For example sometimes programs need frequent small tweaks and many rebuild and reloads.

How do people out there achieve this in an efficient manner?

Can I somehow locally test and debug programs first to get most of the errors out?

Can you please provide a link to a place that explains how to "arrange for the flat release folder to be the load source for that DLL or EXE"?


Thanks

Oliver S.
.

Relevant Pages

  • Re: Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
    ... Oliver Schenk wrote: ... You might not include the output of the subproject in a BIB file and, instead, arrange for the flat release folder to be the load source for that DLL or EXE. ... In that situation, when the DLL or EXE is to be loaded, and when it's not found built into the OS, the loader will get it from the flat release folder, transporting it over the debug connection to the device being debugged, where it will be loaded. ... For example sometimes programs need frequent small tweaks and many rebuild and reloads. ...
    (microsoft.public.windowsce.platbuilder)
  • Debug problem
    ... What I find particularly odd is that the exe created by the build seems to ... Debug Problems ... Then I got an idea and moved the exe to another folder on the ... the laptop. ...
    (microsoft.public.vstudio.general)
  • Re: Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
    ... Are you saying that 99% of all things that are not say components for the OS or hardware drivers should be done OUTSIDE of platform builder? ... I'm sure there are certain things that need to be a subproject of the OS design and not an "application". ... "Oliver Schenk" wrote in message ... In that situation, when the DLL or EXE is to be loaded, and when it's not found built into the OS, the loader will get it from the flat release folder, transporting it over the debug connection to the device being debugged, where it will be loaded. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: .exe debug without sources from Visual Studio 2005
    ... >running WM 2003 SE using eVC 4.0 debugger with no problem. ... >that I want to debug that exe on another target device running Windows ... debugging unless the platform specified in the IDE matches the actual ...
    (microsoft.public.windowsce.embedded)
  • Re: properly disposing of filestream
    ... Try to use the release version of the EXE for the one app, and debug from VS the another instance. ... "The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it" Michelangelo ...
    (microsoft.public.dotnet.languages.csharp)
Loading