I just installed visual studio 2008 pro and following the instruction on MSDN, I am supposed to install DeviceEmulator BSP. But I found out that there is an emulator integrated with VS2008 already and working properly.
So just wondering that since an emulator has been embedded with VS2008 pro already there should be no need to install an extra one?
What about basic window mobile SDK? Do i need install one?
I am new to this area and thanks in advance.
As far as I remember, the simulator is indeed enclosed with VS2008. I think they also ship some WM2003 and WM5.0 ROMs alongside it. You can use those to test, they should automatically be available as debug targets for your application.
You can also move files onto the simulator and "sync" it with your PC by setting ActiveSync to DMA sync connection mode.
It really depends on what your plan on targeting and what you intend to do.
The DeviceEmulator BSP is only for those using Platform Builder to actually generate device OS images. It's highly unlikely you need this (if you did, you'd already know).
Studio ships with a PPC '03 emulator (I think the WinMo 5 stuff was add-on, but honestly it's been a long time since I did a clean install so I don't recall), but if you want to target WinMo 5.0 or WinMo 6.x, then it's nice to install the SDKs for them. They include not just emulators, but also libs, headers and other pieces for features that were introduced in the newer revs of the platform.
So the general answer is that if you install Studio itself, then you have enough to start doing Smart Device development, but depending on what you intend to target, it might be useful to install a few other pieces.
As a last thought, I'd also highly recommend you buy some real iron - even if it's used off of eBay. You'll find that the emulator really sucks for some things, and I've been working with them long enough to just flat out not trust them, so I do 99% of my work on physical hardware. They've gotten a lot better, and for a lot of stuff they work fine, but you'll inevitably run into some weird behavior that you burn days trying to understand only to find out that it doesn't happen on a real device.