dll-reference

Why is this NuGet dependency missing when compiling .NET Framework project depending on .NET Standard?

↘锁芯ラ 提交于 2020-12-02 18:56:59
问题 I have a Visual Studio solution, with 3 projects. The top level is a .NET Framework 4.6.1 Console App (Project A). It depends on a .NET Framework 4.6.1 Class Library (Project B). Project B depends on a .NET Standard 2.0 Class Library (Project C). I have some code in Project C that uses System.Data.SqlClient (NuGet package version 4.6.1). Due to the following known issue https://github.com/dotnet/sdk/issues/901 I have also added System.Data.SqlClient as a NuGet dependency to Project B (the

Why is this NuGet dependency missing when compiling .NET Framework project depending on .NET Standard?

筅森魡賤 提交于 2020-12-02 18:28:49
问题 I have a Visual Studio solution, with 3 projects. The top level is a .NET Framework 4.6.1 Console App (Project A). It depends on a .NET Framework 4.6.1 Class Library (Project B). Project B depends on a .NET Standard 2.0 Class Library (Project C). I have some code in Project C that uses System.Data.SqlClient (NuGet package version 4.6.1). Due to the following known issue https://github.com/dotnet/sdk/issues/901 I have also added System.Data.SqlClient as a NuGet dependency to Project B (the

How do I reference a dll from SSIS in 2012?

感情迁移 提交于 2019-12-18 09:19:33
问题 I am trying to add a dll reference to my SSIS package (2012) with a script Component. The IntelliSense is working for me and I don't see error when coding. However, I get the following error: Could not load file or assembly 'XYZ, Version=1.0.0.0, Culture=neutral, PublicKeyToken=XYZ' or one of its dependencies. The system cannot find the file specified. Please help. 回答1: If this is a custom DLL, then you will need to install it into the GAC (global assembly cache) for it to run outside of SSDT

Difference between project and dll dependencies in .Net in the final compiled assembly

∥☆過路亽.° 提交于 2019-12-12 08:45:28
问题 Lets say I have two projects A and B. A depends on B. I can specify this in two ways: Include A and B in the same solution and specify B as a project dependency for A. This shows up in A's msbuild project as a "ProjectReference" node. Include a reference to the B's compiled dll as dependency for A. This shows up in A's msbuild project as a "Reference" node My question is, once I've build the assembly for A, is there a difference in the final output between these two methods. I tried creating

Impact of adding dll reference vs project reference

我的未来我决定 提交于 2019-12-11 12:38:23
问题 Is there any build time impact ? We have around 30 projects in our .Net solution and they shared projects are added by project reference. I am thinking to change to dll reference instead to see if there is any build performance gain. Did anyone have experience on similar lines ? Please share your thoughts. 回答1: Yes, there is potentially a huge impact depending on how you have your CI set up. The solution to this is to group logical sections of your application (data access, presentation,

How to reference C# dll located in different folder to a C# winforms exe in different folder which uses Interface exposed by that dll

痴心易碎 提交于 2019-12-11 02:48:12
问题 I have a C# windows forms that uses a Utility.dll located in different folder than that of the EXE location. Utility.dll contains a class UtilityClass and an interface ILoadString. When i do not inherit ILoadString interface in my Form1.cs class, i am successfully able to load the Utility.dll through AppDomain.AssemblyResolve Event in Program.cs. The problem arises when i try to inherit ILoadString interface in Form1.cs. When i try to run the project, i get an FileNotFoundException from

Difference between project and dll dependencies in .Net in the final compiled assembly

☆樱花仙子☆ 提交于 2019-12-04 04:19:48
Lets say I have two projects A and B. A depends on B. I can specify this in two ways: Include A and B in the same solution and specify B as a project dependency for A. This shows up in A's msbuild project as a "ProjectReference" node. Include a reference to the B's compiled dll as dependency for A. This shows up in A's msbuild project as a "Reference" node My question is, once I've build the assembly for A, is there a difference in the final output between these two methods. I tried creating a couple of simple projects which model this relation and tried a comparison - but different comparison

How do I reference a dll from SSIS in 2012?

风流意气都作罢 提交于 2019-11-29 16:00:18
I am trying to add a dll reference to my SSIS package (2012) with a script Component. The IntelliSense is working for me and I don't see error when coding. However, I get the following error: Could not load file or assembly 'XYZ, Version=1.0.0.0, Culture=neutral, PublicKeyToken=XYZ' or one of its dependencies. The system cannot find the file specified. Please help. If this is a custom DLL, then you will need to install it into the GAC (global assembly cache) for it to run outside of SSDT. An assembly cannot be installed into the GAC unless it's strongly signed . Once it's signed, from a Visual