Michael Bowen comments

Results 82 comments of


                                            Michael Bowen

Macro-enabled document created with CreateFromTemplate() cannot be opened by Word

Thanks for sending the files from your case. I'm seeing the same issue you, are and I also don't receive an errors, the file just doesn't open. I will try...

OpenXmlValidator.Validate() returns error for valid presentation

I looked into this some and there is definitely, something incorrect happening here. The validator is just not seeing the data correctly; showDLblsOverMax does not have any children, the ext...

ExternalRelationships missing Word Docs from results

Hi @rjgoodman , Can you share the .docx file with the links?

Add API to determine if a child is valid for a given element

@cwensley , Thanks for the suggestion. I've added the enhancement request label to your post. If you have time, pull requests are always appreciated.

Add API to determine if a child is valid for a given element

Adding them to OpenXmlElement, seems reasonable to me. What do you think @twsouthwick & @tomjebo ?

Can you please help me with proof keys implementation

Can you point to which section of the code you're referring?

Can you please help me with proof keys implementation

Hi @priyanshumaurya007, I realized you're referring to the proof keys. Unfortunately, it's commented out, because I haven't completed the implementation. Part of the difficulty is that the wopi-validator-core test for...

Make the project run locally but it failed

It's hard to tell what's wrong from that error message. How are you running the server? What is the response to the hosting discovery (`/hosting/discovery`) ?

Investigate changing extensionlist/extension mechanism naming to more closely match Office use

We tried that. If we only have the specialized type then the child of the `ExtensionList` is a `TableColumnExtension` and if you try ```csharp DocumentFormat.OpenXml.Spreadsheet.Extension e1 = tc.ExtensionList.GetFirstChild(); ``` Then...

Investigate changing extensionlist/extension mechanism naming to more closely match Office use

> Is that a problem? Given the details in the original message, it's the same type, just specialized now, right? Yes unfortunately, becuase if someone had used the original API...