Skip to content
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

Port to .NET Standard 2.0 #36

Open
wants to merge 21 commits into
base: master
Choose a base branch
from

Conversation

ggeurts
Copy link

@ggeurts ggeurts commented Sep 17, 2018

Rhino code and tests have been ported to .NET Standard 2. Projects have been ported to the common project system and dependencies on external libraries replaced with NuGet references. Tests have been updated to use xUnit 2.0. Tests also use SQL Server LocalDB instead of SQL Server Express.

The following features are not available for the .NET Standard 2 platform:

  • SQL Server batch operations, because SqlCommandSet is not (yet) available on the .NET Core platform;
  • Boo DSL support, because no Boo port is available for .NET Core.

A new Rhino.Etl.Infrastructure.ConnectionProvider API has been added to provide a way to define and open connections that does not rely on XML configuration files.

@ggeurts
Copy link
Author

ggeurts commented Nov 13, 2018

A working System.Data.SqlClient.SqlCommandSet implementation should be available when .NET Core 3 is released (see https://github.com/dotnet/corefx/issues/29391).

@ggeurts
Copy link
Author

ggeurts commented Jul 4, 2019

System.Data.SqlClient 4.7.0 preview now has a working SqlCommandSet implementation, which means that except for the DSL logic all functionality is available for .NET Core.

@sundarbabu-dev
Copy link

Is this .Net core support to be released sometime this year? WE are having 40+ ETL packages that are using rhino ETl & Rhino ServiceBus. I would like to try .Net Core update to try to improve performance and multi platform capability.

@yvsean
Copy link

yvsean commented Mar 17, 2020

I'm not sure it would necessarily be the best to merge this into the main branch, for backwards compatibility purposes, but I think this fork looks great. Is there any chance of getting it up on NuGet independantly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants