Re: Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
- From: vaisakh p s <VaisakhRulez@xxxxxxxxx>
- Date: Sat, 6 Sep 2008 01:30:27 -0700 (PDT)
yes you seems to be right.
--
regards
Vaisakh P S
Accord Software Systems Pvt. Ltd.
Banagalore
On Sep 6, 9:18 am, Oliver Schenk <oliver.sch...@xxxxxx> wrote:
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
.
- Follow-Ups:
- References:
- Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
- From: Oliver Schenk
- Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
- Prev by Date: ActiveSync & CEDB event database
- Next by Date: Re: Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
- Previous by thread: Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
- Next by thread: Re: Design process using Windows Embedded CE 6.0, VS2005, CoreCon and SDKs
- Index(es):
Relevant Pages
|
Loading