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

Support .NET Core #146

Closed
jakejscott opened this Issue Feb 22, 2016 · 61 comments

Comments

Projects
None yet
@jakejscott

jakejscott commented Feb 22, 2016

vnext no longer supports web.config, so you will need to change the way your reading up settings in the following places:

  1. ConfigManager.cs
  2. SDKConfigHandler.cs
  3. LogConfiguration.cs
@jbeen19

This comment has been minimized.

Show comment
Hide comment
@jbeen19

jbeen19 Jun 6, 2016

It would be nicer and less problematic if you would just allow use to add our own configuration by code instead of a config file that way, you guys are not holding us back.

jbeen19 commented Jun 6, 2016

It would be nicer and less problematic if you would just allow use to add our own configuration by code instead of a config file that way, you guys are not holding us back.

@braebot

This comment has been minimized.

Show comment
Hide comment
@braebot

braebot Jun 21, 2016

Member

@jbeen19, this is a great suggestion. We'd be willing to merge a PR with the suggested change. Similar changes have been made in the Java SDK to support optional configuration files and code config as well.

Member

braebot commented Jun 21, 2016

@jbeen19, this is a great suggestion. We'd be willing to merge a PR with the suggested change. Similar changes have been made in the Java SDK to support optional configuration files and code config as well.

@jakejscott jakejscott changed the title from Support .NET CoreCLR to Support .NET Core Jul 3, 2016

@jakejscott

This comment has been minimized.

Show comment
Hide comment
@samueldjack

This comment has been minimized.

Show comment
Hide comment
@samueldjack

samueldjack Jul 29, 2016

Contributor

I've just done a quick test with a project built against .Net 4.5.1 and it appears that all that's needed to have the SDK work is

  1. a small change to the ConfigManager, supplied in my pull request #180 . This simply keeps the ConfigManager from throwing when the web.config is missing.
  2. to pass in a settings dictionary containing the mode when you create you credentials. i.e.
           var credential = new OAuthTokenCredential(settings.ClientId, secret, new Dictionary<string, string>()
            {
                {"mode", "sandbox"}
            });

            new APIContext(credential.GetAccessToken()) {
                Config =
                    new Dictionary<string, string>()
                    {
                        {"mode", "sandbox"}
                    }
            };

I appreciate that supporting .Net Core (as opposed to Asp.Net core on .Net 4.5.1) will probably take rather more work!

Contributor

samueldjack commented Jul 29, 2016

I've just done a quick test with a project built against .Net 4.5.1 and it appears that all that's needed to have the SDK work is

  1. a small change to the ConfigManager, supplied in my pull request #180 . This simply keeps the ConfigManager from throwing when the web.config is missing.
  2. to pass in a settings dictionary containing the mode when you create you credentials. i.e.
           var credential = new OAuthTokenCredential(settings.ClientId, secret, new Dictionary<string, string>()
            {
                {"mode", "sandbox"}
            });

            new APIContext(credential.GetAccessToken()) {
                Config =
                    new Dictionary<string, string>()
                    {
                        {"mode", "sandbox"}
                    }
            };

I appreciate that supporting .Net Core (as opposed to Asp.Net core on .Net 4.5.1) will probably take rather more work!

@jakejscott

This comment has been minimized.

Show comment
Hide comment
@jakejscott

jakejscott Aug 8, 2016

I've written some sample code which demonstrates how to accept a payment using .net core

See this gist:
https://gist.github.com/superlogical/1b829ca1c9449e4788710867f346e90f

https://developer.paypal.com/docs/integration/web/accept-paypal-payment/

jakejscott commented Aug 8, 2016

I've written some sample code which demonstrates how to accept a payment using .net core

See this gist:
https://gist.github.com/superlogical/1b829ca1c9449e4788710867f346e90f

https://developer.paypal.com/docs/integration/web/accept-paypal-payment/

@ppmtscory

This comment has been minimized.

Show comment
Hide comment
@ppmtscory

ppmtscory Aug 11, 2016

I see the PR for this has been merged so I will close this. Please do let me know if I'm mistaken.

ppmtscory commented Aug 11, 2016

I see the PR for this has been merged so I will close this. Please do let me know if I'm mistaken.

@ppmtscory ppmtscory closed this Aug 11, 2016

@samueldjack

This comment has been minimized.

Show comment
Hide comment
@samueldjack

samueldjack Aug 11, 2016

