How can we improve the Windows dev platform?

Assembly Binding Redirection support

We really need Assembly Binding Redirection (or Publisher Policies) is Windows Phone!!

Lets say you have a library A that the developer strongly signed.

Now let's say you have two other libs, B and C, and both of these depend on A.

If B and C were to be built with different versions of A, how will he use B and C on our projects?

In the .NET Full Framework, we would use a .config file to make Assembly Binding Redirection (normally, we would point all versions of A to its most recent version), but this is not possible right now in Windows Phone... :(

As far as I can now, this affects the whole Silverlight Framework, not just Windows Phone...

16 votes
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Pedro Lamas shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
on the backlog  ·  Cliff Simpkins responded  · 

Thank you for the suggestion. We are not adding this capability in the 8.0 release, but know that it is high on the consideration list for future Windows Phone releases.

Keep those suggestions and votes coming!

1 comment

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Pedro Lamas commented  ·   ·  Flag as inappropriate

    To be more specific with the situation and give you a scenario where this situation happens, just try using RestSharp and RavenDB on the same Windows Phone project!

    You'll quickly realize that they were build upon different Json.net versions (one or the other will start to complain sooner or later...)

    Thus the request for Assembly Binding Redirection!

Feedback and Knowledge Base