Re: Same codebase for Windows CE 6 and desktop (Windows XP)?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Carsten,

"Thomas Steinmaurer" <t.steinmaurer_dontbugmewithspam@xxxxxxxxxxx> schrieb im Newsbeitrag news:etysDxTqJHA.4516@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

we are writing an .NET based application for Windows CE 6. This includes a graphical user interface, reading data from the CAN bus, storing data in SQL CE, ...

The primary target platform is Windows CE 6 with the .NET compact framework, but ideally, the same application should also run on the desktop (Windows XP) under the .NET framework, especially the graphical user interface part for displaying measurement data. Although reading data won't be from the CAN bus then, but from the COM port ...

Basically, are there any ideas, best practices for having one code base and two target platforms (embedded and desktop)? How is that handled in Visual Studio, ...


in my opinion, it is not so difficult to develop a program which runs on both platform with the same case.

At first, you should know that you primary develop for the .Net Compact Framework, which is just a subset of the Desktop-version. Visual Studio handles is as an solution for smart devices.

If you just use 'plain' .Net-code without any platform invokes or stuff like that, you program should run on the desktop without any problems. If you use libraries for a special hardware that it becomes diffifcult.
If you have to use platform invokes, you should try to substitute the Api calls for coredll.dll to Api calls for gdi32.dll or user32.dll, etc.

If you may have any questions, fell free to ask.

In a first step, it's all about basics. For example, from a development environment POV, how can I handle two platforms in Visual Studio? Two projects/solutions including the same source?

Are there any "getting starting guides" for developing for two platforms possibly with the same code base?


Thanks,
Thomas
.

Relevant Pages

  • Re: Same codebase for Windows CE 6 and desktop (Windows XP)?
    ... The primary target platform is Windows CE 6 with the .NET compact ... Although reading data ... won't be from the CAN bus then, but from the COM port ... ...
    (microsoft.public.dotnet.framework.compactframework)
  • Same codebase for Windows CE 6 and desktop (Windows XP)?
    ... This includes a graphical user interface, reading data from the CAN bus, storing data in SQL CE, ... ... The primary target platform is Windows CE 6 with the .NET compact framework, but ideally, the same application should also run on the desktop under the .NET framework, especially the graphical user interface part for displaying measurement data. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: client -server interaction over XML supporting multiple protocols
    ... > analyzing various models to develop the server. ... The Windows WinInet at just the socket layer is also very ... expected to be different for each platform. ... will the XML size constraints significantly hinder the request ...
    (comp.lang.cpp)
  • Re: Any Clojure users here?
    ... Each platform has distinct libraries for things like ... But a CL implementation can (and does, in fact, for certain libraries) ... I later want to port it to Windows and give it a native Windows GUI, ...
    (comp.lang.lisp)
  • Re: It is almost certain now, INTEL will have 64bit x86 !!
    ... >>IA64 boxes, and then support them on the 8086, on to of the original ... Its difficult to see what future the Windows on IPF port has ... Windows on Itanium was always more of a marketing exercise allowing ... But the introduction of Windows on AMD64 and Intels new platform ...
    (comp.os.vms)