View Single Post
  #1140 (permalink)  
Old 03-04-2009, 11:32 PM
jucytec's Avatar
jucytec
Regular 'Geeker
Offline
Location: Princeton
 
Join Date: Jan 2009
Posts: 438
Reputation: 1220
jucytec is halfway to VIP status based on repjucytec is halfway to VIP status based on repjucytec is halfway to VIP status based on repjucytec is halfway to VIP status based on repjucytec is halfway to VIP status based on repjucytec is halfway to VIP status based on repjucytec is halfway to VIP status based on repjucytec is halfway to VIP status based on repjucytec is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: *21 Feb* UPD 15: SSK 1.5M *8* OS Kitchen inc WM6.5 Build 21159 and OS 21015 ROM -

Quote:
Originally Posted by zim2323 View Post
You gave an "answer" and asked a question that had nothing to do with my question.

What I'm trying to accomplish is just what I said the first time. I want to create a VIRTUAL environment to test in rather than reflashing the phone to test for each change. I've actually got the 6.1.4 SDK installed and testing SEVEN application with it right now. I can "hot dock" the virtual device and play DIRECTLY with it without screwing up my phone in the mean time.

Neither UC or Sashimi really have anything to do with the question other than this would make testing them easier.

The question wasn't why should I not use virtualization.

The question was and still is, has anybody tried to utilize the Windows Mobile SDK virtualization tools as a testing platform for testing new ROM's?

If was and dropped, what were the reasons? Maybe there are too many limitations on this. The mobile virtualization product that VMWare demo'd at Mobile World Conference really sparked this interest.

Thanks!
I see what you are saying now! LoL I wasn't even close...

But as you already know running an instance of any OS via Virtual PC or VMWare will always have it's limitations. if you were to test you'll simply be emulating the OS through a window, and in Windows Mobile SDK's case, you'll be simply testing just the software side of things... Most of the harware components will be emulated, which may not actually test any hardware components on your windows mobile device.

My company does windows mobile development, and while we do recompile some of the applications to run on x86 Windows platform; we only test the recompiled app to spot out basic usability issues/GUI design issues. Qualifying the actual software has always happened on the device inately.

of course this is only my opinion and means nothing...
__________________