downloading new version of npgsql i could See is not compiled old mono.security dll file. Is Not needed in newest version? I have not to ad any reference to this library if i use 3x version?
Thanks.
You're correct - Mono.Security.dll is no longer needed in Npgsql 3.x. You don't need to add any reference to any external library in order to use Npgsql 3.x.
Related
I am using Steeltoe.CloudFoundry.Connector.EFCore with Npgsql.EntityFrameworkCore.PostgreSQL. I want to migrate the application to .NET 5.0. After updating Npgsql to 5.0.2 I am getting the error 'Unable to find DbContextOptionsBuilder, are you missing a PostgreSql EntityFramework Core assembly?' when adding DBContext.
I tried to look at the available versions of Steeltoe, but the highest NuGet I see is 2.5.2, which gives me this error as well as the older I had (2.4.4).
Is there any version combination of those libraries that works?
The name of that Steeltoe package changed in 3.0, you'll be needing Steeltoe.Connector.EFCore going forward.
The name of that particular type inside Npgsql.EntityFrameworkCore.PostgreSQL changed in 5.0, so that's what is preventing Steeltoe from finding it. The fix has also been applied to the 2.x branch and is included in version 2.5.3.
Check the Steeltoe Samples repo for both 2.x and 3.x versions
Current .net framework version of Unity is .net v4.6
Will it allow importing of plugins that target .net v4.7?
And as a more generic (not version based) question.
Does Unity allow importing of dlls built on a higher version than the Unity build support?
No.
The reason is that the DLL may have used C# feature that is not yet supported in the current version of Unity. It will fail silently or you will get a similar error below:
The primary reference "The DLL" could not be resolved because it has a
higher version "x.x.x.x" than exists in the current target framework.
The version found in the current target framework is "x.x.x.x".
You need to recompile the plugin with the-same version of .NET Unity is using or find another plugin with the correct version.
I'm using nppgsql 2.2.x version for 1 year but yesterday I tried to use 3.0.5.
I added reference to new library and all Database extraction run perfect but I found big problem with Majorsilence Reporting. No report will appear.
When using version 2.2.x all reports run.
Now I run on 4.0 framework and I read that it is not possible to use a framework little then 4.5 (but it run on 4.0!).
What could be the problem in your mind? Could it be the target framework?
Could it be some changes in 3.x version?
Do you have any ideas? I don't want to use 2.2.x version forever.
Thanks
Sorry. .. npgsql want 4.5 .net And majorsilence run on 4.0
This scenario goes a bit against the whole way nuget works so what i might be asking for is a hack...
My problem:
I need to have Restsharp and Protobuf-net referred to in a .net assembly that going into SQL-CLR for Server 2008 (so max .net 3.5, framework 2.0).
Restsharp goes back to 3.5 as the lowest supported fwk version.
Protobuf-net 3.5 onwards has a lot of gunk referring to system.servicemodel (and WCF) which i don't need and use and actively want to remove because it causes issues with installing on SQL-CLR. Protobuf-net 2.0 doesn't have this :)
So i've built and tested my code with an assembly targeting .net 3.5 and i installed the restsharp nuget - which gave me the correct reference and i manually added a reference to the protobuf-net 2.0 distro.
This is where i'd like to know - can i (in any way) install the protobuf-net nuget package but still have it reference the .net20 DLL in my assembly which targets 3.5?
The static reference is not a huge deal since protobuf-net has been pretty stable, but i'd like to get the whole setup via nuget if possible.
In the end, this is a workaround as solution to:
protobuf-net version without system.servicemodel dependency?
If there's a better answer to that, i'd be very grateful :)
As far as I know, that is not possible. You could of course create your own custom build and host it on a local nuget drop, or as your own nuget package on the public feed. AFAIK, there's no way to do what you want inside a new nuget folder in the existing package.
What is the difference between AutofacContrib.Multitenant.dll and Autofac.Extras.Multitenant.dll.
I fell both will enables multitenant DI support. Currently i am using AutofacContrib.Multitenant.dll and is not available in NuGet gallery. But Autofac.Extras.Multitenant.dll exists in NuGet gallery. Is both are same ?
Both of these are the same library. As of version 3.0, all AutofacContrib.* libraries were updated to be Autofac.Extras.*. Use the AutofacContrib versions until such time as you've upgraded your core Autofac to 3.0+, then switch over to the Autofac.Extras version. The AutofacContrib libraries were left for people who haven't upgraded yet.