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!
I'm actually working on getting this out right now but I'm afraid it takes some time to make it through the process of being a signed & approved download. If you're able to compile it yourself, the version on GitHub does already have the 2015 update! https://github.com/OfficeDev/Open-XML-Package-Editor-Power-Tool-for-Visual-Studio
Thanks Chris, Yes - indeed recompiling the code targeting 4.6 solved VS 2015 issue.
Get the uploaded output from here- http://blogs.msdn.com/b/maheshk/archive/2015/11/14/open-xml-package-editor-for-visual-studio-2015.aspx
Open XML Package Editor is a power full tool. I have some clarifications reagrding this Editor control.
1. Shall we able to load html content also to this editor.
2. How can we implement this editor in MVC application(we are using razor as view
Please advise as early as possible.
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!
Hi all - my apologies for the time we've taken on this but, as above, I've just updated the binary to support VS2012 and 2013 and open-sourced the project. Link to GitHub repo is on main download page.
I've tried, but whenever I try to open a docx file, it just comes up in Word. Everything on the "Open with..." menu (except Word) tells me "The file cannot be opened with the selected editor."
Do I need a full-blown VS2010 Pro in order to use this?
Apparently, the tool will work with VS 2012 and 2013, but you have to change some registry keys. Instructions here: http://blogs.msmvps.com/wordmeister/2014/01/31/open-xml-pack-editor-vs2012_2013/
Registry files for 32bits and 64bits for VS 2012 (=11.0 in registry):
Registry files for 64bits for VS 2013 (=12.0 in registry):
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.
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.
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.