What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Visual C++ issues

diablo6510

New Member
Joined
Nov 6, 2016
Messages
4
Uninstalled and reinstalled 2015 C++ up to patch 4. Check Greymagic.dll still getting issues



2016-11-06 19:38:25,710 [1] INFO Logger (null) - Hearthbuddy Version: 0.3.1313.329
Path: J:\Program Files (x86)\Hearthbuddy\<ExeName>

OS Name: Microsoft Windows 7 Ultimate
OS Version: 6.1.7601
OS Architecture: 64-bit
InstalledUICulture: en-US [English (United States)]
CurrentUICulture: en-US [English (United States)]
CurrentCulture: en-US [English (United States)]

2016-11-06 19:38:25,731 [1] INFO Logger (null) - Now setting up JitProfiles...
2016-11-06 19:38:25,732 [1] INFO Logger (null) - JitProfiles successfully setup!
2016-11-06 19:38:25,733 [1] INFO Logger (null) - Now beginning pre-start tasks.
2016-11-06 19:38:25,734 [1] INFO Logger (null) - Now checking prerequisites...
2016-11-06 19:38:27,993 [1] ERROR Logger (null) - System.BadImageFormatException: Could not load file or assembly 'GreyMagic, Version=1.0.96.0, Culture=neutral, PublicKeyToken=260525fa2b0e778a' or one of its dependencies. The module was expected to contain an assembly manifest.
File name: 'GreyMagic, Version=1.0.96.0, Culture=neutral, PublicKeyToken=260525fa2b0e778a'
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.Assembly.Load(AssemblyName assemblyRef)
at Hearthbuddy.App.?????????????????????????????????????????()
at Hearthbuddy.App.OnStartup(StartupEventArgs e)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

2016-11-06 19:38:28,020 [1] ERROR Logger (null) - [Application_DispatcherUnhandledException] Unhandled exception
System.BadImageFormatException: Could not load file or assembly 'GreyMagic, Version=1.0.96.0, Culture=neutral, PublicKeyToken=260525fa2b0e778a' or one of its dependencies. The module was expected to contain an assembly manifest.
File name: 'GreyMagic, Version=1.0.96.0, Culture=neutral, PublicKeyToken=260525fa2b0e778a'
at Triton.Game.TritonHs.?????????????????????????????????????????()
at Hearthbuddy.App.OnExit(ExitEventArgs e)
at System.Windows.Application.DoShutdown()
at System.Windows.Application.ShutdownImpl()
at System.Windows.Application.ShutdownCallback(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
 
Attempted all as listed. Twice. Still receiving the failed application start because its missing "visual studio 2015 update 3 x86, VC++ 14.0
 
Back
Top