Open XML Package Editor Power Tool for Visual Studio 2010

Microsoft Free

This Power Tool is a Visual Studio add-in that provides an easy way to parse and edit Open Packaging Conventions files, including Word, Excel and PowerPoint documents.

Microsoft
(7) Review
Visual Studio
2010
Download (28,142)
6/22/2010
1.0
E-mail Twitter del.icio.us Digg Facebook
Add To Favorites
Description
Reviews (7)
Q and A (6)
Sign in to Write a Review
Sort By:

by z1c0 | July 10 2012

by Dragan Radovac | May 11 2012

This is really cool. I had no idea that I could view Word Documents in this fashion. Great Job !!!

by HerbF | April 11 2012

Great job, this is a must when developing Word or Excel applications with VSTO.

by Barry Postma | October 26 2011

Excellent tool, does exactly what it says on the box.
Indeed, as Eric commented, make sure you close all instances of VS, otherwise (in my case) it'll generate a 'application has stopped responding' when you open an internal XML file.

Also, far more lightweight than the Open XML Productivity Power Tools, that has an advantage of being able to generate code, but you can't edit anything. Compliments!

by Dzmuh | February 15 2011

by Tom Underhill | June 24 2010

This is an awesome tool. Make sure that you are not running Visual Studio 2010 when you install it.

Sign in to Start a Discussion


  • VS 2012 support
    8 Posts | Last Post April 16, 2013
    • Hi, are there any plans to support VS 2012?
    • Good question - why no reply yet? This is an essential tool for Office development.
    • I am also interested to leverage this adding with VS 2012. Any word when the add-in will be available for VS 2012?
    • VS 2012 support?
    • Support for Visual 2012 please.........
    • VS 2012 support please. Will stay with 2010 until this is available for 2012.
    • Yes, a vs 2012 version would be lovely.
    • I do not understand this. Why write a great tool to assist the integration of the new Office format and then not support it????? Is there plans that mean that supporting Open XML would be a waste of time/money for MS? Come on MS. 2012 support please!
  • Mystery extension!
    1 Posts | Last Post January 11, 2012
    • I too am intrigued by how this extension works.  Does not show up in Visual Studio add-ins.
  • Visual Studio extension technologies
    2 Posts | Last Post May 17, 2011
    • I wonder which exactly VS extension technology was used to create this tool? I've checked both Add-In Manager and Extensions Manager in VS after I installed this tool and I don't see it in either location. 
      
      Thank you!
      Konstantin
    • Well, I don't know the exact answer, but it shows up in the "Add or Remove Programs" applet of the Control Panel, so it's a full-blown app; I would guess interfacing via the VS SDK.  
      
  • Changes the .docx (Word) association in TFS
    1 Posts | Last Post May 17, 2011
    • Nice product, but after installing it, when using TFS, when I double-clic (View command) a .docx file in source control, instead of it opening in Word, it opens in a package explorer window.  I've searched for a reasonable solution without success.   Note that the Windwos Explorer association is for .docx still MS Word.
      
      Hi Eric.
      
  • cannot open InfoPath 2010 .XSN file
    2 Posts | Last Post March 14, 2011
    • I thought that a .XSN file was like a .DOCX file (i.e. cabinet/zipped XML), but when I try to open this type of file in VS 2010, InfoPath is launched. The desired behavior is to be able to see/edit the underlying XML just like with DOCX.
      
      1. Can I get this to work some other way?
      2. Do you plan to "fix" this?
      
      Thanks in advance.
      
      
      Regards..RogerW
    • Hi Roger,
      
      I don't believe that XSN files are Open Packaging Convention (OPC) files.
      
      -Eric
  • Make sure you are not running Visual Studio when you install
    3 Posts | Last Post September 06, 2010
    • If Visual Studio 2010 is running when you install, it will not work properly until you exit / restart Visual Studio 2010.
    • I get the same issue of not being able to find the tool in Extension Manager.  I installed it succesfully with Visual Studio not running, but no sign of it in VS.
    • Just open the document (e.g. via File - Open).