Word Content Control Toolkit

New Post: Unexpected Token - Syntax Error

mrscott — Mon, 06 May 2013 23:43:33 GMT

Hi Danna,

I can have a look. Please send me the document which contains the minimal reproducible issue. Also what version of Word are you using?

Thanks,

Matt

New Post: Unexpected Token - Syntax Error

mrscott — Mon, 06 May 2013 23:43:33 GMT

Hi Danna,

I can have a look. Please send me the document which contains the minimal reproducible issue. Also what version of Word are you using?

Thanks,

Matt

New Post: Unexpected Token - Syntax Error

mrscott — Mon, 06 May 2013 23:43:33 GMT

Hi Danna,

I can have a look. Please send me the document which contains the minimal reproducible issue. Also what version of Word are you using?

Thanks,

Matt

New Post: Unexpected Token - Syntax Error

Danna144 — Mon, 06 May 2013 21:50:20 GMT

Hello,

Total novice here. I have had to make updates to a previously created form. All of the fields work properly until I get to my last field named Job Title. When I try to add this to the edit fields in order to bind it to the next occurence in the Word document I receive an XML syntax error that says I have an unexepected token.

I have used the same method for the Job Title field as I did for all of the other fields in the form and they work just fine. I can't find my error.

Danna

New Post: Unexpected Token - Syntax Error

Danna144 — Mon, 06 May 2013 21:50:20 GMT

New Post: Unexpected Token - Syntax Error

Danna144 — Mon, 06 May 2013 21:50:20 GMT

Created Issue: Reoccurring Data not being saved [33801]

esturner1 — Thu, 21 Feb 2013 20:55:27 GMT

New Post: Fail to open. Object reference not set to an instance of an object.

mrscott — Fri, 08 Feb 2013 00:01:57 GMT

<div> <div style="font-family:Calibri,sans-serif; font-size:11pt">Thank you!<br> <br> Thanks,<br> Matt<br> <br> Sent from my Windows Phone<br> </div> </div> <hr> <span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">From:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">dotsad</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Sent:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">2/8/2013 6:25 AM</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">To:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">Matt Scott</span><br>
<span style="font-family:Tahoma,sans-serif; font-size:10pt; font-weight:bold">Subject:
</span><span style="font-family:Tahoma,sans-serif; font-size:10pt">Re: Fail to open. Object reference not set to an instance of an object. [dbe:243083]</span><br>
<br>
<div> <p>From: dotsad</p> <div id="ThreadNotificationPostBody">I found that "Ink Signature" in my case was a culprit. <br> <br> If you want to ignore "Fail to open. Object reference not set to an instance of an object." and continue WCC load your file edit: <br> <br> file: PkgNavigator.cs <br> line: 266 <br> add: <br> <pre><code> if (prXmlItemProp == null) continue; </code></pre> </div> </div>

New Post: Fail to open. Object reference not set to an instance of an object.

mrscott — Fri, 08 Feb 2013 00:01:57 GMT

New Post: Fail to open. Object reference not set to an instance of an object.

mrscott — Fri, 08 Feb 2013 00:01:57 GMT

New Post: Fail to open. Object reference not set to an instance of an object.

mrscott — Fri, 08 Feb 2013 00:01:57 GMT

New Post: Fail to open. Object reference not set to an instance of an object.

dotsad — Thu, 07 Feb 2013 22:24:46 GMT

I found that "Ink Signature" in my case was a culprit.

If you want to ignore "Fail to open. Object reference not set to an instance of an object." and continue WCC load your file edit:

file: PkgNavigator.cs
line: 266
add:

 if (prXmlItemProp == null)
            continue;

New Post: Fail to open. Object reference not set to an instance of an object.

dotsad — Thu, 07 Feb 2013 22:24:46 GMT

 if (prXmlItemProp == null)
            continue;

New Post: Fail to open. Object reference not set to an instance of an object.

dotsad — Thu, 07 Feb 2013 22:24:46 GMT

 if (prXmlItemProp == null)
            continue;

New Post: Fail to open. Object reference not set to an instance of an object.

dotsad — Thu, 07 Feb 2013 22:24:46 GMT

 if (prXmlItemProp == null)
            continue;

Commented Issue: Rich Text control converted to Plain Text [30128]

yyyexf2 — Tue, 05 Feb 2013 18:43:31 GMT

<p>I insert rich text control in word document and then use the Word Content Control Toolkit to bind it to XML element. After that, when I open the word document again - the control is Plain Text!</p>

Comments: ** Comment from web user: yyyexf2 **

I have the same issue. Did it fix?

Source code checked in, #99885

Project Collection Service Accounts — Mon, 01 Oct 2012 21:24:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #99884

Project Collection Service Accounts — Mon, 01 Oct 2012 21:16:08 GMT

Checked in by server upgrade

New Post: Rich Text Content control turns into a plain text content after association using Word 2007 content control toolkit.

jharrop — Mon, 28 May 2012 04:07:19 GMT

> I am experiencing the same thing in Word 2010. I could make a lot of use out
> of this tool if it would allow Rich Text binding, but without it won't be
> able to use it at all.

As Matt says, you can bind a rich text control. However, you can work
around this to some extent if you are prepared to 'resolve' the
bindings yourself.

I do this by using the content control tag to store the binding
information. See the OpenDoPE conventions web site for details.

New Post: Rich Text Content control turns into a plain text content after association using Word 2007 content control toolkit.

jharrop — Mon, 28 May 2012 04:07:19 GMT