OK, I suppose the best course is just to manually manage the projects with a PC and Device folder structure where separate project files are maintained and possibly a common source folder.
But you said one thing that I don't completely understand.
Quote:
|
As I sayed before, any DLL targeting the Compact(ed) FrameWork, WILL run on bothe platforms.
|
Are you saying the that PC and Device DLL are identical? Aren't the architectures of the CPU's different and thus the instruction set and thus the generated code or am I really missing something?
Or are you saying that by targeting .Net CF they are functionally the same, guaranteed not to use incompatible classes, BUT the actual DLL generate code is different and thus there are two DLLs, one for PC and one for device. The only things they share are use of .Net CF, their name, and source.
I had assumed that I had to have two versions of the DLL just like the B4P.exe files.
If they are different then the manual management will be fine.
Hope you have a nice weekend.
Regards,
Jim