Member Avatar for jbennet

Ok i need a pocketpc app for some project work but ive had to made the app as if it were a windows forms app though (as i have only standard edition) could someone with VS.NET pro 2003/2005 and the pocketpc 2003 SDK please modify and compile for me please :)

  • 3 Contributors
  • 5 Replies
  • 109 Views
  • 22 Hours Discussion Span
  • Latest Post Latest Post by Ancient Dragon

Dani AI

Generated

A compact checklist and troubleshooting guide for turning a desktop WinForms app into a Pocket PC 2003 build and producing an installable CAB. This picks up from the thread and is intended to help whoever ends up compiling the project (for example ) or anyone following along later.

Create a Smart Device project that targets the Pocket PC 2003 SDK and the correct .NET Compact Framework version for the target device. Do not simply copy the desktop designer files — create the forms in the CF designer and move logic/event handlers into them. Separate UI code from business logic so the latter can remain shared between desktop and device builds. Replace desktop-only APIs and controls with CF-compatible alternatives; watch for missing namespaces, large bitmaps, unsupported controls and limited System.Drawing functionality.

Key steps to hand to a compiler or follow yourself:

  • Provide the full solution and project files plus source (.sln, .cs/.vb, .resx).
  • State the target .NET CF version and the device/emulator resolution.
  • List every third-party and native dependency; include ARM builds for any unmanaged DLLs.
  • Build and test on the emulator first, then on a real device.
  • Create a Smart Device CAB Project in Visual Studio and include project output and prerequisites (only add the CF redistributable if the device lacks it).

A small conditional-compilation pattern that helps keep shared codebases manageable:

#if COMPACT_FRAMEWORK
// compact-framework specific code
#else
// desktop-specific code
#endif

Common failures and quick fixes: "Type or namespace not found" usually means a missing or unsupported reference; designer errors often mean controls used on desktop are not in CF — recreate those forms in the CF designer; deployment errors typically come from wrong CPU/native DLLs or a missing CF runtime. Keep resources small and avoid unmanaged code unless properly built for the device architecture.

Recommended Answers

All 5 Replies

Member Avatar for Nick Evan

Send me a link and I'll see what I can do

p.s. You could download VS2005 pro yourself from microsoft.com, it's a 90 day trail

Member Avatar for Ancient Dragon

Send me a link and I'll see what I can do

p.s. You could download VS2005 pro yourself from microsoft.com, it's a 90 day trail

The free express edition will not compile for wireless smart devices.

Member Avatar for Nick Evan

The free express edition will not compile for wireless smart devices.

I know....
that's why I said:

p.s. You could download VS2005 pro yourself from microsoft.com, it's a 90 day trail

:p

Regards, Niek

Member Avatar for jbennet

ive got the trial thanks, runs good

Member Avatar for Ancient Dragon

I know....
that's why I said:

:p

Regards, Niek

Oops!:o

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.