Common JustDecompile Beta 1 Issues/Workarounds

11 posts, 0 answers
  1. Todd Anglin
    Todd Anglin avatar
    2040 posts
    Member since:
    Aug 2005

    Posted 28 Apr 2011 Link to this post

    Hello Everyone-

    Thanks again for taking the time to try the JustDecompile Beta and for helping us make JustDecompile a great v1 tool. Obviously, with any early beta, there are issues that must be ironed out and you can expect updated builds from Telerik soon that will start to fix many of these items. For now, here are some workaround to the common problems people are encountering with the Beta 1 build.

    (You can also review the the unofficial JustDecompile FAQs on my blog for more info.)

    ISSUES/WORKAROUNDS

    1. Crash when trying to use Find Usages
      There is a known issue with the Find Usages dialog that will cause a crash if a "Ctrl+Left Click" action is performed while the Find Usages window is open. To resolve, simply close the Find Usages window before doing a Ctrl+Left Click. More info in this forum thread: http://www.telerik.com/community/forums/justdecompile/general-discussions/crash-during-find-usages.aspx
    2. Crash on Windows XP
      There is a known issue with Windows XP that causes JustDecompile to crash (error says something about Bitmap image format). There is no available workaround for this problem other than to use a newer version of Windows. We will fix Windows XP support in an upcoming build.
    3. Unable to launch JustDecompile from "Open With..." Windows menu
      This is a known beta issue. JustDecompile will crash if you attempt to launch using the "Open With..." Windows command due to a MEF error. To resolve, simply launch JustDecompile by double-clicking the executable or by making shortcuts for the executable in your Start Menu/Task Bar. Support for "Open With..." will be fixed in an upcoming build.
    4. Crash with message about unable to load HistoryModule
      JustDecompile is based on MEF and all of the built-in tools, like History, are MEF plug-ins. In order to load properly, the JustDecompile EXE needs to be able to locate these plug-ins. Please make sure the JustDecompile.exe is located in the same folder as the supporting MEF and Prism dlls (in other words, don't move the .EXE or you may have problems like this). Also, make sure any shortcuts are pointing to the correct JustDecompile.exe in the install folder ("C:\Program Files (x86)\Telerik\JustDecompile\Libraries").
    5. Unable to launch after installing
      Unfortunately, the JustDecompile beta installer does not add shortcuts to the start menu, desktop, or task bar. After running the beta installer, please navigate to the JustDecompile install directory ("C:\Program Files (x86)\Telerik\JustDecompile\Libraries") and directly launch the JustDecompile.exe. You can also pin the JustDecompile.exe app to your Start Menu or Task Bar for easier launching in the future.
    6. GoToType/GoToSymbol Growing Search Results
      In some cases, the search results for GoToType or GoToSymbol will append and duplicate when a space is added after the initial search results have been returned. To resolve, simply clear the entire search string and restart the search process. This will reset the search results list.

    Hope this helps. Obviously, there are other bugs and issues that we are documenting and responding to in upcoming builds, but these seem to be the major issues people are hitting with Beta 1. If additional items rise to the top, I will update this thread. Keep the great feedback coming and stay tuned for updated builds with bug fixes and new features!

    -Todd
  2. Cody
    Cody avatar
    9 posts
    Member since:
    Mar 2011

    Posted 28 Apr 2011 Link to this post

    +1 vote for XP support ( I didn't see a better place to vote for features).
  3. DevCraft banner
  4. Bill Wehnert
    Bill Wehnert avatar
    1 posts
    Member since:
    Jul 2009

    Posted 03 May 2011 Link to this post

    I'm also getting this same error on Windows Server 2003.
  5. Thomas
    Thomas avatar
    1 posts
    Member since:
    May 2011

    Posted 08 Jun 2011 Link to this post

    I found a work around for the Crash on Windows XP - at higher screen resolutions the crash occurs. Setting the resolution down to 1280 x 1024 for example, the crash does not occur.

    Crash on Windows XP

    There is a known issue with Windows XP that causes JustDecompile to crash (error says something about Bitmap image format).
  6. Tsviatko Yovtchev
    Admin
    Tsviatko Yovtchev avatar
    408 posts

    Posted 14 Jun 2011 Link to this post

    @Thomas: Does this stil happen on your machine? Have you updated to the latest version of JustDecompile?

    @Cody: You can always vote for features here - http://justdecompile.uservoice.com/

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>

  7. Rob
    Rob avatar
    1 posts
    Member since:
    Jan 2011

    Posted 20 Jun 2011 Link to this post

    I just installed the latest version "JustDecompile_BETA_2011.1.624.2" and still get these exceptions.
    I'm on Windows 7 64bit with all the latest Microsoft updates.

    Assembly List:      DefaultAssemblyList
    Name:                  Protect
    Platform Target:   NET 4 
    Location:              C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Security.dll
    -------------------------------------------------------------------------------------------------
    An exception is thrown when I try to open either of these methods:

    System.Security.dll
    System.Security.Cryptography
    ProtectedData
     - Protect(...
     - Unprotect(...

    Exception

    Current member / type: System.Byte[] System.Security.Cryptography.ProtectedData::Protect(System.Byte[],System.Byte[],System.Security.Cryptography.DataProtectionScope)File path: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Security.dllIndex was outside the bounds of the array.
    at ..(Collection`1 instructions)
    at ..() at Telerik.JustDecompiler.Decompiler.DecompilationPipeline.Run(MethodBody body, ILanguage language)
    at Telerik.JustDecompiler.Decompiler.Extensions.(DecompilationPipeline pipeline, ILanguage language, MethodBody body)
    at Telerik.JustDecompiler.Languages.BaseImperativeLanguageWriter.Write(MethodDefinition method)
    at Telerik.JustDecompiler.Languages.BaseImperativeLanguageWriter.Write(IMemberDefinition member, Boolean showCompilerGeneratedMembers)
    at JustDecompile.CodeViewer.CodeWriter.Write() in c:\B\Behemoth\JustDecompile Production Build\Sources\UI\JustDecompile.CodeViewer\Writers\CodeWriter.cs:line 34
    at JustDecompile.CodeViewer.ViewModels.CodeViewerViewModel.(AssemblyMemberNode member, CancellationToken cancellationToken) in c:\B\Behemoth\JustDecompile Production Build\Sources\UI\JustDecompile.CodeViewer\ViewModels\CodeViewerViewModel.cs:line 107

     

     

  8. Mbutu
    Mbutu avatar
    1 posts
    Member since:
    Dec 2007

    Posted 25 Jun 2011 Link to this post

    When I try to open compiled resources (*.resources) from assembly, *sometimes* I get following exception:

    An error has occurred. Please, report this exception to the Telerik team (Use CTRL + C to copy the text). Thanks in advance!

    System.NullReferenceException: Object reference not set to an instance of an object.
       at JustDecompile.CodeViewer.Formatters.ResourceViewer.() in c:\B\Behemoth\JustDecompile Production Build\Sources\UI\JustDecompile.CodeViewer\Formatters\ResourceViewer.cs:line 16777215
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
       at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
       at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
       at System.Windows.Application.RunDispatcher(Object ignore)
       at System.Windows.Application.RunInternal(Window window)
       at System.Windows.Application.Run(Window window)
       at JustDecompile.App.() in c:\B\Behemoth\JustDecompile Production Build\Sources\UI\JustDecompile\obj\Release\App.g.cs:line 16777215

    --------------
    .NET Framework 4.0.30319, Windows XP Pro SP3. Both up to date and all hotfixes installed.
  9. Kaloyan
    Admin
    Kaloyan avatar
    920 posts

    Posted 28 Jun 2011 Link to this post

    Hi Mbutu,

    Thank you for reporting the issue. Can you try reproducing the issue by using the latest product update? We used to have a similar problem in one of the older product versions.

    Kind regards,
    Kaloyan
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>

  10. John
    John avatar
    1 posts
    Member since:
    Sep 2011

    Posted 08 Sep 2011 Link to this post

    This is my first post so I'm not sure if this is the correct place for a bug report.

    I decompiled a very small project.  Most of the code was correct but the following snippet was significantly incorrect.  The original code is:

    public bool IsValidDate ( string date )
    {
    // Allow an empty TextBox
    if ( date.Length != 0 )
    {
    // Must be exactly 10 characters
    if ( date.Length != 10 )
    {
    return false;
    }
    // Parse the date.  If it fails the date is invalid
    try
    {
    DateTime dateTime = DateTime.Parse ( date );
    }
    catch ( Exception ex )
    {
    return false;
    }
    }
    return true;
    }

    The decompiled version came back as:

    public bool IsValidDate(string date)
    {
    bool flag;
    if (date.Length != 0)
    {
    DateTime dateTime = DateTime.Parse(date);
    if (date.Length != 10)
    {
    flag = false;
    }
    else
    {
    flag = false;
    flag = true;
    }
    }
    try
    {
    }
    catch
    {
    }
    return flag;
    }

    Notice that the else block sets flag to both false and true, and that the try/catch block is empty.

    I thought I would pass this along in case no one else had reported it.

    Thanks,

    John

  11. Tsviatko Yovtchev
    Admin
    Tsviatko Yovtchev avatar
    408 posts

    Posted 13 Sep 2011 Link to this post

    Hi John,

     Thanks a bunch for letting us know about this problem. Normally, one would start a new topic for a new issue so you might just do that the next time.

    The good thing is we are already aware of this issue and we are already working on fixing it. So, please, stay tuned and update regularly.

    Regards,
    Tsviatko Yovtchev
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

  12. Isidro Padilla
    Isidro Padilla avatar
    31 posts
    Member since:
    Sep 2012

    Posted 13 Sep 2011 Link to this post

    I had a problem with version 09092011 released but was fixed in version 12092011. Now it seems to work correctly in Windows XP SP3 and Windows 7. It will certainly be a good tool.
    Good job.
    ipadilla
Back to Top
DevCraft banner