Freigeben über

Portable Library Tools Release

  • Artikel

We just released the official version of the Portable Library Tools. The set of tools and updates to .net platform allow you to create dlls that can be used in .NET Framework, Silverlight, Windows Phone, and XBOX projects. You can download the tools here and read more about them on MSDN.



Comments

  • Anonymous
    June 15, 2011
    The comment has been removed

  • Anonymous
    June 16, 2011
    Gutemberg, INotifyPropertyChange is threre. Indeed the ObservableCollection is not; we are trying to add it to the next release (no promisses though).

  • Anonymous
    June 16, 2011
    Hi, Can you elaborate why ICustomAttributeProvider was removed in the official release? Regards, sdobrev

  • Anonymous
    June 17, 2011
    Thanks a lot for this library, it is just what I need to avoid to be maintaining multiple projects at the same time for the same source files. Do you think it will be possible System.Diagnostics.StackTrace class could be available on the next release? Regards!

  • Anonymous
    June 17, 2011
    I agree with with Gutemberg Ribeiro, ObservableCollection it is a must for us.

  • Anonymous
    June 17, 2011
    The comment has been removed

  • Anonymous
    June 17, 2011
    I see your point about ICustomAttributeProvider. The problem is that there are existing APIs that depend on this interface and are part of the portable tools. For example our particular issue is ServiceKnownTypeAttribute which contract requires the method that you specify to take a single parameter of type ICustomAttributeProvider. This is kind of breaking for our scenario and we reverted to the release candidate of the tools. Regards, sdobrev

  • Anonymous
    June 29, 2011
    Good to hear! Though not having ObservableCollection  in the package makes the whole thing not very usable :(

  • Anonymous
    February 14, 2012
    Can you please explain why a simple .Net library that doesn't reference any other libraries (except the implicit mscorlib reference) is not portable? Why do we have to use the Portable Library Tools to get any portability even in the most simple and "pure" cases?

  • Anonymous
    February 15, 2012
    Different .NET redists (Silverlight, .NET Framework, Windows Phone) have different features available in their corresponding mscorlibs. The portable library project ensures that you can call only features that are available in all portability targets.

  • Anonymous
    March 19, 2012
    The comment has been removed

  • Anonymous
    March 23, 2012
    Hi Adrian. I asked Dave to reply to the original msdn thread, which he did. Thanks for the feedback.