5 Answer(s)
-
0
Hi,
Angular2 version does not have public website. You can read this announcement about it <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-angular-obsolete/issues/10">https://github.com/aspnetzero/aspnet-ze ... /issues/10</a>
-
0
Thanks. link seems broken. What do you advise for public website? Do we download a different version? or perhaps go with wordpress or something? Or are we supposed to use the angular 2 website as the public website? Thanks.
-
0
Hi,
Your github user (chauey) has right to see this page, maybe you tried with a different github user ?
-
0
it goes to <a class="postlink" href="https://github.com/aspnetzero/aspnet-zero-angular-obsolete/issues/10">https://github.com/aspnetzero/aspnet-ze ... /issues/10</a> and I get a 404 message there.
-
0
Hi,
I'm sharing the related part of this issue/announcement here.
Public Web Site pages currently consists of integrated (merged) views into ASP.NET MVC (MPA) and ASP.NET Core (MPA) projects (they are in same project in the VS solution).
Also, we had decided to completely separate Angular 2 UI solution from the backend. They are completely different VS solutions (Angular project is even can be developed outside of VS, for example on Linux with Sublimetext).
Based on this information; Currently ASP.NET Core + Angular 2 solution does not contain the public web site. Because;
- We don't include ASP.NET Core MVC project into the downloaded project and public web site locate inside this project (as I described above).
- We haven't re-developed it via Angular2 since we think it should not be a SPA, but should be a MPA.
So, what if you want ASP.NET Core + Angular 2 and but also want to have the public web site template. We are planning to separate it from ASP.NET Core MVC application as an independent MVC project. So, you will be able to get it in the future. But it has a problem: Single sign on! Once they are different projects and deployed independently, they can not share same auth tokens normally. So, we should find a way of single sign on (aspnetzero/aspnet-zero-core#6). We didn't want to wait Angular 2 release just before of this bonus public web site.
For who want it before we create a way, as a workaround, they can re-create their solution as ASP.NET Core 1.x + jQuery, delete Areas folder in the solution and copy Web.Mvc project to their ASP.NET Core solution created with Angular 2 UI.
