Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Dotfuscator CE error: External type not found System.Windows.Input.ICommand,PresentationCore RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Preemptive will not support CE so I am trying here...

    I have an application targeting the .NET Framework 4.0.  It builds and runs fine but I cannot get it to compile in Dotfuscator CE. I am stuck.

    Dotfuscator CE (v5.0.2500.0) with Visual Studio 2010 SP1.  Here is the Error:

    Resolving method references...

    External type not found System.Windows.Input.ICommand,PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.

    Build Error.

    The problem seems to originate from ICommand being moved from PresentationCore.dll (in NET 4.0) to System.dll (in NET 4.5).  Studio handles this and compiles fine as I am targeting NET 4.0 and the references all point to

    C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\

    Dotfuscator CE however does not seem to handle it correctly and I am not sure how to correct the issue.  Any help would be greatly appreciated!!

    Friday, January 3, 2014 4:52 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Perter,

    It seems that it is not the VS General issue.

    I did some research about the Dotfuscator CE, like paul’s suggestion in this thread, I’m afraid that we don’t support this software production.

    But I think you could get better support here:

    http://www.preemptive.com/support/dotfuscator-support

    Reference:

    http://social.msdn.microsoft.com/Forums/en-US/48b85bb8-f60f-444c-8ee4-0b2980ca4a41/dotfuscator-issue?forum=vbgeneral

    Best Regards,

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, January 6, 2014 7:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you Jack. 

    The problem is Visual Studio ships with Dotfucator CE under our MSDN subscription as a tool to be used.  Using Premptive support would be fine but they tend to not answer unless you have paid for the professional version of Dotfuscator which is priced higher than Visual Studio.

    I did try them first for support and still no answer at all.  I cannot get any detail out of Dotfuscator to find the problem.  It really shouldn't be this difficult and finger pointing between companies for support leaves the customer frustrated; this is why customers look for other solutions and tool sets.

    The root cause is likely the way Dotfuscator is mapping changes caused by .NET 4.5 where classes were moved from one dll to another.

    Monday, January 6, 2014 2:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Perter,

    Thanks for your response.

    External type not found System.Windows.Input.ICommand,PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.

    Maybe it is related to the references in your project.

    Reference:

    The type 'System.Windows.Input.ICommand' exists in both 'PresentationCore.dll' and 'System.dll'

    Since it is not the VS General issue, I am moving your question to the moderator forum ("Where is the forum for..?"). The owner of the forum will direct you to a right forum. Thanks for your understanding.

    Best Regards,

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, January 7, 2014 5:29 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I tried Preemptive directly rather than a support case and they outright told me they will not support dotfuscator CE edition. 

    I have checked all of my references and everything targets the .NET 4 Reference Assemblies folders.  Everything builds and runs fine in debug and release mode within studio.  Even if the error is somewhere within my own projects, I really have no indicator, log or debug tool to determine where things are going wrong.

    Tuesday, January 7, 2014 1:23 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Microsoft does not support Preemptive products either.

    The community edition is backed up by the community. Try your luck in the Dotfuscator Community Edition forum on http://www.preemptive.com/forum/

    Visual C++ MVP


    Tuesday, January 7, 2014 10:30 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Microsoft does not support Preemptive products either.

    Then Microsoft should not include that crap of an unsupported software that only runs its users into trouble. Please remove it from future Visual Studio setups to signal that it's not a good idea to use it.
    Wednesday, March 5, 2014 1:19 PM