Contributor

This PR only enables Asp.Net Core applications on the full .Net framework. I think quite a lot more need to change to use this library on .Net core (which enables multi-platform development)

Contributor

samueldjack commented Aug 11, 2016

This PR only enables Asp.Net Core applications on the full .Net framework. I think quite a lot more need to change to use this library on .Net core (which enables multi-platform development)

@braebot

This comment has been minimized.

Show comment
Hide comment
@braebot

braebot Aug 11, 2016

Member

Whoops, apologies for preemptively closing this issue!

Member

braebot commented Aug 11, 2016

Whoops, apologies for preemptively closing this issue!

@braebot braebot reopened this Aug 11, 2016

@dcworldwide

This comment has been minimized.

Show comment
Hide comment
@dcworldwide

dcworldwide Aug 14, 2016

Yes!! Please upgrade to .net core. It has been out for a while already and is definitely the future.

dcworldwide commented Aug 14, 2016

Yes!! Please upgrade to .net core. It has been out for a while already and is definitely the future.

@vip30

This comment has been minimized.

Show comment
Hide comment
@vip30

vip30 commented Sep 1, 2016

+1

@lobster2012-user

This comment has been minimized.

Show comment
Hide comment
@lobster2012-user

lobster2012-user commented Sep 23, 2016

+1

@mb2140

This comment has been minimized.

Show comment
Hide comment
@mb2140

mb2140 Oct 22, 2016

+1 - any update on this? This is one of the big pieces holding me back from upgrading.

mb2140 commented Oct 22, 2016

+1 - any update on this? This is one of the big pieces holding me back from upgrading.

@JeanCollas

This comment has been minimized.

Show comment
Hide comment
@JeanCollas

JeanCollas commented Oct 25, 2016

Updates?

@jphellemons

This comment has been minimized.

Show comment
Hide comment
@jphellemons

jphellemons Nov 29, 2016

When will the nuget package get this update?

jphellemons commented Nov 29, 2016

When will the nuget package get this update?

@master-still

This comment has been minimized.

Show comment
Hide comment
@master-still

master-still commented Jan 3, 2017

+1

@DarrellBailey

This comment has been minimized.

Show comment
Hide comment
@DarrellBailey

DarrellBailey commented Jan 3, 2017

+1

@chemitaxis

This comment has been minimized.

Show comment
Hide comment
@chemitaxis

chemitaxis Jan 14, 2017

Hi! Any news? :) Thanks!!!

chemitaxis commented Jan 14, 2017

Hi! Any news? :) Thanks!!!

@ClovertechAU

This comment has been minimized.

Show comment
Hide comment
@ClovertechAU

ClovertechAU Jan 16, 2017

+1 - Really need this to keep our apps on current tech

ClovertechAU commented Jan 16, 2017

+1 - Really need this to keep our apps on current tech

@JeanCollas

This comment has been minimized.

Show comment
Hide comment
@JeanCollas

JeanCollas Jan 16, 2017

If you need a core implementation, it has been ported few months ago. I checked it is is similar to the official implementation, only very few changes to make it compatible
https://github.com/geoperez/PayPalCore

JeanCollas commented Jan 16, 2017

If you need a core implementation, it has been ported few months ago. I checked it is is similar to the official implementation, only very few changes to make it compatible
https://github.com/geoperez/PayPalCore

@Cor4xX

This comment has been minimized.

Show comment
Hide comment
@Cor4xX

Cor4xX Feb 8, 2017

+1 Any news ? Really need this too ! Thanks a lot ! :p

Cor4xX commented Feb 8, 2017

+1 Any news ? Really need this too ! Thanks a lot ! :p

@Janisku7

This comment has been minimized.

Show comment
Hide comment
@Janisku7

Janisku7 Mar 3, 2017

totally would be awesome and then add visual studio 2015 and Visual Studio 2017 as well as .Net Core

Janisku7 commented Mar 3, 2017

totally would be awesome and then add visual studio 2015 and Visual Studio 2017 as well as .Net Core

@slamotte

This comment has been minimized.

Show comment
Hide comment
@slamotte

slamotte Mar 15, 2017

+100!!! This issue has been open over a year? How can a company like PayPal not respond? As reported two months ago by @JeanCollas above, someone else has made an unofficial port at https://github.com/geoperez/PayPalCore and if they can do this with minimal changes to code, why can't PayPal? Simply create a new NuGet package for .NET Core, no?

