Generally I create 2 projects one for desktop and one for CF. The desktop version is a desktop exe that just references CF . Dlls (this is fine).
Obviously you'll need to push your main app into librarys and make your actual . Exe just a very light wrapper (but this is quite nice design anyway) It's not actually running on the CF but the FF so there are a few compatability issues you may notice in a difference of the implementations The other option is to use the debugging option in Visual Studio to "attach to process". That way you can run the app by double clicking and then just attach to that process.
Generally I create 2 projects one for desktop and one for CF. The desktop version is a desktop exe that just references CF . Dlls (this is fine).
Obviously you'll need to push your main app into librarys and make your actual . Exe just a very light wrapper (but this is quite nice design anyway) It's not actually running on the CF but the FF so there are a few compatability issues you may notice in a difference of the implementations. The other option is to use the debugging option in Visual Studio to "attach to process".
That way you can run the app by double clicking and then just attach to that process.
Follow this guide by Daniel Moth to setup a "My Computer" deploy target: "The Moth: Deploy to My Computer" Then choose this as the deploy target for your Smart Device Project and press F5. Try to stay clear of any platform specific modules/methods etc. There are a lot of great blog entries in mr Moth's blog if you are an Compact Framework developer.
I know what you mean regarding slow performance of the emulator when debugging CF apps. Unfortunately, I don't think this is possible out of the box. If you notice, the debugger in VS always checks what is your connected device in order to decide if your app should be deployed or not, depending on whether you have any changes since the last deploy.
If someone wants to debug in something other than the emulator or the device, they should try and put another "emulator" in that list, that maybe it is not the typical emulator, but the desktop itself. Unfortunately, I don't think this is possible. Of course I am ready to be corrected by someone more experienced in CF development.
I would be really interested if such a technique for debugging CF apps, exists!
In that case, I think I'll build a desktop project for debugging. The GUI will most likely be completely self-written with OpenGL. It's just strange because a CF app runs fine on the desktop.
Maybe I should try to attach to a running CF process, even if that's not as cool as direct debugging. – OregonGhost Mar 17 '09 at 13:03 Yes, maybe attaching to a running CF process, would do the trick. If you have any success, please comment about it here?
I interested in this. – Petros Mar 17 '09 at 14:00 Seems to actually work. I tested with a simple CF WinForms app.
Manually attaching is not the most appealing thing, but that it works will certainly help :) – OregonGhost Mar 17 '09 at 14:53.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.