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

I have been spending quite a bit of time recently trying to get my head around just using VS2005 with Platform Builder and everything that goes with WinCE6. Many things I have learned so far are from trial and error, by reading blogs and MSDN.

I would like someone to verify the statements that I am going to make here. They are a reflection of what I currently understand of development for WinCE6.0.


1. Development with Windows CE 6.0 comes in two parts.

a. OS design
b. Application design


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.


3. When debugging an OS Design the debugger can only be attached during bootup when the new runtime image is downloaded.


4. A runtime image loaded via VS2005 is not permanent.


5. The Tools > "Connect to Device ..." menu option in VS2005 is only available in application design solutions and not in OS design solutions.


6. KITL is used when debugging projects in the OS Design phase.


7. CoreCon is used when debugging projects (managed and unmanaged) in the application phase (once the SDK for the OS design has been installed).


8. For WinCE6.0 to work with my eBox 4300 I need to install the BSP msi on my PC so that VS2005 can include the eBox third party drivers, etc...


9. The eBox 4300 comes with an SDK that I can install but if I modify the OS design I need to create my own SDK.


Hopefully someone can verify that I am indeed on the right track here!


Regards,

Oliver


.

Relevant Pages

  • Re: Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
    ... Application design ... KITL is used when debugging projects in the OS Design phase. ... the application phase (once the SDK for the OS design has been installed).. ... on my PC so that VS2005 can include the eBox third party drivers, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: html changes not showing
    ... Tried to install firefox, can't seem to get to go. ... When I came back most of the images had loaded but not all. ... Also don't forget to run the design checker tool. ...
    (microsoft.public.publisher.webdesign)
  • Re: Installing applications for all users
    ... Is there a way to force the application to install for use by all users? ... Not if that program's developers didn't design it to properly recognize multi-user operating systems. ... Quite simply, the application doesn't "know" how to handle individual user profiles with differing security permissions levels, or the application is designed to make to make changes to "off-limits" sections of the Windows registry or protected Windows system folders. ... limited accounts, you can fix it to allow limited users to access the ...
    (microsoft.public.windowsxp.general)
  • Re: Store returns
    ... Especially galling to manufacturers is that many returns are ... The install procedure was barely documented ... because the mfgr cut corners in the design ... who outsourced tech support to get a large bonus for looking good. ...
    (misc.consumers)
  • Re: For the morons
    ... Some more than others sure, but it's a given, and if there is no provision to handle that given, then there is a design or UI issue. ... This person goofed up an NT box pretty badly trying to install ... some ActiveX and they have screwed the registry etc. ... When a single user can cause trouble on the whole system, it's a bit like writing code without a debugger, and where every bug you make could force a reboot or a reinstall. ...
    (borland.public.delphi.non-technical)