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

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"

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

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).

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?

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

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

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

Is there any extension for Visual Studio 2017?

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

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

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

       <p188:extLst>
            <p:ext xmlns:p="http://schemas.openxmlformats.org/presentationml/2006/main" uri="{5BB2D875-25FF-4072-B9AC-8F64D62656EB}">
                <p228:taskDetails xmlns:p228="http://schemas.microsoft.com/office/powerpoint/2022/08/main">
                    <p228:history>
                        <p228:event time="2024-07-16T05:56:24.928" id="{22A90AAB-29DC-4F45-80B8-41660EB3CE91}">
                            <p228:atrbtn authorId="{DDBD2B34-3E97-38F7-B7A9-5BD8D52D7288}"/>
                            <p228:anchr>
                                <p228:comment id="{C5BB4569-00FC-429B-B44C-282847B06E34}"/>
                            </p228:anchr>
                            <p228:add/>

In part \ppt\comment\modernComment... part is coded in the SDK metadata as p188:ext. This causes OpenXmlUnknownElement to be assigned as the child of p188:extLst.

This should be fixed on our schema processor.