none
Open XML SDK on NuGet? RRS feed

  • Question

  • There is version 2.0 of the SDK on NuGet, but its not clear whether that was published and is maintained by Microsoft. Would it be possible to post the latest version on NuGet?

    Thank you!

    -Michael

    Tuesday, March 5, 2013 5:24 PM

Answers

  • I have forwarded your feedback to product team. The response is positive. You may get Open Xml from Nuget in future. But I don't have schedule information though.

    thanks.


    Forrest Guo | MSDN Community Support | Feedback to manager

    Thursday, March 7, 2013 4:38 AM
    Moderator

All replies

  • Hi Michael,

    Thank you for posting in the MSDN Forum.

    I'll consult your issue with my colleague. You'll be informed if there's any update.

    Thank you for your patience and understanding.

    Best regards,


    Quist Zhang [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, March 6, 2013 6:19 AM
    Moderator
  • The DocumentFormat.OpenXml on NuGet is not published by Microsoft. Microsoft publishes the SDK over MSDN, it will confuse developers if there're two places where they can download the SDK.

    http://www.microsoft.com/en-us/download/details.aspx?id=5124


    Forrest Guo | MSDN Community Support | Feedback to manager

    Wednesday, March 6, 2013 8:26 AM
    Moderator
  • The DocumentFormat.OpenXml on NuGet is not published by Microsoft. Microsoft publishes the SDK over MSDN, it will confuse developers if there're two places where they can download the SDK.

    Forrest, respectfully, I have to disagree. There are a number of teams inside and outside Microsoft that make their artifacts available through multiple channels, including NuGet. Just have a look at DevDiv, and the ASP.NET team. You can get components of the platform as part of VS, via MS downloads, via the Web Platform Installer, and via NuGet. All these choices don't lead to confusion, they simply allow people to get at the bits they need in the manner most convenient to them.

    -Michael

    Wednesday, March 6, 2013 4:52 PM
  • I have forwarded your feedback to product team. The response is positive. You may get Open Xml from Nuget in future. But I don't have schedule information though.

    thanks.


    Forrest Guo | MSDN Community Support | Feedback to manager

    Thursday, March 7, 2013 4:38 AM
    Moderator
  • To suggest that developers are so stupid that they will be confused by the existence of both an SDK and a NuGet package is insulting. If you really believe your customers are going to have a hard time grasping this sort of thing, how on earth do you think they'll cope with something as complex as the Open XML document formats?

    Moreover, you're ignoring the evidence that thousands of developers are perfectly capable of comprehending this sort of arrangement with other Microsoft libraries.

    For example, take the Reactive Extensions for .NET. Microsoft has made official versions of this available since v1.0 via NuGet: http://www.nuget.org/packages/Rx-Main and up to v2.0 they made an SDK available too: http://www.microsoft.com/en-us/download/details.aspx?id=30708 If you wanted documentation and samples, you'd download the SDK, but if you merely wanted to be able to build code that depends on Rx, you only need the NuGet package. (As of v2.1, there's no longer an SDK release, but there are still two release channels: the source at https://rx.codeplex.com/ is now the official way to get documentation and samples; if you just want the binaries and accompanying XML doc files for IntelliSense, you use NuGet.)

    There are good reasons for having two separate channels: an SDK will often include additional material such as documentation and samples, which you won't necessarily want to install on all machines that will need to be able to build your project. (It's a pain in the neck having to install an SDK on a build server. It may not even be possible - if you're using Microsoft's hosted TFS services, they don't let you install whatever you like on those servers.)

    Perhaps more importantly, with NuGet it becomes much easier to distribute new code that depends on existing code. If there were an official OpenXML NuGet package, I could publish my own NuGet packages that express a dependency on OpenXML. But with things as they stand, that's just not possible. The absence of an official OpenXML Nuget package acts as a brake on adoption.

    Thursday, September 26, 2013 8:22 AM
  • Hi Ian,

    I agree with you and it's a good user scenario of publishing to Nuget. Just now, I checked the OpenXml SDK 2.5, it's alreay published on Nuget: https://www.nuget.org/packages/DocumentFormat.OpenXml/2.5

    Nuget is definitely a popular and useful platform of publishing, distributing software. The fact that OpenXml 2.5 getting on Nuget supports that. Kindly be noted that, the timing of my reply above, it's not to explain Microsoft won't publish it.

    best regards,

    Forrest


    Remember to mark reply as answer if it answers the question.

    Thursday, September 26, 2013 9:21 AM
    Moderator
  • It's been over two years since this question was asked. The unofficial NuGet package has over half a million downloads. When is Microsoft going to officially release OpenXML library on NuGet?
    Friday, October 23, 2015 9:12 PM
  • Microsoft has made the Open XML SDK open source on GitHub:
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/42380725-dbb3-49ee-96d5-f4dde3e258f3/getting-randomly-selected-table-cells-in-word-document?forum=vsto

    Cindy Meister, Office Developer/Word MVP, <a href="http://blogs.msmvps.com/wordmeister"> my blog</a>

    Sunday, October 25, 2015 6:03 PM
    Moderator
  • https://github.com/officedev/open-xml-sdk

    Monday, October 26, 2015 1:54 AM
    Moderator