Official support for Windows Phone 7 Series

Mar 28, 2010 at 11:42 AM

Given the emphasis of both MEF and Windows Phone 7 Series at MIX two weeks ago, it seems clear that Microsoft is pushing both technologies hard. This is great, and to my mind WP7 would benefit greatly from an officially supported version of MEF (plug in features, shared UI components, trial vs full versions etc.)

Does anybody know if an official Windows Phone 7 port is in the pipeline?

May 31, 2010 at 3:25 PM

"Does anybody know if an official Windows Phone 7 port is in the pipeline?"

May 31, 2010 at 3:44 PM

Silverlight is the platform for Windows Phone 7 development. MEF is already part of Silverlight 4

May 31, 2010 at 4:08 PM

Somewhat misleading as System.ComponentModel.* is not available in Windows Phone 7 applications. 

I ask because I'm somewhat stalled on my http://EHR.CodePlex.com project; it is a multi-targeted (multiple platforms sharing the same code).   If PRISM goes MEF and MEF doesn't go WP7 then I'll be in somewhat of a pickle.   I ported PRISM to WP7 using the ContainerModel (I emulate Unity using the http://Mobile.CodePlex.com DI Container).   

If MEF does go WP7 then it obviously becomes the choice of preference for this multi-targeted framework.

May 31, 2010 at 7:33 PM
Prism will still allow you to use other containers. Hard dependencies on MEF are not currently planned.

As far as MEF in Windows Phone, we are working on it,

Sent from my IPad.

On May 31, 2010, at 8:09 AM, "BillKrat" <notifications@codeplex.com> wrote:

From: BillKrat

Somewhat misleading as System.ComponentModel.* is not available in Windows Phone 7 applications.

I ask because I'm somewhat stalled on my http://EHR.CodePlex.com project; it is a multi-targeted (multiple platforms sharing the same code). If PRISM goes MEF and MEF doesn't go WP7 then I'll be in somewhat of a pickle. I ported PRISM to WP7 using the ContainerModel (I emulate Unity using the http://Mobile.CodePlex.com DI Container).

If MEF does go WP7 then it obviously becomes the choice of preference for this multi-targeted framework.

Jun 1, 2010 at 10:07 AM
Edited Jun 1, 2010 at 11:23 AM
BillKrat wrote:

Somewhat misleading as System.ComponentModel.* is not available in Windows Phone 7 applications. 

Really? Interesting. In that case I have been mislead by this incorrect information in a Visual Studio magazine article about Silverlight 4 RC (emphasis mine):

"This isn't Silverlight-lite, this isn't Silverlight different, this is Silverlight," said Scott Guthrie, corporate vice president of Microsoft's Developer Division, during the keynote. Developers can use the same programming skills (C#) and tools to create event-driven applications for the Windows Phone OS 7.0.

Jun 1, 2010 at 3:38 PM
gblock wrote:
Prism will still allow you to use other containers. Hard dependencies on MEF are not currently planned.
As far as MEF in Windows Phone, we are working on it,

Thanks - this will help in planning. 

Jun 1, 2010 at 4:24 PM

wcoenen

It is Silverlight, just a different version, SL3 :-) And there are some differences like not having IQueryable support and not supporting Reflection.Emit.