slamotte commented Mar 15, 2017

+100!!! This issue has been open over a year? How can a company like PayPal not respond? As reported two months ago by @JeanCollas above, someone else has made an unofficial port at https://github.com/geoperez/PayPalCore and if they can do this with minimal changes to code, why can't PayPal? Simply create a new NuGet package for .NET Core, no?

@cyberyak

This comment has been minimized.

Show comment
Hide comment
@cyberyak

cyberyak commented Mar 30, 2017

+1

@SneezeWeeze

This comment has been minimized.

Show comment
Hide comment
@SneezeWeeze

SneezeWeeze Apr 10, 2017

It's not like .NET Core will be used by a huge number of users and grow significantly over the next 5 years as the way to build any .net application or anything like that. I don't see what the big deal is all about.

SneezeWeeze commented Apr 10, 2017

It's not like .NET Core will be used by a huge number of users and grow significantly over the next 5 years as the way to build any .net application or anything like that. I don't see what the big deal is all about.

@slamotte

This comment has been minimized.

Show comment
Hide comment
@slamotte

slamotte Apr 10, 2017

Agreed @SneezeWeeze, it's not a big deal at all, not for me anyway. I decided on a different platform so I don't really care about this anymore.

slamotte commented Apr 10, 2017

Agreed @SneezeWeeze, it's not a big deal at all, not for me anyway. I decided on a different platform so I don't really care about this anymore.

@jakejscott

This comment has been minimized.

Show comment
Hide comment
@jakejscott

jakejscott Apr 10, 2017

@SneezeWeeze @slamotte Honestly, just go and write some simple HttpClient based code, you don't need a library to integrate with a rest API.

I've even published some example code in an comment in this thread here: https://gist.github.com/superlogical/1b829ca1c9449e4788710867f346e90f

jakejscott commented Apr 10, 2017

@SneezeWeeze @slamotte Honestly, just go and write some simple HttpClient based code, you don't need a library to integrate with a rest API.

I've even published some example code in an comment in this thread here: https://gist.github.com/superlogical/1b829ca1c9449e4788710867f346e90f

@JeanCollas

This comment has been minimized.

Show comment
Hide comment
@JeanCollas

JeanCollas Apr 11, 2017

@superlogical A library helps to keep the API up to date, and when it is official, it helps to integrate the right level of security, do the right checks, etc.
It is also a huge gain of time when starting a project, rather than having to start all over.
There is nothing difficult in integrating a Rest API, but it takes time and tests. And when it comes to money, it better be reliable.
Therefore an official solution is much better, even more when they have done 95% of the work for .Net, just need to modify like 40 lines of code to make it work on .NetCore

JeanCollas commented Apr 11, 2017

@superlogical A library helps to keep the API up to date, and when it is official, it helps to integrate the right level of security, do the right checks, etc.
It is also a huge gain of time when starting a project, rather than having to start all over.
There is nothing difficult in integrating a Rest API, but it takes time and tests. And when it comes to money, it better be reliable.
Therefore an official solution is much better, even more when they have done 95% of the work for .Net, just need to modify like 40 lines of code to make it work on .NetCore

@kwe

This comment has been minimized.

Show comment
Hide comment
@kwe

kwe commented Apr 19, 2017

+1

@rlogwood

This comment has been minimized.

Show comment
Hide comment
@rlogwood

rlogwood Apr 23, 2017

@superlogical appreciate the sample, Thank You!, agree with your view, but since we're all busy, it's also nice to have well tested turn-key solutions that are ready to go. There are a lot of events and event objects, there is the token acquisition and management, potential changes with subsequent API versions, etc. Would agree with other comments that an official .NET Core release would be a nice help, even as fun as it is to use the PayPal REST API with .NET Core, it feels a little like reinventing the wheel :)

rlogwood commented Apr 23, 2017

@superlogical appreciate the sample, Thank You!, agree with your view, but since we're all busy, it's also nice to have well tested turn-key solutions that are ready to go. There are a lot of events and event objects, there is the token acquisition and management, potential changes with subsequent API versions, etc. Would agree with other comments that an official .NET Core release would be a nice help, even as fun as it is to use the PayPal REST API with .NET Core, it feels a little like reinventing the wheel :)

@rolandoldengarm

This comment has been minimized.

Show comment
Hide comment
@rolandoldengarm

