Security difference between InfoPath 2007 and 2003 with code behind - InfoPath Dev
in

InfoPath Dev

Security difference between InfoPath 2007 and 2003 with code behind

Last post 12-02-2008 04:31 PM by Greg S. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 11-26-2008 10:05 AM

    • Greg S
    • Not Ranked
    • Joined on 10-15-2006
    • Posts 9

    Security difference between InfoPath 2007 and 2003 with code behind

    I'm upgrading a form from InfoPath 2003 to 2007 and adding new functionality.  The form uses C# code behind, and I'm currently using VS 2008.  The form has to run with Domain security. It cannot run with Full Trust

    When pulling values from datasources in 2003, this worked code worked fine:

    thisXDocument.DOM.selectSingleNode("/my:myFields/my:message").text

    However when I try this in 2007: 

    MainDataSource.CreateNavigator().SelectSingleNode("/my:myFields/my:message", NamespaceManager).Value

    I'm getting a security error.  I can get it to work in preview mode only when setting the security to Full Trust, but this is not an option in production.

    Am I missing something?  I can't imagine that InfoPath 2007 requires full trust just to pull values from the form's DOM.

  • 11-26-2008 11:40 PM In reply to

    Re: Security difference between InfoPath 2007 and 2003 with code behind

    Hi,

    InfoPath 2007 does not require full trust to pull the values from the form’s DOM. Can you give me message that you are getting when you are trying to pull the data from IP form without making the form full trust. So that I can help you.

    Chandrakanth/GGKTech
  • 12-02-2008 04:31 PM In reply to

    • Greg S
    • Not Ranked
    • Joined on 10-15-2006
    • Posts 9

    Re: Security difference between InfoPath 2007 and 2003 with code behind

    OK, I'm going crazy. I went back to my app and the very code I posted above is now working.  No clue what's different from last week.

     Thanks for the response.

Page 1 of 1 (3 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.