Cacher is the code snippet organizer for pro developers

Today I built a CRUD app hosted in IIS

Lessons learnt:

- Needed to install a package for hosting .NET Core 3.1 applications
- Turning off verbosity in output and logger massively increased build/publish speed
- Localhost connection strings still require the appropriate IIS APPPOOL\[app pool name] SQL server login
- Don't bother with Azure - the pain of connecting to SQL remotely is not worth it (unless deploying using CE)
- appsettings.production.json is used when publishing as release
- Cannot see a difference setting the Application Pool from No Managed Code to the v4.0 CLR.  However No Managed Code is recommended
- Using .NET Core only sends the JSON data via AJAX so much more responsive than WebForms
- Use RazorPages to stay close to WebForms in terms of design
- CRUD much easier to develop as simply need to return results as DataSourceRequests and DataSource Responses
- Make sure to use this boilerplate as the manual set up takes a long time
- More difficult to debug SQL errors as the response will simply return a 404 error
- Using the Framework Dependent results in a much smaller publish size.  However Ready to Run and single file allows us to precompile at the expensive of publish time
- Set the global culture by using Kendo JS culture file and also inserting a snippet in the Master Page (known as _Layout), but do not use the culture formats (e.g. "d").