Restore Silverlight support about prism

[bartlannoeye]

If I remember correctly, the Async nuget package changes the msbuild files. Personally I'd like to keep that out of the general Prism PCL used by all environments (and limit only to SL). Some of our team members have had issues with it in the past.

Are there any alternative approaches we could consider?

[brianlagunas]

The effort to do this and support SL may not be worth it. Besides getting the code ported, and all the tests in place we would also have to answer support questions regarding SL. I'm not sure this is something worth the time and effort considering the fate of SL.

If this was to be done, most likely we would use linked files. We would definitely not put in a number of dependencies and new projects just to support SL.

[Mike-E-angelo]

As an aside here, (and from what I understand) linked files are being replaced with Shared Projects (.shproj) going forward. This is something that should be considered for the main Prism solution if possible/needed/encountered. Their support in VS2013 is a little lacking (but accounted for). However, they are getting 1st-class support in VS2015.

As for SL, I personally think it would be cool to see it supported in some fashion, maybe in an unofficial fork somewhere? If there is enough support/energy around it to bring it into the official repo, that would be cool, too. Personally, I have said my goodbyes to SL but a part of me would like to see it continue however possible (I still think SL5 is the best tech MSFT has ever released to date!).

[iskiselev]

I'm not sure what will be better to use - file links or Universal projects. Universal projects is not yet used in Prism - but possible it is a good time to start usage of them.
I've started my fork with example how it may looks - https://github.com/iskiselev/Prism/tree/Silverlight.

[davidezordan]

I agree with Brian about Silverlight support. I don't think it's worth the time and effort for supporting it at this stage.
Silverlight projects should continue to use Prism version 4 imo.

[augustoproiete]

+1 agree with @brianlagunas. Not worth the effort.

[thomashagstrom]

We're using Prism 4 with SL5 without issues

[brianlagunas]

Frankly, this isn't going to happen. As other members have commented, you will have to either create your own port to take advantage of the new Prism 6 features, or continue to use Prism 4.1 for Silverlight projects.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.