IMAP library compatible with .NET Framework 2.0 - imap

Is there any free IMAP library that supports .NET Framework 2.0?
As I know, the Imapx, InterImap, S22.Imap and MailSystem.NET are not compatible with .net 2.0.
Thank you!

Good day!
ImapX can be compiled under .Net 2.0 using LinqBridge. Please see this discussion thread for a download: Does ImapX support .NET Framework 2.0?. The binaries for .Net 2.0 and 3.0 will be also available through the download section and Nuget starting from next library release.

Related

I cannot change the Target Framework from .NET 5.0 to .NET 4.8 for a C# .NET Framework Class Library in Visual Studio 2019

I am trying to build a .NET 4.8 Class Library that I can make COM-Visible as a support library from an Access application.
There are no prompts for the version of .NET Framework when I create the solution.
When I look at the Project Properties, the .NET Framework is set to 5.0.
Although I have the .NET Framework 4.8 installed, it does not appear in the combo-box for the Target framework. The only options are shown below.
I have also noticed that the Startup object combobox does not reflect the selected startup assembly.
Do I need to drop back to Visual Studio 2017 to create a .NET Framework 4.8 library?
Which SDK is installed?
If you only have the .net 5 SDK installed, it might suffice for making a .net core 3 app but it will not cover .net Framework.
Install the .net Framework SDK for the version you want to target.
And/or install a targeting pack if you want to target .net 4.8 and 4.7.2 for example.
(Maybe helpful: What's the difference between the .NET Framework SDK and the Targeting pack)
This happened to me because I had choosen the wrong kind of project.
I had choosen a project library for C#, Windows Linux, macOS.
By this the same thing, that one could only had .NET 5.0 and higher as Framework.
I had to create a new library project with only C# and Windows.
Than I could choose all installed .NET frameworks

Install nuget package : EntityFramework 6 in .NETStandard 2.0 class library

I installed nuget package: EntityFramework 6 in .NET Standard2.0 Class library. On building the project I am getting the below warning message:
NU1701:Package 'EntityFramework 6.2.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.
Does it mean that we cannot use EntityFramework 6 in .NETStandard 2.0 class library?
Can anyone help me here by providing their inputs
[...]. This package may not be fully compatible with your project.
Entity Framework 6 will be compatible with a project that target .NET Framework but will not be compatible with a project that target .NET Core
The answer is yes, you can use EF6 with .NET Standard 2.0 class library as long as you plan to only support .NET Framework
Microsoft already announced they plan to release a version of EF6 that support .NET Core at the end of 2019.
Disclaimer: I'm the owner of the project Entity Framework Classic
Entity Framework Classic is an EF6 fork. It's everything you like about EF6, but with better performance, must-have features, .NET Core support, and more.
It's currently the only option available to use a EF6 fork on a project that target NET Core
There is a free Community version that includes pretty much everything and an Enterprise version that include additional features.

How is it possible to use OData in .net core application?

According to docs (http://odata.github.io/WebApi/#11-01-OData-V4-Web-API-Scaffolding) it is required to inherit from ODataController.
I have installed package using nuget and still not able to inherit from that class.
Does OData support .net core? Are docs obsolete?
A possible duplicate of OData Support in ASP.net core
The docs link that you mentioned is targeting .NET Framework. For .NET Core support, please download the Microsoft.AspNetCore.OData NuGet Package from
https://www.nuget.org/packages/Microsoft.AspNetCore.OData
This package has a dependency on Microsoft.OData.Core which will also get installed automatically. Starting from version 7.2.0 the package is targeting .NET Standard 1.1.
Once the package is referenced, You should be able to inherit from ODataController. For further details please refer to the following video and links
https://www.towfeek.se/2017/01/08/odata-with-aspnet-core/
http://odata.github.io/odata.net/v7/#ODL-7.3.1
I hope this helps

Is exists any nuget package for oauth 1.0 that compatible with asp.net core?

I tried very hard to find and could not.
I need OAuth 1.0 since I need to use intuit QB which not support oauth 2.0 yet.
thanks!
I had the same struggle the past few days in finding an implementation for .NET Core that supports OAuth 1.0. The library from Chilkat may be the only one out there. Not sure if the OAuth API inside the library requires the commercial license or not.
https://www.chilkatsoft.com/refdoc/csOAuth1Ref.html
https://www.chilkatsoft.com/dotnet-core.asp
Another solid option is to use the portable version RestSharp which has a built-in OAuth1Authenticator: https://www.myget.org/feed/restsharp-portable/package/nuget/FubarCoder.RestSharp.Portable.OAuth1
I used OAuth.DotNetCore for OAuth 1.0 with .Net Core 2.1, it worked fine.
https://www.nuget.org/packages/OAuth.DotNetCore/

Build libgit2sharp for .net 2.0

Did anyone succeed in building libgit2sharp using .NET 2.0?
I need to make the library work under VS 2005 and have many 3.5 features to re-write.
Does anyone know of a better way to work under VS 2005 with the library or is there .net 2.0 library version available anywhere?
Is there .net 2.0 library version available anywhere?
There is no official LibGit2Sharp version working against .Net 2.0. Only .Net 3.5 or Mono 2.10 are currently supported.
Does anyone know of a better way to work under VS 2005?
Current version embeds a lightweight compatibility layer to ease a future migration towards .Net 4.0.
Provided you're committed to make it to work against .Net 2.0, I'd suggest you to adapt a similar kind a isolation layer, and (as much as possible, trying to) avoid altering the code of the library. This will ease the backporting of any future LibGit2Sharp update in your project.

Resources