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

Inviting @Dixin to this project #1

Open
tsahi opened this issue Jan 11, 2022 · 2 comments
Open

Inviting @Dixin to this project #1

tsahi opened this issue Jan 11, 2022 · 2 comments

Comments

@tsahi
Copy link

tsahi commented Jan 11, 2022

Incidentally I found that @Dixin prepared a .NET Core port of the Transient Fault Handling block at Dixin/EnterpriseLibrary.TransientFaultHandling.Core, and also added new API. Why not join effort and concentrate EntLib development in one organization?

@Dixin
Copy link

Dixin commented Jan 11, 2022

Thanks. This library is no longer updated since 2013: https://www.nuget.org/packages/EnterpriseLibrary.TransientFaultHandling/

And my repo Dixin/EnterpriseLibrary.TransientFaultHandling.Core is not a folk of this repo, because I created my repo in 2016 for .NET Core/.NET Standard 1.0 by decompiling the binary, and this repo was created later in 2018.

@tsahi
Copy link
Author

tsahi commented Jan 12, 2022

Why did you decompile the binary, when the source was available on CodePlex (and now is available here)?

Anyway, I'm aware of the fact that the original EntLib isn't updated since 2013. I'm not sure how this repo was created, but it's based on the original source code. My thought was to apply your changes to this repo, and continue working from there. It may not be without problems, but considering it's the original source, I think it would be better. We could also generate API documentation from source, instead of relying on the MS Docs API documentation, that I don't know how long will they be kept online.

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

No branches or pull requests

2 participants