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

Note that this particular blog entry is about modifying built-in components
of the OS. This is unrelated to writing applications to run on the device,
generally.

Paul T.

"Oliver Schenk" <oliver.schenk@xxxxxx> wrote in message
news:%23BCfK60EJHA.4488@xxxxxxxxxxxxxxxxxxxxxxx
I may have found a good link:

http://geekswithblogs.net/BruceEitman/archive/2008/06/06/platform-builder-getting-from-bsp-source-code-change-to-test.aspx

Oliver Schenk wrote:
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: Cant Debug COM Interface
    ... that is loading the dll. ... if I specify the second exe as host application I ... When I start to debug the application the DLL ... > Debugging in this configuration is definitely possible. ...
    (microsoft.public.vsnet.debugging)
  • Debug - Stepping through an exe without the source code - any help
    ... I am looking forward to learn how to debug exe or dll files without the ... source codes. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: cant bebug a dll
    ... The problem is that the exe is a just startup program, ... The VC debug tool icon start soon becomes enable ... > the VS7 designer to make the DLL preload ability so blindingly obvious ... > have two different MFC runtimes each believing it has the sole correct ...
    (microsoft.public.vc.mfc)
  • Re: Problem with usage of STL release Dll with debug application
    ... TSGenD.DLL - debug version of TSGen ... Otherwise make sure that a DLL provides _all_ services to allocate, ... >> and in exe there is copy constructor and then dtor is called. ... std::string decides it needs more memory, where will it acquire the memory ...
    (microsoft.public.vc.stl)
  • Re: How to connect to children process
    ... Main problem is amount of manual operations required per debug cycle. ... connection to DLL with debugger takes sensible amount of time and manual ... Is the main problem that the debugger keeps symbols file loaded ... AFAIK that's how VS2003 debugger works, but WinDbg should usually ...
    (microsoft.public.vsnet.debugging)