I think the answers above with * instead of assembly name should also work. dll extension, exactly as it shows in the exception. Note: assembly name is your filename without. reg file, change assembly name and its guid and double-click it to merge into the Registry.
You have to create those new keys in the registry, keys have no values under them. This is a solution which worked for me to disable strong name validation for a particular assembly while testing it within totally signed service: Even more so because it was happening inside a WiX custom action, making it difficult to check the assemblies that were actually included. Someone shared this solution in the 'Share your Unity Hub 3.0 Beta Feedback Here' thread. Being used to seeing similar exceptions when assemblies are missing or have their versions mismatched, it took me a while before I finally got to the bottom of it. This is apparently an issue with the new hub beta. This is an exception I received: Error Type: System.IO.FileLoadExceptionĮrror Message: Could not load file or assembly 'MyAssemblyName, Version=5.1.0.0, Culture=neutral, PublicKeyToken=30b439e30eee46b4' or one of its dependencies. Quit the Unity Hub from the icon tray (the thing bottom right) and relaunch the Unity Hub as administrator.
0 kommentar(er)
