Are you sure you have the right RegAsm in your path since you’re calling it by exe name only without specifying the full path? You must call the right version of RegAsm for it to work, i.e 32 or 64-bit version of .NET 4. Try specifying the full path: c:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /codebase F:\Workflow\WorkflowHandler\bin\debug\WorkflowHandler.dll or c:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe /codebase … Read more
You can use the Strong Name tool to determine if the assembly is strongly named. In command prompt you can do this to verify it is a strong named assembly. sn -v “C:\MyAssemblyPath” and to get the public token, you can do this sn -T “C:\MyAssemblyPath” You can also use Reflector or ILSpy to find … Read more
Clear out the temporary framework files for your project in: For Windows 7, the path is: C:\Users\[username]\AppData\Local\Temp\Temporary ASP.NET Files\ For 64 bit systems with ‘Framework’ in the path the full path is: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\ http://www.solutioncottage.com/ShowSolution.aspx?solID=59
Try doing something like this: var mth = new StackTrace().GetFrame(1).GetMethod(); var cls = mth.ReflectedType.Name; // where 1 illustrates how deep into the stack to reflect. There are more elegant solutions in C# 5.0 >, however if you are using older frameworks, the above will help.
Assembly.GetAssembly assumes you have an instance of the type, and Type.GetType assumes you have the fully qualified type name which includes assembly name. If you only have the base type name, you need to do something more like this: public static String GetAssemblyNameContainingType(String typeName) { foreach (Assembly currentassembly in AppDomain.CurrentDomain.GetAssemblies()) { Type t = currentassembly.GetType(typeName, … Read more
The options that I found were to: Add a reference to PostSharp in Project A. Add dummy code in Project B so that the compiler would detect that the reference is being used. Add a build event to force copy the DLL. I don’t like any of the above solutions. They are hacks in my … Read more
Resharper shadow copies assemblies for testing by default. If you turn off shadow-copy, it will run in the bin folder and the test should pass. Here are some instructions on turning it off.
ConcurrentDictionary<WeakReference, CachedData> is incorrect in this case. Suppose we are trying to cache info for type T, so WeakReference.Target==typeof(T). CachedData most likely will contain reference for typeof(T) also. As ConcurrentDictionary<TKey, TValue> stores items in the internal collection of Node<TKey, TValue> you will have chain of strong references: ConcurrentDictionary instance -> Node instance -> Value property … Read more
… Could not load file or assembly ‘X’ or one of its dependencies … Most likely it fails to load another dependency. you could try to check the dependencies with a dependency walker. I.e: https://www.dependencywalker.com/ Also check your build configuration (x86 / 64) Edit: I also had this problem once when I was copying dlls … Read more
You can use Reflector, ILDASM or ILSpy to get the assembly version. You usually can find ILDASM in C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\ildasm.exe (where v8.1A is the version of the Windows SDK installed). ILDASM: Reflector: