The "creating-a-starter-project" guide here:
https://world.episerver.com/documentation/developer-guides/CMS/getting-started/creating-a-starter-project/Says you can just create an empty start project, login with windows credentials, and start creating pages.
However, this seems to be far from the truth, at least for users who are on a domain (who's windows user is not a local admin), i.e. anyone in a corporate network.
After intalling VS, episever plugin and nuget, you can create for example an "alloy MVC" site. This prompts to create a user which it ads to its Asp.Net.Users table. you can hit localhost:xx/episerver and login with this user to edit the site.
This is great, but to learn episerver, the docs say to create an empty site, and create a page.
So I created a new episerver project of type "empty" instead of Alloy. You can run this ok, but when you hit localhost:xx//episerver, the user you created for alloy does not work. As we dont have local admin access to our machines (we are on a domain), it is implossible to login.
In fact, the database it creates for the empty site does not even have a Asp.Net.Users table.
The only workaround seems to be to create a user programatically, by creating a file called "EpiserverInitialization.cs" which contains the code someone kindly put together to create an account.
However, when you try to login with this account, you get the error "No owin.Environment item was found in the context.". It seems that the empty project is missing the "startup.cs" file which is required.
So getting an empty project working seems to be extremely difficult, and not documented.
What am I missing?
Has anyone managed to get an emtpy site working?
if so, how did you get around not being able to create users, and the missing owin/startup stuff?
Could some kind sole put together a guide on how to create an empty site, including the account creation, owin, startup and any other missing critical items? So far, as a new episerver user, I have not managed.