View Single Post
  #1130 (permalink)  
Old 03-04-2009, 02:04 PM
zim2323's Avatar
zim2323
Regular 'Geeker
Offline
 
Join Date: Feb 2009
Posts: 263
Reputation: 210
zim2323 is keeping up the good workzim2323 is keeping up the good workzim2323 is keeping up the good work
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 jucytec View Post
I'm uncertain what you are trying to test... I've also served in the IT realm for 4 years a while back.

UC script is dead simple, as it only has a number of commands that it can execute. XMLs are required for provisioning registry settings.

Sashimi is even simpler as it only requires you to store Cabs, and Regs into a specific folder in your SD card for auto or manual execution.

In terms of Mail Account setups, Exchange/IMAP4/POP3, they are all provisioned from a single or multiple XMLs.

Of course regular rule for a Valid XML schema must be followed including omitting the usage of special characters and replacing them with XML equivalent. Such as & = &

Sashimi allows you to run anytime you'd like, while UC is ran after the Initial boot of a ROM Flash. The downside to UC especially when using ROMs that has Autocalibrate scripts... You will not be able to use your touch screen to click OK on messages that pop up. You can HIDE the UC window and UNLOCK the screen, but you'll need to use the Dpad to interact with any popup windows.

Let me know if this answers your question.
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!