rolandoldengarm Apr 27, 2017

@superlogical thanks heaps for the example code! Exactly what I needed.

rolandoldengarm commented Apr 27, 2017

@superlogical thanks heaps for the example code! Exactly what I needed.

@webprofusion-chrisc

This comment has been minimized.

Show comment
Hide comment
@webprofusion-chrisc

webprofusion-chrisc May 14, 2017

Ok, so like many people starting new .net web projects I'm using dotnet core exclusively for a new site. We can all spend time building our own solutions or we can contribute to a common library (this one). @pp-randy et al, can you confirm this is something you are working on yourself? Do you want someone to work on a PR?

webprofusion-chrisc commented May 14, 2017

Ok, so like many people starting new .net web projects I'm using dotnet core exclusively for a new site. We can all spend time building our own solutions or we can contribute to a common library (this one). @pp-randy et al, can you confirm this is something you are working on yourself? Do you want someone to work on a PR?

@randstraw

This comment has been minimized.

Show comment
Hide comment
@randstraw

randstraw May 15, 2017

Member

@webprofusion-chrisc I am not currently working on a port for dotnet core. I will admit I have not done much of any new development with the dotnet core framework. This is still open as a SDK enhancement and I am tracking this internally. We do appreciate pull requests for changes and are happy to review them.

Member

randstraw commented May 15, 2017

@webprofusion-chrisc I am not currently working on a port for dotnet core. I will admit I have not done much of any new development with the dotnet core framework. This is still open as a SDK enhancement and I am tracking this internally. We do appreciate pull requests for changes and are happy to review them.

@webprofusion-chrisc

This comment has been minimized.

Show comment
Hide comment
@webprofusion-chrisc

webprofusion-chrisc May 16, 2017

@pp-randy no problem, it's a cheeky question but would PayPal be at all open to funding the port? If so, this can happen pretty quickly (because then I can do it at work rather than doing it when I get time at home). I can be contacted at apps {at} webprofusion.com

For a proper port the trick is deciding what the minimum .netcore api version to target would be (i.e .net standard 1.1) and trying to make minimal changes to the overall codebase so that the we can still share most of the code between the targeted .net versions. There would be some architectural differences where things like the configuration API have changed or been removed. At this stage it would be too early to port directly for .net standard 2.0 (which has more APIs available).

webprofusion-chrisc commented May 16, 2017

@pp-randy no problem, it's a cheeky question but would PayPal be at all open to funding the port? If so, this can happen pretty quickly (because then I can do it at work rather than doing it when I get time at home). I can be contacted at apps {at} webprofusion.com

For a proper port the trick is deciding what the minimum .netcore api version to target would be (i.e .net standard 1.1) and trying to make minimal changes to the overall codebase so that the we can still share most of the code between the targeted .net versions. There would be some architectural differences where things like the configuration API have changed or been removed. At this stage it would be too early to port directly for .net standard 2.0 (which has more APIs available).

@bremussolutions

This comment has been minimized.

Show comment
Hide comment
@bremussolutions

bremussolutions Jun 10, 2017

Paypal, what is the problem to port the SDK into a dotnet Core compatible format? Please take a stand what is your strategy and when we can reckon with this SDK port!

bremussolutions commented Jun 10, 2017

Paypal, what is the problem to port the SDK into a dotnet Core compatible format? Please take a stand what is your strategy and when we can reckon with this SDK port!

@webprofusion-chrisc

This comment has been minimized.

Show comment
Hide comment
@webprofusion-chrisc

webprofusion-chrisc Jun 11, 2017

@bremussolutions I can't speak for PayPal but dotnet core has significantly different APIs in some places, so stuff has to be cut out or re-written. Ideally this would be done in a way that retains backwards compatibility with .Net 4.5.x etc, I'm guessing this just isn't a priority or they don't have budget for it.

webprofusion-chrisc commented Jun 11, 2017

@bremussolutions I can't speak for PayPal but dotnet core has significantly different APIs in some places, so stuff has to be cut out or re-written. Ideally this would be done in a way that retains backwards compatibility with .Net 4.5.x etc, I'm guessing this just isn't a priority or they don't have budget for it.

@bremussolutions

This comment has been minimized.

Show comment
Hide comment
@bremussolutions

bremussolutions Jun 11, 2017

