View Single Post
  #1134 (permalink)  
Old 03-04-2009, 05:07 PM
DigitalAttic's Avatar
DigitalAttic
Regular 'Geeker
Offline
Location: Dark Side of the Moo...
 
Join Date: Feb 2008
Posts: 335
Reputation: 1255
DigitalAttic is halfway to VIP status based on repDigitalAttic is halfway to VIP status based on repDigitalAttic is halfway to VIP status based on repDigitalAttic is halfway to VIP status based on repDigitalAttic is halfway to VIP status based on repDigitalAttic is halfway to VIP status based on repDigitalAttic is halfway to VIP status based on repDigitalAttic is halfway to VIP status based on repDigitalAttic is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to DigitalAttic Send a message via MSN to DigitalAttic Send a message via Skype™ to DigitalAttic
Lightbulb 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!

From the looks of it, the effort to do what you seek w/the MS Developer Tools is far too complex and time consuming for the average user. If you were interested in developing an application for commercial use, I would say go for it. On the other hand, if you are just a hard-core developer and want something to play with, go for it too. But my take on this is that it is not at all intended to be a test-bed platform in the way that flashing and UC/Sashimi provide. This is a tool for testing WM applications in a development environment.

Now VMware's MV is a very interesting piece of software, a mobile phone hypervisor. But the description they give isn't clear on whether a WM VM can be made using it, though it is alluded to; and that is basically-- IMHO-- what you are looking for, and that would be great to test with.

I have been using a set of tools to abstract the application and settings space from the WM OS so I can redeploy effortlessly to new WM ROMs: PM me if you are interested.

One last thing on WM Virtual.: I noticed Android was absent from the list of supported OS'es... hmmm.

TC - DA
__________________


If my post helps you, please hit the "Thanks" button... it's free and I need the rep!
This post has been thanked 1 times.