Extra info, there are some build conflicts, (although the solution does build)
There was a conflict between "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes".
1> "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" was chosen because it was primary and "mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes" was not.
1> References which depend on "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6.1\mscorlib.dll].
Is this a 4.5.1, 4.6.1 .net framework thing?
Hi ismcagdas,
Thank you for the reply. I have an error and observation that I want to share with you.
Error: If I post to /api/TokenAuth/ExternalAuthenticate it returns an error.
Exception thrown: 'System.IO.FileLoadException' in System.Net.Http.dll
Exception thrown: 'System.IO.FileLoadException' in mscorlib.dll
Exception thrown: 'System.IO.FileLoadException' in mscorlib.dll
Observation: You need to post an provideraccescode and a providerkey to this endpoint. To do this for e.g. Facebook in the Angular UI, the Facebook Connect Javascript SDK is loaded, which is (among other things) a oAuth client. So we now have a complete oAuth implementation on the Angular client side and a complete oAuth implementation on the Server side, handling over authentication through /api/TokenAuth/ExternalAuthenticate endpoint. In a way this feels redundant, but I wouldn't know a better approach. Is my abservation correct?
It supports AspNet Core, but it still relies on .Net Framework 4.6?
(I never really understood the new .net stack, with AspNet Core being partly dependant on .Net framework 4.6 and/or .Net Core)