.NET Core

[iamadamreed]

Do you know if this can be used with .NET Core, and if not when you intend to release an update library for it?

[SergeySagan]

Yes, please!

[mitchcapper]

I agree, we have migrated a large amount of our code over but we cannot move the authorize.net segment due to the lack of .net core support.

[SergeySagan]

Sadly, you have to manually create all of the DTO and make the Rest calls yourself. Here' a bit more on SO: http://stackoverflow.com/q/40356667/550975

[brianmc]

Hi guys, I just ran the portability analyzer on our SDK and it's showing 97%, so not much to do, really just the http request classes and couple of others. We'd really like to get a cut out soon, but with minimal impact to the .net framework compatibility obviously. I can't promise anything but our plan right now is to create a new core branch, make the changes there and hopefully publish a separate beta core package until we have better testing and confidence around the overall compat.

Thanks for the request, it's exciting period for Microsoft and I'm loving .Net Core on the Mac :-)

Brian

[Insomniak47]

Are there any updates WRT timelines for core support?

[gehnster]

I'd also like an update, looks like last one was 6 months ago and .NET Core is up to 1.1 now. Also, please make sure any updates you release to this support VS 2017. It is currently in a late-stage RC but it made an important change of moving from xproj to csproj project files. Thanks!

[Optiknights]

Any updates to the dotnet core updates?
Until thats completed, does anyone have a walk through solution to integrating this as a .Net Nuget package targeting .Net framework on a dotnet core project? Or some other solution to get this package working on a dotnet core app?

[mitchcapper]

The package needs to be recreated to target .NET standard not .net framework. .NET standard works for .NET core and .NET framework projects. This framework is really just a wrapper around REST calls to the authorize.net server so if you were on a crunch you could just re-implement or migrate what code you could using their REST documentation. Assuming Authorize.NET releases the SDK on nuget as a .NET standard library it will work in any VS instance including 2017. Even if they didn't and they left it as an xproj converting to csproj is very easy so would not be an issue. csproj files are not as back compat either which causes another problem.

[mtinnes]

Another vote for a quick convert to .net core. We are in a holding pattern until the core library is released and I hate to go through the trouble of converting it ourselves if a release is imminent.

[chassq]

Yes, please do this! NET Core 2.0 is almost here. Would be nice to roll this out with 2.0.

[chris-oswald]

+1 for .Net Core Support

[gehnster]

Would much like .NET Core support.

[vishalmgiri]

Team any update on .net core support

[brianmc]

Hi everyone. We hear ya and thanks for all the feedback. So had a crack at this earlier in the year and ran into a few roadblocks. So at that point, knowing we have some great new lightweight client libraries coming we figured we would design those to be core from the ground up. Obviously those are not out yet either so we owe an apology there. What we will do right now is look at the last attempt again and review the issues. Maybe we even open that core repo up as public and see if we can get some contributions. Look for another update on this early next week.

[vishalmgiri]

Thanks for update Brain