-
Notifications
You must be signed in to change notification settings - Fork 566
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
What happened to StripeChargeCreateOptions and StripeChargeService? #1349
Comments
Hey @UweKeim! Sorry about the confusion here! The 20.0 release was a major release which introduced numerous breaking changes. The main one was removing the Let me know if this doesn't help! |
Hi @UweKeim. Something to keep in mind when upgrading stripe-dotnet: we use semantic versioning, meaning that we increment the major version number whenever breaking changes are introduced. This means that it's always safe to upgrade to a new a minor or patch version, but you should always check the changelog before upgrading to a new major version. |
To answer your specific question, we've removed the Closing the issue, but feel free to reply if you're having trouble or have any suggestions to improve the migration guide! |
Thanks a lot guys! |
Above migration guide's link is broken. @remi-stripe, fyi, may be worth updating your comment here. |
I think this is old, but i have a question about the "StripeChargeService" i used |
@Alexislml96 The change was mostly a rename from |
Yes i understand that, my question is where can i put the "sk_test" key in the ChargeService method? |
You would do something like this:
|
Wll finally i can resolve it, i just need to put the key like this at the beginning of the code in the server side. |
Just updated the NuGet package to v20.1.0 just to see compiler errors about undefined symbols for
StripeChargeService
andStripeChargeCreateOptions
.Are there migration paths available to whatever's hot now?
The text was updated successfully, but these errors were encountered: