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.

C# 100.00%

open-xml-package-editor-power-tool-for-visual-studio's Introduction

Open XML Package Editor Power Tool for Visual Studio

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, PowerPoint and Visio documents. This Power Tool enables you to do the following tasks:

Open any Open XML Package file or XPS Package file directly in Visual Studio 2010SP1/2012/2013/2015
Browse the contents of Package files in a tree view
Open any XML part directly in Visual Studio's rich XML editor
Add or remove parts and relationships directly in the user interface
Import and export part contents to and from files
Detect when a Package file that is opened in Visual Studio is modified externally. The Power Tool prompts the user to reload the file without having to close any open XML part editors
Create new Office Packages from a set of templates using Visual Studio's File > New dialog

The project is designed to be edited in VS2010SP1, but can be one-way converted to VS2012, VS2013 or 2015.

To compile this Visual Studio add-on you need the [SDK for Visual Studio 2010 SP1] (http://www.microsoft.com/en-us/download/details.aspx?id=21835). If you are getting mysterious errors about loading the csproj, you most likely haven't installed the SDK.

The compiled version of this Power Tool is available for [download on the Visual Studio Gallery] (http://visualstudiogallery.msdn.microsoft.com/450a00e3-5a7d-4776-be2c-8aa8cec2a75b) - please note that currently downloadable VSIX version does not support VS2015; update is in progress.

This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

open-xml-package-editor-power-tool-for-visual-studio's People

Contributors

Stargazers

Watchers

open-xml-package-editor-power-tool-for-visual-studio's Issues

Remove theRsidR Property

I hope the issue tracker is an OK place to ask questions.

I'd like to ask where in the repository lies the code that adds the RsidR attributes to the <w:p> tags for .docx word documents. I'd like to fork the code to be able to eliminate these (along with other tags).

Parsing package

Desktop DPI scaling

It seems the extension does not support desktop scaling, the texts are tiny compared to the rest of Visual Studio

VS2015 extension is missing

Although it seems someone else has created a binary

http://blogs.msdn.com/b/maheshk/archive/2015/11/14/open-xml-package-editor-for-visual-studio-2015.aspx

Default editor

In VS 2019, double-clicking a Word file in a project opens the Package File editor even if it's not the default editor. To reproduce, right-click a Word document and select Open With.... Then select Word in the list and click the Set as Default button. Then click OK. Double-click a Word document and see that it's opened not in Word, but in the Package File editor. This worked correctly in VS 2017

Add option to pretty-print when XML part is opened

Equivalent of Edit..Advanced..Format Document in VS.

VS 2017 for Mac

OSX user here, would love to see support for visual studio for mac.

VS 2017 Extension

Is there any extension for Visual Studio 2017?

Installation error when installing with Visual Studio Code

When trying to install the extension using visual studio code, it comes up with an error "extension/ package.json not found inside zip"

Is there another build for visual studio code?

XML not Validating

Should start by saying this is a FABULOUS tool, and thank you! This issue could be my lack of knowledge of VS2012 so please bear with me.

When editing a Word template (dotm file) the XML doesn't seem to be validating. A case in point is a duplicate id attribute value on 2 different buttons. While editing the XML in the package VS doesn't flag that as a problem.

But, if I create a new XML file in VS and copy and paste the entirety of my customUI.xml file VS flags that problem, even though it's all the exact same code.

Is there something I need to do in VS to get the validation working when editing the package?

Thanks again!
Ken

Wrong Program Files

When installing the vsix the files are installed in "C:\Program Files (x86)" but when loading an OpenXml document in Visual Studio it tries to load the tool from "C:\Program Files"

VS2015 Support

The Open XML Package Editor for Visual Studio extension is not currently compatible with VS2015. What are the plans for adding VS2015 support?

officedev / open-xml-package-editor-power-tool-for-visual-studio Goto Github PK

open-xml-package-editor-power-tool-for-visual-studio's Introduction

Open XML Package Editor Power Tool for Visual Studio

open-xml-package-editor-power-tool-for-visual-studio's People

Contributors

Stargazers

Watchers

Forkers

open-xml-package-editor-power-tool-for-visual-studio's Issues

Recommend Projects

Recommend Topics

Recommend Org