So all, what is your solution? Are you building all your own solution? Build your own Model, Serialization and use the REST API of PayPal? What is the best and efficient way to integrate PayPal into a .Net Core application?

bremussolutions commented Jun 11, 2017

So all, what is your solution? Are you building all your own solution? Build your own Model, Serialization and use the REST API of PayPal? What is the best and efficient way to integrate PayPal into a .Net Core application?

@georgiosd

This comment has been minimized.

Show comment
Hide comment
@georgiosd

georgiosd Jun 13, 2017

This is clearly a minimal-effort SDK. Very poor for a huge organization such as Paypal. No async/await support either.

@bremussolutions already started making my own client with WebRequest and Polly to be honest - it's only 3-4 calls that I need. If you need a larger surface from the API then probably worth branching off...

georgiosd commented Jun 13, 2017

This is clearly a minimal-effort SDK. Very poor for a huge organization such as Paypal. No async/await support either.

@bremussolutions already started making my own client with WebRequest and Polly to be honest - it's only 3-4 calls that I need. If you need a larger surface from the API then probably worth branching off...

@JeanCollas

This comment has been minimized.

Show comment
Hide comment
@JeanCollas

JeanCollas Jun 20, 2017

In case some are interested, I forked it to make it compatible with .Net Core, and even Xamarin if needed ( .Net Standard 1.6 library).

https://github.com/JeanCollas/PayPal-NETStandard-SDK

Do not hesitate to PR.
A review from the official team would also be appreciated.

Maybe I will add support for async/await soon.

JeanCollas commented Jun 20, 2017

In case some are interested, I forked it to make it compatible with .Net Core, and even Xamarin if needed ( .Net Standard 1.6 library).

https://github.com/JeanCollas/PayPal-NETStandard-SDK

Do not hesitate to PR.
A review from the official team would also be appreciated.

Maybe I will add support for async/await soon.

@xiaoleih41

This comment has been minimized.

Show comment
Hide comment
@xiaoleih41

xiaoleih41 Jun 21, 2017

PayPal is also working on a major revision of all of our SDKs right now. PayPal does not expect to have a final release until late 2017, but when we release the new version of .NET it will be compatible with .NET Core.

xiaoleih41 commented Jun 21, 2017

PayPal is also working on a major revision of all of our SDKs right now. PayPal does not expect to have a final release until late 2017, but when we release the new version of .NET it will be compatible with .NET Core.

@JeanCollas

This comment has been minimized.

Show comment
Hide comment
@JeanCollas

JeanCollas Jun 21, 2017

It seems logical to me as the competition seems very much advanced compared to Paypal.
And there is no reason for PayPal not to be compatible with .Net Standard as it does not require more than this (quite complete) framework, and would be compatible with all platforms.
Thanks for the information, waiting for it.

JeanCollas commented Jun 21, 2017

It seems logical to me as the competition seems very much advanced compared to Paypal.
And there is no reason for PayPal not to be compatible with .Net Standard as it does not require more than this (quite complete) framework, and would be compatible with all platforms.
Thanks for the information, waiting for it.

@xiaoleih41

This comment has been minimized.

Show comment
Hide comment
@xiaoleih41

xiaoleih41 Jun 22, 2017

@JeanCollas Truly appreciate your support, contribution, comment and patience. I will keep this thread posted once we get more updates.

xiaoleih41 commented Jun 22, 2017

@JeanCollas Truly appreciate your support, contribution, comment and patience. I will keep this thread posted once we get more updates.

@iAmBipinPaul

This comment has been minimized.

Show comment
Hide comment
@iAmBipinPaul

iAmBipinPaul Jul 26, 2017

Mean while ASP.NET Core developer can also use Microsoft.AspNetCore.NodeService package to use node SDK in the back-end, https://github.com/aspnet/JavaScriptServices/tree/dev/src/Microsoft.AspNetCore.NodeServices#microsoftaspnetcorenodeservices

iAmBipinPaul commented Jul 26, 2017

Mean while ASP.NET Core developer can also use Microsoft.AspNetCore.NodeService package to use node SDK in the back-end, https://github.com/aspnet/JavaScriptServices/tree/dev/src/Microsoft.AspNetCore.NodeServices#microsoftaspnetcorenodeservices

@stevehipwell

This comment has been minimized.

Show comment
Hide comment
@stevehipwell

stevehipwell Aug 25, 2017

Now that .NET Standard 2.0 is officially released can we get a time frame for a release that supports it?

