Liking this framework.
Don't quite understand why there is a mix of technologies - it seems to complicate things. Anyway, as a lesson in using the framework I was hoping to move the login page of the application which currently loads up via MVC view/controller to <a class="postlink" href="http://myserver/Account/Login">http://myserver/Account/Login</a> and instead I would want the user to be redirected to <a class="postlink" href="http://myserver/#/Login/">http://myserver/#/Login/</a>
I've immediately hit a hurdle in the Startup.cs file where I try to change the login path, but the # gets translated to /%23/Login?returnurlxxxxx
So, 2 questions really:
Why is the out of the box design split in this way? is this just to demonstrate that the app can be developed using either approach?
if it is not a requirement and just an example, how can I move my login logic to within the main SPA?
I did it like that since this allows us to use razor and c# code in our views. And it adds an extra power to our views. But this is not required. Actually, startup template has just 2 empty pages. So, you can easily convert it to simple html files. If you want to completely seperate, I suggest you to create a completely seperated project for it. Do not create it in Visual Studio. Thus, you will not be tied to VS and ASP.NET at all.