.net-assembly

问题 I have a .NET Standard 2.0 DLL project. It has no other references, apart from NETStandard.Library 2.0.1 and all is fine. It is referenced by a WPF application and everything seems to work fine. Once I add a nuget package for System.Collections.Immutable 1.5.0 to the DLL project, a yellow exclamation mark appears on the Dependencies root of the Solution Explorer. (Hm... I now see that the exclamation remains even after I remove this package, but I guess this is a VS bug since everything

问题 My project solution is currently having three projects: MyProject , which is my main startup project (using .NET Framework 4.7 ) - WPF, UI specfic, MyProject.Core - class library ( .NET Standard 2.0 ) - holding the models, and all of the 'behind the scenes' data MyProject.Relational - class library ( .NET Standard 2.0 ) - responsible for processing and saving the database specific informations Project 1 (main) has set a reference to project 2 and 3 . For the project 3 I have installed a NuGet

问题 In our application (solution with 65 projects), all referenced assemblies are analysed in run-time for the presence of Ninject modules (there is some filtering applied too). The modules are loaded later into the Ninject kernel and each module declares bindings for the kernel. We have adopted a loader that loads the referenced assemblies into a separate assembly in reflection only mode. The difference from the way Ninject can load assemblies from the directory is that the directory can contain

问题 Anybody seen the following an know of a workaround? Question If I have multiple solutions with multiple projects in each one. What I’m seeing is a failure to resolve assembly references. This seems to occur when I previously had an open solution that was built but had a missing reference (I forgot to build it). Then I open up the solution that will build the missing reference and do a build. Sometimes this solution fails to build even thought it has built successfully in the past. Error

问题 I'm writing C# code in Visual Studio. I add the embedded DLL inside the project, I am dynamically loading the assemblies. We use JSON.NET to serialize and deserialize objects with type Context.JobDataObj , which is defined in one of the embedded DLLs, and passing the DLLs between various programs. Unfortunately, whenever I attempt to deserialize, I get the following error: Type specified in JSON 'Context.JobDataObj, HPMContext, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' is not

问题 My console app uses System.Net.Http.Formatting v5.1.0.0 that depends on Newtonsoft.Json v4.5.0.0. My app however includes v6.0.0.0 of Newtonsoft.Json (for other reasons). To make System.Net.Http.Formatting use the new Newtonsoft.Json version I added an assembly redirect to the App.config: <?xml version="1.0" encoding="utf-8"?> <configuration> ... <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Newtonsoft.Json" publicKeyToken=

问题 I have custom assembly which serves only 1 purpose - it contains localization strings along with static method to read them. Assembly is successfully installed on server (SSRS's bin folder) and I have created function mapping static method to custom code - it all works. By works, I mean I can use this assembly to read strings, when I create localized version - it switches locale, etc... However if I change or add any text to assembly - deploy it and make sure right DLL file is deployed SSRS

问题 Say, that we have .NET application App along with additional assembly ClassLibrary , which, in turn, uses native DLL called Library . All these are in single solution, so I may set up the dependencies etc. The catch is, that I want the Library to be automatically "attached" to ClassLibrary , such that when my App references it, Visual Studio will automatically copy the Library to target bin folder. Usually I did that by using pre-build or post-build events and adding custom scripts. But hey,

问题 I am going to use #if DEBUG directive in a class library. The compiled ClassLibrary.dll will be used in a separate Application.exe. Will my debug code from this class library be executed in the following situations? library is compiled in DEBUG mode, application is compiled in RELEASE library is compiled in RELEASE, application is compiled in DEBUG 回答1: A compiler directive is interpreted at compile time and not at runtime. Therefore it does not matter, if the using application is compiled in

问题 I am currently trying out writing my own Intellisense comments into my sources as described in stackoverflow 8240402 stackoverflow 1632942 but it's not yet working correctly. I'm using VS 2008. I have a assembly "testAssembly" (compiled to a DLL) with ref class class1a and public ref class class1b : namespace testAssembly { /// <summary> /// Testkommentar class1a /// </summary> ref class class1a { int m_iValue; public: /// <summary> /// Testkommentar class1a constructor /// </summary> class1a