This is a migrated thread and some comments may be shown as answers.
Crash on startup
1 Answer 55 Views
This is a migrated thread and some comments may be shown as answers.
Mel
Top achievements
Rank 2
Mel asked on 28 Apr 2011, 09:22 AM
Crashes when starting up with the following message (this happens if you run the app from a shortcut created by right clicking on the app and selecting 'pin to start menu' - the app starts ok if you run it straight from the installation directory - shortcut created due to no start menu created by the Installer):

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



Microsoft.Practices.Prism.Modularity.ModuleTypeLoadingException: Failed to load type for module HistoryModule.



If this error occurred when using MEF in a Silverlight application, please ensure that the CopyLocal property of the reference to the MefExtensions assembly is set to true in the main application/shell and false in all other assemblies.



Error was: Could not load file or assembly 'JustDecompile.History.dll' or one of its dependencies. The system cannot find the file specified.. ---> System.IO.FileNotFoundException: Could not load file or assembly 'JustDecompile.History.dll' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

   --- End of inner exception stack trace ---

   at System.Reflection.AssemblyName.nGetFileInformation(String s)

   at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile)

   at System.ComponentModel.Composition.Hosting.AssemblyCatalog.LoadAssembly(String codeBase)

   at System.ComponentModel.Composition.Hosting.AssemblyCatalog..ctor(String codeBase, ICompositionElement definitionOrigin)

   at Microsoft.Practices.Prism.MefExtensions.Modularity.MefFileModuleTypeLoader.LoadModuleType(ModuleInfo moduleInfo)

   --- End of inner exception stack trace ---

   at Microsoft.Practices.Prism.Modularity.ModuleManager.HandleModuleTypeLoadingError(ModuleInfo moduleInfo, Exception exception)

   at Microsoft.Practices.Prism.Modularity.ModuleManager.IModuleTypeLoader_LoadModuleCompleted(Object sender, LoadModuleCompletedEventArgs e)

   at Microsoft.Practices.Prism.MefExtensions.Modularity.MefFileModuleTypeLoader.RaiseLoadModuleCompleted(LoadModuleCompletedEventArgs e)

   at Microsoft.Practices.Prism.MefExtensions.Modularity.MefFileModuleTypeLoader.RaiseLoadModuleCompleted(ModuleInfo moduleInfo, Exception error)

   at Microsoft.Practices.Prism.MefExtensions.Modularity.MefFileModuleTypeLoader.LoadModuleType(ModuleInfo moduleInfo)

   at Microsoft.Practices.Prism.Modularity.ModuleManager.BeginRetrievingModule(ModuleInfo moduleInfo)

   at Microsoft.Practices.Prism.Modularity.ModuleManager.LoadModuleTypes(IEnumerable`1 moduleInfos)

   at Microsoft.Practices.Prism.Modularity.ModuleManager.LoadModulesWhenAvailable()

   at Microsoft.Practices.Prism.Modularity.ModuleManager.Run()

   at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.InitializeModules()

   at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.Run(Boolean runWithDefaultConfiguration)

   at JustDecompile.App.OnStartup(StartupEventArgs e) in c:\B\Behemoth\JustDecompile Production Build\Sources\UI\JustDecompile\App.xaml.cs:line 21

   at System.Windows.Application.<.ctor>b__1(Object unused)

   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.Threading.Dispatcher.Run()

   at System.Windows.Application.RunDispatcher(Object ignore)

   at System.Windows.Application.RunInternal(Window window)

   at System.Windows.Application.Run(Window window)

   at System.Windows.Application.Run()

   at JustDecompile.App.() in c:\B\Behemoth\JustDecompile Production Build\Sources\UI\JustDecompile\obj\Release\App.g.cs:line 16777215
---------------------------
OK   
---------------------------

1 Answer, 1 is accepted

Sort by
0
Todd Anglin
Top achievements
Rank 2
answered on 28 Apr 2011, 04:59 PM
Hello Mel-

Sorry for the beta trouble. I've run in to this in the past sporadically, too. Usually the problem was due to some other process on my system trying to access the MEF modules JustDecompile is trying to load (like maybe a virus scanner). As you've observed, it's not consistent and you can still sometimes successfully launch JustDecompile. We'll work on providing better error handling for this with the official release.

In the meantime, you may want to check out my response on this forum thread where I provide more explanation about the HistoryModule and you can disable it if you're interested:

http://www.telerik.com/community/forums/justdecompile/general-discussions/exception-running-justdecompile-the-first-time.aspx

-Todd
Asked by
Mel
Top achievements
Rank 2
Answers by
Todd Anglin
Top achievements
Rank 2
Share this question
or