1. Brian O'Malley
  2. SnapDevelop
  3. Monday, 1 February 2021 16:44 PM UTC

I am just starting to look into using SnapDevelop to possibly migrate our application and I have been having a difficult time with the demos because it seems that things do not match.  I am using SnapDevelop 2019 R3 Build 2622. 

I have moved onto trying JWT and I am again not able to do what the demo says.  I try to add the following to my startup:

using Microsoft.AspNetCore.Authentication.jwtbearer;

And I get an error that jwtbearer does not exist in the namespace Microsoft.AspNetCore.Authentication

I tried using the NuGet to install Microsoft.AspNetCore.Authentication.JwtBearer (which is version 5.0.2) and I get another error that it is not compatible with netcoreapp3.1 and that it supports .NetCoreApp Version 5.0. 

I am not sure how to update .NetCoreApp to 5.0?

Instead, can I install a lesser version of JWTBearer (3.1.11)?

Thanks!

Brian

Accepted Answer
Logan Liu @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 2 February 2021 09:06 AM UTC
  2. SnapDevelop
  3. # Permalink

Hi Brian,

Thank you for pointing out the problem!

JwtBearer packages depend on the .NET Core version. Net Core 5.0 is still not supported in SnapDevelop R3, so please install Microsoft.AspNetCore.Authentication.JwtBearer 3.1.11 to your .NET Core 3.1 project.

 

Sorry for the confusion. We will improve the documentation to make it clearer.

 

BTW: you can refer to more details about this change since ASP.NET Core 3.0.

"ASP.NET Core 3.0 removes some assemblies that were previously part of the Microsoft.AspNetCore.App package reference. "

https://docs.microsoft.com/en-us/aspnet/core/migration/22-to-30?view=aspnetcore-5.0&tabs=visual-studio#add-package-references-for-removed-assemblies

Regards,

Logan

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 1 February 2021 17:04 PM UTC
  2. SnapDevelop
  3. # 1

With all respect to Appeon, but due to a lot of changes in packages, it would be nice if you guys could re-run the demo material you provide to see if everything still works.
The other way of getting there is by having us report every little thing that doesn't work. A slow process.
It's little encouraging for noobs like me to try demos that don't compile since we first would think we've done something wrong or missed something.

Thank you, we do appreciate your hard work!

Comment
  1. Armeen Mazda @Appeon
  2. Monday, 1 February 2021 19:14 PM UTC
Hi Miguel, We do update the tutorials to reflect changes of new versions. I think a couple of them must have been overlooked. For future releases, we will improve the process so doesn't fall through the cracks.
  1. Helpful
  1. Miguel Leeuwe
  2. Monday, 1 February 2021 20:05 PM UTC
Thank you Armeen!
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.