New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NET Core port [DNET682] #635
Comments
Modified by: @cincuranet |
Commented by: Michał Ziemski (r_o_o_k) As the NET Core 1.0 is officially out I set out to try to get FbClient to compile as netstandard1.6 I was able to compile a working client in ~1 hour by excluding some parts: Possibly the last two could have been saved :) Project.json I used: {
"dependencies": { "frameworks": { After the dependencies are there the rest of the process was reacting to changes in API in Core (rather straightforward |
Commented by: Michał Ziemski (r_o_o_k) One more needed dependency (with this I was able to keep Services & Events): Native client requires (at least - I wasn't able to build this part) for FbClientFactory |
Commented by: Fernando Leal (fernandocode) Are there any plans for the development of issues? There is some preliminary version that is possible to use it for testing? |
Commented by: Fernando Leal (fernandocode) As a basis for development we could use what has already been done by [Npgsql (Postgres Provider)](npgsql/npgsql@87e8cd2), which has already moved the .NET driver and EF Core module (old EF7) (https://github.com/npgsql/npgsql). I am using [this code version](https://sourceforge.net/projects/firebird/files/firebird-net-provider/5.0.5.0/) of source to make my tests! This is the official repository? |
Commented by: @cincuranet Yes, the code package is correct. I'm planning to work .NET Core once the compression support is finished. |
Modified by: @cincuranetstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: net-core [ 10784 ] |
Commented by: Tom S (tom) .NET Standard 2.0 is now fully RTW, including the tooling: https://blogs.msdn.microsoft.com/dotnet/2017/08/14/announcing-net-standard-2-0/ (as well as .NET Core 2.0) Would it be possible to look into upgrading the http://ADO.NET Provider to take advantage of the new standard? Thank you! |
Submitted by: Michał Ziemski (r_o_o_k)
Relate to DNET663
Votes: 1
NET Core RC2 was released recently.
I'd be great to have a build of NET Provider targeting one of the net platform standards:
https://github.com/dotnet/corefx/blob/master/Documentation/architecture/net-platform-standard.md
that would be able to run in the new environment.
The API exposed by NET Core is somewhat different then the Framework.
Few example:
- ICloneable is no more (this could be easiliy solved by removing that from the implemented interfaces list)
- serialization was scrapped (there are some stubs available in System.Runtime.Serialization.Primitives)
There are may other issues. Sometimes easily solved by referencing a relevant CoreFX assembly (ie System.Data.Common, System.ComponentModel.Primitives, etc ):
https://github.com/dotnet/corefx
others regretfully require some more sophisticated changes.
There are also some points that are simply not availabe (AFAIK):
- distributed transactions
The text was updated successfully, but these errors were encountered: