What is the logic behind having multiple domains for your product/SaaS offering???? Why would you want more than one domain name for your business? If customers go to MyBrand.com, then they also have to remember MyOtherURL.com too??
Why the decision to make the public landing pages completely separate and hosted at separate URL? What business use does this serve??
Before, with the Angular1 and MVC 5 version, you have your landing pages with no login required, and then when you login, the SPA lives under /Application#
Then only one domain name to remember, to brand, to backup, to deploy, and to pay for hosting on.
What about the current Core MVC + jQuery solution - why could it not have landing pages at base url mybrand.com? - and put all the admin/login required part - under mybrand.com/app ??? What would someone need to change to put it back to working like that??
I see this happened with version 4.1.0 of ASP.NET Zero:
V4.1.0 (2017-06-23) Public web site is moved to a separated project (and authentication integrated to the main application).
Possible to get guidance on how to get back to not separated project?
3 Answer(s)
-
0
Hi @dparizek,
The main purpose of the seperating Public website was Angular project.
I agree that the cost of maintaining more than one project requires more work but we don't have a chance to provide Public website both for jQuery and Angualr templates.
Public users only need to know the public website address. You can redirect users to admin websites from public website. I think this is not a problem for public users but it might be a problem for developers.
With the current design, you have two options I guess.
You can publish public website under IIS website and publich admin website as a sub-website under the public website. I haven't tried this actually.
You can manually merge Public website project into your admin project. But, I don't suggest doing that. It will require quite amount of time I guess.
-
0
Well can't I just modify the routing such that the logged in section is mybrand.com/app and then use a controller to make myself an index page that does not require login at mybrand.com (and any subdirectories that are not /app) ?
What files do I need to modify to effect that routing setup change? I don't need any login or shared login on the non /app pages
-
0
@dparizek that can work as well. You can just create an Area named App and place your controllers/views under that area. Then, you don't need to do any other configuration.
