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