dbe Work Item Rss Feed

Commented Feature: CustomXmlPart Incompatible with Microsoft SDK for Open XML Formats

elsawood — Wed, 10 Jun 2009 19:39:44 GMT

In the Content Control Toolkit clicking "Create a new custom XML Part" creates a part with the path "customXml\item1" or similar.

Creating a CustomXmlPart using the Microsoft SDK for Open XML Formats creates a part with the path "customXML\item" or similar. (Note the difference in case)

The effect of this is that custom XML parts added in the tool cannot be manipulated easily using the SDK.

i.e. MainDocumentPart.CustomXmlParts does not return the parts created by the Tool.
Comments: ** Comment from web user: elsawood **

Now I see the part. Please disregard my previous comment.

Commented Feature: CustomXmlPart Incompatible with Microsoft SDK for Open XML Formats

elsawood — Wed, 10 Jun 2009 18:46:13 GMT

The SDK does not list the Custom XML part added with the toolkit when interrogating the document by using the following code:

WordprocessingDocument _report = WordprocessingDocument.Open(reportStream.File, false);
IEnumerable<CustomXmlPart> customXmlparts = _report.MainDocumentPart.CustomXmlParts;

The field customXmlparts does not list the custom XML added with the Toolkit.

Commented Issue: Lost links to content control fields

elsawood — Wed, 10 Jun 2009 17:33:41 GMT

I'm a Word user (not a programmer). I've been using the CCT for Word 2007 to link XML data from about a dozen separate files to several hundred content control fields in a Word 2007 document. I'm running into some bewildering (perhaps buggy?) behavior that seems related to saving the Word document from the CCT. Although the CCT interface still shows all the data links to the various content control fields, when I quit the CCT and open the Word document from Word 2007, only those fields most recently saved from the CCT are filled in. The rest have lost their former content. When I dig down into the XML content fields for the Word document itself (a tedious process!), I see that the links indeed appear to have been lost. My only theory about this at this point is that the tool (although displaying the links correctly in its interface), rewrites the entire Word document with only the newly added XML links, losing all the links added at earlier session(s). I don't know if this is by design, or a bug, or a flaw in the design of the CCT.

Has anyone encountered similar problems? Is there a solution? Workaround? Am I doing something wrong here to cause this? Any help is greatly appreciated.

Thanks,
Comments: ** Comment from web user: elsawood **

I am having the same problem. I have bound this document twice already and the same thing happens. Very few controls remain bound, while the vast majority loose their dataBinding elements. What could be the problem?

Created Issue: Windows OS version support?

BurtHarris — Thu, 26 Feb 2009 18:00:06 GMT

This may be a simply documentation issue. Currently the System Requirements section of the doc only mentions "XP SP2, Vista RC1 or later". I see no reason why this shouldn't include server & Win7 relases.

Closed Issue: Custom XML Parts pane doesn't expand as SplitView increases

mrscott — Fri, 05 Dec 2008 05:55:46 GMT

When you drag the seperator bar of the main SplitView control the Custom XML Parts pane doesn't expand to take up the new space, so you're left with a bind/edit view that's just as narrow and a bunch of empty grey space on the far right hand side.

Created Issue: Custom XML Parts pane doesn't expand as SplitView increases

935main — Mon, 17 Nov 2008 23:47:49 GMT

COMMENTED ISSUE: Lost links to content control fields

mrscott — Fri, 25 Apr 2008 18:59:48 GMT

You raise some good points. But to know for sure if this is a schema issue I would need to test this. I am patiently waiting for the dummy document to minimally repro the issue. If the issue repros without the XML files \ schema that would be optimal, otherwise I would need dummy XML \ schema.

Thanks for your contribution.

COMMENTED ISSUE: Lost links to content control fields

sajeanp — Wed, 16 Apr 2008 00:05:17 GMT

Thanks for getting back to me so quickly. Unfortunately, I can't send you the document in question (proprietary information). I noticed that most of the XML files I was linking to failed to declare a schema. I've been working on fixing this but can't yet tell if this is making any difference in the Word document. Certainly, it hasn't helped the linked data to reappear (but I haven't yet relinked things, saved and then reopened to see if anything works better).

Also, after digging around in the Word ML more, it now appears that I was mistaken about the links being deleted in Word. They do indeed appear to be there, just not displaying their data.

Would lack of a schema cause such behavior? If so, it would help if the tool had a warning message of some kind. Or if the user documentation had some information about troubleshooting.

I'll see if I can figure out how to create a dummy document that displays the same behavior and then send that to you. Would you need the external XML files and schema as well? I don't know how quickly I'll be able to do this, so please be patient! Thanks again.

COMMENTED ISSUE: Lost links to content control fields

mrscott — Fri, 11 Apr 2008 14:08:33 GMT

sajeanp - please upload or send me the document so that I may debug.

CREATED ISSUE: Lost links to content control fields

mrscott — Fri, 11 Apr 2008 14:01:30 GMT

COMMENTED TASK: Quality: Create VS Team Suite Unit Test project -- begin adding tests

mrscott — Fri, 14 Mar 2008 06:13:40 GMT

Add unit tests using Visual Studio team suite functions. Create a seperate project dbe.test and begin adding tests.

Reason: Ass the toolkit grows it'll get harder to ensure quality from regressions, unit tests at different scopes (acceptance / comprenhensive) at the method and class and application scope are now neccessary. This is an investment in long term building and support of this tool.
Comments: ** Comment from web user: mrscott **