stevehipwell commented Aug 25, 2017

Now that .NET Standard 2.0 is officially released can we get a time frame for a release that supports it?

@SneezeWeeze

This comment has been minimized.

Show comment
Hide comment
@SneezeWeeze

SneezeWeeze Aug 26, 2017

Yes, I am working on a project that is depending on the new SDK. A time estimate on this would be awesome to give to my client.

SneezeWeeze commented Aug 26, 2017

Yes, I am working on a project that is depending on the new SDK. A time estimate on this would be awesome to give to my client.

@jphellemons

This comment has been minimized.

Show comment
Hide comment
@jphellemons

jphellemons Aug 28, 2017

You can install Paypal's Nuget 1.8.0 if you target .Net Core 2.0 it's just restored using the full .net framework 👎 so a real/native .Net Standard 2 version would be great!

snip_20170828151538

jphellemons commented Aug 28, 2017

You can install Paypal's Nuget 1.8.0 if you target .Net Core 2.0 it's just restored using the full .net framework 👎 so a real/native .Net Standard 2 version would be great!

snip_20170828151538

@PaulStovell

This comment has been minimized.

Show comment
Hide comment
@PaulStovell

PaulStovell Sep 1, 2017

While you can install/restore the 1.8.0 NuGet in an ASP.NET Core 2.0 project, it doesn't actually work at runtime.

When you go to send a request to PayPal, it eventually hits this line of code:

httpRequest.ServicePoint.Expect100Continue = false;

This results in:

Unhandled Exception: System.PlatformNotSupportedException: Operation is not supported on this platform.
   at System.Net.SystemWebProxy.GetProxy(Uri destination)
   at System.Net.ServicePointManager.ProxyAddressIfNecessary(Uri& address, IWebProxy proxy)
   at System.Net.ServicePointManager.FindServicePoint(Uri address, IWebProxy proxy)
   at System.Net.HttpWebRequest.get_ServicePoint()

While you can certainly install it and compile against it, this package just doesn't actually work on ASP.NET Core 2.0.

I guess there's simply no official PayPal SDK support for ASP.NET Core 2.0.

PaulStovell commented Sep 1, 2017

While you can install/restore the 1.8.0 NuGet in an ASP.NET Core 2.0 project, it doesn't actually work at runtime.

When you go to send a request to PayPal, it eventually hits this line of code:

httpRequest.ServicePoint.Expect100Continue = false;

This results in:

Unhandled Exception: System.PlatformNotSupportedException: Operation is not supported on this platform.
   at System.Net.SystemWebProxy.GetProxy(Uri destination)
   at System.Net.ServicePointManager.ProxyAddressIfNecessary(Uri& address, IWebProxy proxy)
   at System.Net.ServicePointManager.FindServicePoint(Uri address, IWebProxy proxy)
   at System.Net.HttpWebRequest.get_ServicePoint()

While you can certainly install it and compile against it, this package just doesn't actually work on ASP.NET Core 2.0.

I guess there's simply no official PayPal SDK support for ASP.NET Core 2.0.

@paulcsiki

This comment has been minimized.

Show comment
Hide comment
@paulcsiki

paulcsiki Sep 1, 2017

I'm also looking forward to seeing support for .NET Core LTS (1.1.2 at this moment). Looking forward for an official update.

paulcsiki commented Sep 1, 2017

I'm also looking forward to seeing support for .NET Core LTS (1.1.2 at this moment). Looking forward for an official update.

@SneezeWeeze

This comment has been minimized.

Show comment
Hide comment
@SneezeWeeze

SneezeWeeze Sep 10, 2017

Yes, an official statement would be great right about now

SneezeWeeze commented Sep 10, 2017

Yes, an official statement would be great right about now

@hscanlan

This comment has been minimized.

Show comment
Hide comment
@hscanlan

hscanlan Sep 22, 2017

I also need this.

hscanlan commented Sep 22, 2017

I also need this.

@mdonogma

This comment has been minimized.

Show comment
Hide comment
@mdonogma

mdonogma Sep 25, 2017

asp.net core with full .net core runtime support is needed. (for cross platform developers it is essential).

mdonogma commented Sep 25, 2017

asp.net core with full .net core runtime support is needed. (for cross platform developers it is essential).

@JeanCollas

This comment has been minimized.

Show comment
Hide comment
@JeanCollas

