Change Log is here:
<a class="postlink" href="https://aspnetzero.com/Documents/Change-Logs">https://aspnetzero.com/Documents/Change-Logs</a>
Several deployment questions: I understand how to deploy the non-merged version... but what about the merged version?
So if we are deploying the merged version of Angular/.NET Core then how does deployment to Azure differ?
Do we still need two urls and two instances of Azure App Services??
Do we still need to update with NSSwag from the command line when we add new services? Still need to npm build -prod the angular portion? Or does that get done by the build scripts automatically in the merged version?
It is confusing how the workflow is different comparing the merged and not-merged solutions.
@alper THANK YOU!
Actually I have jTable example CRUD now finally working for an issue tracker app. At least for basic fields, still need add in User better, and connect in Actions on Issues. I think this would make a great tutorial / learning app. I volunteer to write an extensive tutorial and contribute the code back to AspNetZero examples github repo if ANZ developers will review it and suggest changes for best practice - because I am probably not doing it the best way. And ANZ developers might also need to answer a question or two offline via email for me to get it done... else then such a tutorial could make it a lot easier for future newbies (-:
Would there be interest in that?
I would like to bring attention to this request once again. Between Boilerplate, Module Zero, and AspNet Zero -and given the examples generally use custom DTO's (e.g. Users) and Managers inherited from ABP, and simple Dto's versus FullAuditedEntity DTO's, Stores??? where Stores documented??? etc etc etc. -- the level of complexity and different ways to do it is a lot for a newbie to handle.
I cannot get a simple CRUD app using jTables up and going - something like the Users jTable pages but that doesn't have to have a UserManager and what is UserStore?? and Roles, Editions same complexity. Granted I am C# and ASP.NET newbie, but I have many years experience with Django/Django REST Framework/ Angular 1 successfully building significant web apps. More tutorials and documentation is needed more than more new ANZ features.
And while the Users/Roles etc examples are complex, they also don't show how to connect in those things.
So this is what is needed:
jTable views like with User - of a ToDo app. ToDo should NOT connect to new Persons model, but instead to real, authenticated application Users. Full audited entities should be used. Then show how to use CreateOrEdit modals to get full CRUD, including Update, of ToDo items that include the User who created them. Show how to use FullAudited Dtos too - Users/Roles/Editions don't even use the FullAudited functionality, right?
@ alirizaadiyahsi Thank you!
So issue fixed to make it fully open in VS. When I try to do next step:
C:\Code\Research1\aspnet-core\src\Research1.EntityFramework>dotnet ef database update The specified framework 'Microsoft.NETCore.App', version '1.1.0' was not found.
more issues... where would I specify 1.0.1 instead of 1.1.0? or specify a preview release instead of 1.1.1 straight up?
sigh.
More info in case others have the same issue:
<a class="postlink" href="https://github.com/aspnet/Tooling/blob/master/known-issues-vs2015.md#missing-sdk">https://github.com/aspnet/Tooling/blob/ ... issing-sdk</a>
Helps a ton! Thanks!!
Well update... looking at example code for Users or Editions or Friendships, I see they work somewhat differently. Instead of having a repo object that is queried via Linq? they have an additional concept of a Manager. Like UserManager.
Is there somewhere this is documented? The detailed how to documents for each of the different starting apps don't seem to talk about Managers.
