Check this. The idea is that you get the list of assembly attributes using Assembly.GetCustomAttributes() and search for DebuggableAttribute and then find if such attribute has IsJITTrackingEnabled property set. public bool IsAssemblyDebugBuild(Assembly assembly) { return assembly.GetCustomAttributes(false).OfType<DebuggableAttribute>().Any(da => da.IsJITTrackingEnabled); }
The frameworks are designed to be backwards-compatible; if you have a program written in .NET 2.0, you can run it in the 4.0 runtime, because none of the frameworks ever remove functionality that a prior version had (which is why we still have the non-generic collections like ArrayList, even though they’re deprecated in favor of … Read more
This is a shameless copy-paste from I Note It Down and is a simple way to get the FQN for the project output: Open Visual Studio Go to Tools –> External Tools –> Add Title: Get Qualified Assembly Name Command: Powershell.exe Arguments: -command “[System.Reflection.AssemblyName]::GetAssemblyName(\”$(TargetPath)\”).FullName” Check “Use Output Window”. The new tool appears under Tools –> … Read more
This seems to be a reliable, simple way to get the “entry” or main assembly for a web app. If you put controllers in a separate project, you may find that the base class of ApplicationInstance is not in the same assembly as your MVC project that contains the Views – but, this setup seems … Read more
As the others said, most of the time you won’t want to do that because it doesn’t copy the assembly to your project and it won’t deploy with your project. However, if you’re like me, and trying to add a reference that all target machines have in their GAC but it’s not a .NET Framework … Read more
Here is some code I use that supports getting the application’s “main” assembly from either Web or non-web apps, you can then use GetName().Version to get the version. It first tries GetEntryAssembly() for non-web apps. This returns null under ASP.NET. It then looks at HttpContext.Current to determine if this is a web application. It then … Read more
There is a way to do this, but you will have to hand edit your project files. The project files can have a Condition attribute applied to them in many of the elements, including the one for references. You can add these to your references to specify when the reference should be used: <Reference Include=”Product, … Read more
If you mean programmatically, use Assembly.GetReferencedAssemblies. You can use that recursively to find all the assemblies you need. (So you find the dependencies of X, then the dependencies of the dependencies, etc.)
I work on the CLR/BCL team and just answered your email. Here it is pasted below: Jared’s answer on Stack Overflow is right on. mscorlib.dll is tightly bound to the CLR for the reasons he mentions. Note that mscorlib.dll itself doesn’t contain any native code (as Scott suggests), but there are many places where it … Read more
Try setting the Build Action property of the source DLLs to None. It solved the issue for us.