JeanCollas commented Sep 25, 2017

@mdonogma Check https://github.com/JeanCollas/PayPal-NETStandard-SDK/tree/Core
And SamplesNetStandard folder for bits of code

@jphellemons

This comment has been minimized.

Show comment
Hide comment
@jphellemons

jphellemons Sep 25, 2017

the 1.9 nuget does still target the full framework. 4.6.1

jphellemons commented Sep 25, 2017

the 1.9 nuget does still target the full framework. 4.6.1

@AbdelrahmanGIT

This comment has been minimized.

Show comment
Hide comment
@AbdelrahmanGIT

AbdelrahmanGIT commented Oct 4, 2017

+1

@mikeenders77

This comment has been minimized.

Show comment
Hide comment
@mikeenders77

mikeenders77 Oct 9, 2017

This is why so many turn to stripe and never look at Paypal anymore. the number one web framework for the major language of C# is now at 2.0 and Paypal cannot release a version for over a year that even works with 1.0...smh.

mikeenders77 commented Oct 9, 2017

This is why so many turn to stripe and never look at Paypal anymore. the number one web framework for the major language of C# is now at 2.0 and Paypal cannot release a version for over a year that even works with 1.0...smh.

@hscanlan

This comment has been minimized.

Show comment
Hide comment
@hscanlan

hscanlan Oct 9, 2017

^^ Agreed. I moved to Stripe 10 seconds after my first comment here. Sorry PayPal, you snooze you loose. I'm guessing most people are going to ditch you if you don't support CORE.

hscanlan commented Oct 9, 2017

^^ Agreed. I moved to Stripe 10 seconds after my first comment here. Sorry PayPal, you snooze you loose. I'm guessing most people are going to ditch you if you don't support CORE.

@stefrank

This comment has been minimized.

Show comment
Hide comment
@stefrank

stefrank commented Oct 17, 2017

@jphellemons

This comment has been minimized.

Show comment
Hide comment
@jphellemons

jphellemons Oct 23, 2017

So PayPal bought https://www.braintreepayments.com/ to provide better dev support?

Install-Package Braintree

Feels strange to use "Braintree" stuff when working with PayPal 'native'

jphellemons commented Oct 23, 2017

So PayPal bought https://www.braintreepayments.com/ to provide better dev support?

Install-Package Braintree

Feels strange to use "Braintree" stuff when working with PayPal 'native'

@nukuuk

This comment has been minimized.

Show comment
Hide comment
@nukuuk

nukuuk Dec 16, 2017

Just discovered that this won't work with Asp.net Core 2.0. Jesus, mary and joseph on a crapstick.

nukuuk commented Dec 16, 2017

Just discovered that this won't work with Asp.net Core 2.0. Jesus, mary and joseph on a crapstick.

@randstraw

This comment has been minimized.

Show comment
Hide comment
@randstraw

randstraw Dec 16, 2017

Member

We are working on supporting the .Net Core platform with our next version. If you are interested review and provide feedback https://github.com/paypal/PayPal-NET-SDK/tree/2.0-beta.

Member

randstraw commented Dec 16, 2017

We are working on supporting the .Net Core platform with our next version. If you are interested review and provide feedback https://github.com/paypal/PayPal-NET-SDK/tree/2.0-beta.

@paulcsiki

This comment has been minimized.

Show comment
Hide comment
@paulcsiki

paulcsiki Dec 16, 2017

paulcsiki commented Dec 16, 2017

@sdcoffey

This comment has been minimized.

Show comment
Hide comment
@sdcoffey

sdcoffey Jan 12, 2018

Contributor

Hey ya'll!

Thanks for all the feedback on this request. I'm excited to announce we have a beta live of PayPal 2.0 with full support for dotnet core 2.0!

It's live on nuget here, or have a peek at the 2.0-beta branch.

I'm going to close this issue, please try out the beta and let us know what issues you find.

Contributor

sdcoffey commented Jan 12, 2018

Hey ya'll!

Thanks for all the feedback on this request. I'm excited to announce we have a beta live of PayPal 2.0 with full support for dotnet core 2.0!

It's live on nuget here, or have a peek at the 2.0-beta branch.

I'm going to close this issue, please try out the beta and let us know what issues you find.

@sdcoffey sdcoffey closed this Jan 12, 2018

@paypal paypal locked as resolved and limited conversation to collaborators Jan 16, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.