I was successful in upgrading the .net core app from 1.0 to 1.1, but when I upgraded the .net framework from 4.5.2 to 4.7, it failed.
What I am trying to do is have a dot net core 1.1 web application that uses a dot net framework 4.7 web api. By achieving this I would be able to develop an angular 4 app in dot net core, while getting access to the full dot net framework inside the webapi application (and specifically, the entity framework canvas).
To achieve this, I was going to create a new, stock standard dot net core mvc web app with individual security, then set up a stock standard dot net full framework mvc web app, also with mvc individual security but also with the webapi option ticked. Then if I used the core app, I could go through the standard log in process, knowing that it would also be authenticated with the webapi layer of the net framework app. The test case is that after authenticating with the dot net core app, I should be able to perform a GET on the default Values controller of the full net framework app and it would authenticate behind the scenes. (The default Values controller, btw, is found in a WebApi only application, but any webapi controller that has the Authorize attribute set and returns values would be a success for me.)
I was successful in upgrading the .net core app from 1.0 to 1.1, but when I upgraded the .net framework from 4.5.2 to 4.7, it failed.
What I am trying to do is have a dot net core 1.1 web application that uses a dot net framework 4.7 web api. By achieving this I would be able to develop an angular 4 app in dot net core, while getting access to the full dot net framework inside the webapi application (and specifically, the entity framework canvas).
To achieve this, I was going to create a new, stock standard dot net core mvc web app with individual security, then set up a stock standard dot net full framework mvc web app, also with mvc individual security but also with the webapi option ticked. Then if I used the core app, I could go through the standard log in process, knowing that it would also be authenticated with the webapi layer of the net framework app. The test case is that after authenticating with the dot net core app, I should be able to perform a GET on the default Values controller of the full net framework app and it would authenticate behind the scenes. (The default Values controller, btw, is found in a WebApi only application, but any webapi controller that has the Authorize attribute set and returns values would be a success for me.)