SignTool reported an error 'XmlResolver can be set only by fully trusted code.

Hot Topic

Balloon tips on VB .Net
RegionMaster C# to VB.NET References
Datagrid features/limitations
passing variables to form
Progress Bar will not update (visual J#)
How to make two Message Queues communicate
Problem with interface of the application (red crosses?)
PocketVision fix...
Gridview
Sample Code: TreeGridView - collapsing/expanding DataGridView

Windows Forms

Visual Basic .NET 2003 Drawing Applications
toolStripComboBox to fill the toolsstrip
Cannot modify DataGridView properties in inherited control
Form Border Flicker
Status bar statusStrip bug ?
Changing backcolor for a single cell in datagriview
listbox item refresh
Horizontal Scrollbar does not activate
How to scale text using Textrenderer?
Hiding an Application title bar using VB program ....

SignTool reported an error 'XmlResolver can be set only by fully trusted code.

Hi all,

Everytime i publish my winform app, I encounter this error.

"SignTool reported an error 'XmlResolver can be set only by fully trusted code."

How can I fix this problem.

Thanks

Answer this question

SignTool reported an error 'XmlResolver can be set only by fully trusted code.

  • andre_durand

    what is the .sin. where is it located

  • Chinese KongFu

    Tried this but I am am still getting the error.

  • Markx3

    Thank you thank you thank you!

    I've tried deleting the .sln, and editing it to leave only the bare minimum. Sometimes it worked, sometimes it didn't. Clearing all the open solution items and the toolbox works like a charm. Happy days.

  • nimi

    Me too.

    Delete the ".sln" can resolve temparely,but next time if we copy source to another PC,it comes again.

    Faint~

  • simonw.

    I remember I have to exit VS itself,delete .sln and re-open the representative project again,no only close the solution ...tired~

  • Thawani

    I had this problem on my work PC, but not my laptop. After installing the VS2005 SP1 the problem did not go away. Then I had a look at VS Add-in Manager. I had XSDObjectGen in the list but it was not loaded.

    As a last desperate attempt I uninstalled XSDObjectGen and I finally had SUCCESS.

    So just having XSDObjectGen installed on your machine can cause the dreaded XmlResolver error during ClickOnce publishing.

    I hope that helps.

  • DougP

    Daniel R. Tarsky wrote:

    I've tried deleting the .sln, and editing it to leave only the bare minimum. Sometimes it worked, sometimes it didn't. Clearing all the open solution items and the toolbox works like a charm.

    I don't understand your too much. What is "Clearing all the open solution" mean and "the toolbox works "---which "toolbox"


  • Jon Peltier

    I will see what I can find Monday AM and reply with that info.

    It does sound like there may be some issue with project portability here and possibly changing from one certificate/signing key to another. Have also seen similar reports of deleting the .sln file and resaving - which seem to correct the issue.

    Again, will see what I can find out...

    -Robert Schoen (Microsoft Visual Basic QA)

  • ThirtySix Software

    I am getting this as well, and the VS IDE gives no indication of where this is coming from [the Output pane doesn't mention it].

  • satya31237

    I was receiving the two exact error messages listed in the kb article: http://support.microsoft.com/kb/919472. For whatever reason, I only received these when trying to publish a ClickOnce app on a branch that had been freshly created. I did not have XSDObjectGen listed as an installed Add-In. After obtaining the hotfix, problem was solved.

  • techmanblues

    Sorry, followed instructions and tried again and was able to publish application. Thanks.

  • wiro

    big t - What instructions did you follow that worked for you

    Also, the ".sin" that you asked about I think was really the ".SLN" file...which should be located next to your project file...

    -Robert Schoen (Microsoft Visual Basic QA)

  • Kunjal Karamshi

    Okay,

    looking into this further and talking with some our our Publishing folks - this is a known issue...and is being addressed in some fashion within VS....

    The basic problem is caused by having assemblies that aren’t full trust loaded into Visual Studio while trying to publish. My understanding there are some scenarios where just having the toolbox loaded which will load some assemblies (non-full trust ) within the VS system can cause this...

    What you can do that should help is to do the following - before publishing after make changes in the designer or what ever - be sure you have all designers closed.

    You might even try for example to do the following:

    1. Close all designers surfaces so you have an empty environment (maybe even close the toolbox)

    2. Close your solution ( may need to also close your devenv)

    3. Relaunch Devenv and open your solution - this should load with an empty environment.

    4. Publish now...and this should work.

    If you really are pressed for a fix, please contact Product Support and ask to get a QFE (fix) for your situation...

    Hope this helps

    Robert Schoen (Microsoft Visual Basic QA)

  • TimFröglich

    Does anyone have any idea where this is coming from It completely blocks using ClickOnce to deploy the application.

  • SignTool reported an error 'XmlResolver can be set only by fully trusted code.
Answer this question