views:

180

answers:

1

I wrote an application which automatically generates and updates Word documents.
I store information used to update each document in a CustomXmlPart.

How will this be affected by Microsoft's settlement with i4i?
I have been unable to find technical details about what exactly will be disabled.

Also, if it will be affected, what's the best alternative feature?
All I'm storing is a couple of values.

+1  A: 

You can find more details here. I've had the same issue and because I'm not extensively using CustomXmlParts, but rather just writing/retrieving a few values, went with Custom Document Properties instead. It is somewhat more limited than CustomXmlPart, but did the trick for my purposes.

Otaku
As I understand that blog post, `CustomXmPart` is _not_ affected. **Not Affected** :Word 2007 also added features allowing Content Controls to map to XML data stored in a DOCX or DOCM file (ref: “Mapping Word 2007 Content Controls to Custom XML Using the XML Mapping Object”, http://msdn.microsoft.com/en-us/library/bb510135.aspx). Content Controls and XML data stored within DOCX or DOCM files will not be affected by this change.
SLaks
That's right, that's how I'm reading it as well. I had thought that it would be the CustomXmlPart that was affected, so I made the change to my code to use Custom Properties instead. But it looks like it's the XML Mapping instead.What I'm still not 100% sure on is the code-behind of Content Controls that have data-binding if that will be affected or not.
Otaku
FWIW document properties are limited to 255 bytes/chars. If you need more space you can try document variables. I'm skipping straight from doc props to custom xml since I'm surpassing the size limitation.
DGGenuine
@DGGenuine: thats a good point on the character limitation.
Otaku