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

.net core support #298

Closed
chrishaly opened this issue Nov 11, 2016 · 13 comments
Closed

.net core support #298

chrishaly opened this issue Nov 11, 2016 · 13 comments

Comments

@chrishaly
Copy link

chrishaly commented Nov 11, 2016

Hi,

are there roadmap for making tesseract support .Net Core?

@charlesw
Copy link
Owner

charlesw commented Dec 5, 2016

Not yet, I'm inclined to wait till .Net Core's tooling and .Net standard has stabilised.

@tdhintz
Copy link
Contributor

tdhintz commented Jan 3, 2017

Just a shout out for .Net Standard - we've made the shift to that.

@Brumawen
Copy link

I have successfully ported the code to compile under DotNet Core. There are a few minor changes that need to be done but it all seems to work OK.

@tmacharia
Copy link

How did you do it @Brumawen ??

@aporquez
Copy link

Any updates guys? Net Standard 2.0 has been released months ago.

@Brumawen can you share the steps/process on how you ported the code to .net core?

@seriouz
Copy link

seriouz commented Oct 25, 2017

The question is... will it be ever done?

@antoniocorreia
Copy link

any updates on that? @Brumawen can you share this changes with us?

@charlesw
Copy link
Owner

charlesw commented Mar 20, 2018 via email

@antoniocorreia
Copy link

antoniocorreia commented Mar 20, 2018

awesome, thanks!

For those who are in a hurry I successfully adapted it to run with a .NET Core project, you can see a sample here

ps: it is just a rough adapt

@charlesw
Copy link
Owner

charlesw commented Mar 20, 2018

Done, complete rewrite of existing project structure to support multi-targeting and testing the major supported targets and generating nuget packages via visual studio's pack feature (or just use dotnet pack). However because of this a fully up-to date version of Visual Studio 2017 is required to build the project.

I'll be releasing a new version once I've tested the generated package on the sample project some more. Might not be for a few days though.

@unarix
Copy link

unarix commented Nov 26, 2018

@charlesw are this changes made in any nuget package?

@ghost
Copy link

ghost commented Mar 24, 2022

I want to ask. Any update?

@charlesw
Copy link
Owner

charlesw commented Mar 24, 2022 via email

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

No branches or pull requests

9 participants