You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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.
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?
The text was updated successfully, but these errors were encountered: