Hi Everyone,
Searched everywhere for a clear answer to this questions, can someone please point me in the right direction.
1. Can eVC++ 4 still be used for WinMobile 5 development
I understand that VS2005 is the recommended way, but can programs compiled with eVC++ still run under WM5
2. If aswer to 1. is "YES, programs should run" then is there a document that details possible issues that might be encountered (apart from screen orientation which seems pretty clear).
WinMobile 5.0 Development - Clear answer needed
Hot Topic
- Hide File
- Form.Close does not close form, instead changes from modal to modeless
- Simple way to "make single instance application" with a VB WinCE 5.0 App?
- Problem with GPSAPI
- Incoming call handling on smartphone 2005 emulator
- deployment to mobile device
- What's wrong with my timeSetEvent() call
- Doubt with ActiveSync
- Eureka
- where to get the Intel Pro100 driver for WinCE 5.0?
Smart Device
- ControlBox
- How to retrieve IMEI of pocket pc phone ?
- threading
- Remoting with TcpChannel and Smartphone
- Installer for .net Application
- Data Synchronization between Desktop Application and PocketPC application
- Drawing Graphic Images using .NET CF 2.0
- asp.net control led
- Get ActiveSync IP Address
- Converting Wav files to Mp3
WinMobile 5.0 Development - Clear answer needed
Eric C.
http://blogs.msdn.com/windowsmobile/archive/2005/06/02/424382.aspx
What about Q2 though, is there any issues developers should be aware of if you choose not to develop with VS2005
Crashin
Yes Visual studio 2005 provides very good development environment and tools for developing device application compared to eVC, the connectivity, device emulators, debugging and deployment support is much more better.
For your second question you can look at http://msdn.microsoft.com/library/default.asp url=/library/en-us/dnppcgen/html/med303_msdn_migrate_evc_app_vs2k5.asp for more information of step by stem migration for eVC project to VS 2005.
There are some issues in migration however you can find solutions to those known issue by looking at this forum answered questions or VSD team blogs
http://blogs.msdn.com/vsdteam/archive/2004/07/16/185778.aspx
Thanks,
Gangadhar