2. Reversed the order of registration of Environment source & json source as the logic for source override changed.
3. Taking a snapshot of the latest packages.
Removing all code related to External login from Account controller.
I also added a little ugly work around to initiate a static UserManager for testing purpose. This should go away shortly.
With this change user can register a user, login & logout.
1. Adding cookies middleware to the music store app
2. Enabling login, register & related management pages to render some UI for testing
3. Updated the LKG.json
Specifying just the name of the file works fine on selfhost or IISExpress. When app is hosted in IIS, Config.json is being searched in the w3wp3.exe's folder path resulting in an exception.
So fixing the path of Config.json by retrieving the application base path from AppDomain.
If the same set of values (those present in config.json) is present in the environment variables
then ones from environment variables be picked up. This will be the antares scenario where the portal variables
flow in as environment variables with a specific prefix.
1. Adding a view component
2. Adding more partial views from the sample and enabled a few of them.
3. Updating Account controller to accomodate all the recent identity changes.
4. Enabling some available Url helpers like Url.Content
5. Adding a ~ to all the scripts and images as this bug is fixed now.
1. Removing copyright text from all files per a code review feedback
2. Adding a cookie based session to the application to retrieve the cart Id.
3. Enabled the Accounts controller as we now have the necessary Http abstractions for User, SignIn, SignOut etc.
4. Changing self hosting scripts to run on coreclr by default.
5. Enabling the layout page on all required views.
6. Adding a favico.ico
7. Renaming the Cart property in the EF context to CartItems as it returns a CartItems list.
8. Uncommenting some code which was previously accessing unavailable APIs. They are available now (but yet to validate them).
The code that does an 'UPSERT' of seed data on app start was querying
existing instances and attaching as modified of seed instances on the
same context. Now that we track query results this will throw because
the context has two instances of the same entity (same key value).
Swapping to use a temporary context to query existing data.
Praburaj
David Fowler
Hao Kung
ajcvickers
rowanmiller
Pranav K