.net-assembly

In one of my projects, I am using an awesome library called Humanizer . This library comes in many language variations (I counted 38). When I build my project, I then see all these folders like "af", "ar", "bg", "bn-BD", ..., "zh-Hant" with assemblies containing the localized resources for this library. My issue is that my project is English-only and I have no interest in having all those localized assemblies in my build output. Is there some good way of omitting them from the build? I am looking for general solutions to this problem. It happens with libraries other than Humanizer, like

Goal: From a .NET 4.7 console app, using reflection with Assembly.GetType(), I am trying extract the Type of a netstandard 2.0 class from Assembly X. Then I want to create an instance of this Type with Activator.CreateInstance(). What I am trying to do: However, this assembly X has a dependency to netstandard 2.0. To be able to get the Type, netstandard dependency has to be loaded into the AppDomain. That's why when the AppDomain is requesting the netstandard assembly through the AssemblyResolve event, I simply load the dll like this : var netStandardDllPath = @"C:\Users\xxx\.nuget\packages

This question already has answers here : Retrieve AssemblyCompanyName from Class Library (5 answers) I am using Assembly.GetEntryAssembly().GetName() to get application/assembly name and its version but I do not see any variable for company name and copyright. How do I get that? You can use FileVersionInfo like this: var versionInfo = FileVersionInfo.GetVersionInfo(Assembly.GetEntryAssembly().Location); var companyName = versionInfo.CompanyName; George Duckett From this answer for the company name: Assembly currentAssem = typeof(CurrentClass).Assembly; object[] attribs = currentAssem

I'm trying to make application with plugins. I have MainLib.dll, where I made some commnon interface(let it be ICommon ) with 1 method. Then, I made 2 .dlls(plugins) which have reference to MainLib.dll and implement the ICommon in some classes. Also, I removed all the references in this .dlls exept System . Then, I created an application, which monitors folder ".\\Plugins" and loads all .dlls in newDomain , check if the types in .dll implement ICommon (so this application also reference to MainLib.dll). If yes - add the name of .dll in some list. And now here the problem : before I tried to

I've recently set up a new Windows Server 2012 R2 environment and installed Visual Studio 2012 . Now I'm having a problem with multiple .NET 4.5 project's I migrated from my old server, a Windows Server 2008 machine. This never occurred on the old server. When trying to load an assembly from a network location, I run into the following issue: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be

Given a loaded Assembly is there a way (in code) to determine which of the 3 load contexts it was loaded into (default Load , LoadFrom, or Neither )? In Suzanne Cook's "Choosing a Binding Context" article, there are some disadvantages that occur when an assembly is loaded into the LoadFrom . In particular, my library uses deserialization and encounters an InvalidCastException when loaded into the LoadFrom context. Currently my library fails very late (it fails when it executes the problematic deserialization code--see my example ). I'd like to make it fail much earlier in these circumstances