Update considerations for .NET Standard

pull/39/head
FreddyD 6 years ago
parent 366a4f2b14
commit e945f4cef8

@ -47,6 +47,10 @@
- Refer to: https://developercommunity.visualstudio.com/content/problem/697732/test-runner-wont-execute-net-core-tests-in-32-bit.html
- Ensure xUnit test projects contain a reference to the nuget package xunit.runner.visualstudio to run the test from Visual Studio Test Explorer
## .NET Standard Compatibility
- Should the projects also target .NET Standard 2.0? Even if the project compiles for .NET Standard 2.0, it will not work across all .NET Standard 2.0 platforms. In particular, it will only work on Windows, which many users may expect, however, I believe either the COM or System.Data.OleDb (or both) will fail if running on .NET Core 2.0/2.1/2.2, which would be an incompatibility that is more difficult for users to guess.
- Is targeting .NET Standard 2.1 instead an option? Would have to explicitly target .NET Framework as well, unless EFCore.Jet wants to drop support for it. However, what is the advantage? Perhaps just Mono on Windows?
## General Resources
- [Multitargeting](https://docs.microsoft.com/en-us/dotnet/core/tutorials/libraries#how-to-multitarget)
- [MS Access Data Manipulation Language](https://docs.microsoft.com/en-us/office/client-developer/access/desktop-database-reference/data-manipulation-language)

@ -1,7 +1,7 @@
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFrameworks>netstandard2.0;net461;netcoreapp3.1</TargetFrameworks>
<TargetFrameworks>net461;netcoreapp3.1</TargetFrameworks>
<GenerateAssemblyInfo>false</GenerateAssemblyInfo>
<RootNamespace>EntityFrameworkCore.Jet</RootNamespace>
<AssemblyName>EntityFrameworkCore.Jet</AssemblyName>

@ -1,7 +1,7 @@
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFrameworks>netstandard2.0;net461;netcoreapp3.1</TargetFrameworks>
<TargetFrameworks>net461;netcoreapp3.1</TargetFrameworks>
<GenerateAssemblyInfo>false</GenerateAssemblyInfo>
<Platforms>AnyCPU;x86;x64</Platforms>
</PropertyGroup>

Loading…
Cancel
Save