Today we finally deployed our client's updated ASP.NET Web Forms app, now with a Content Security Policy that blocks unsafe-inline JavaScript! 🥳
Wrangling ASP.NET was fun, but I'm happy to see this little project finished. It's the busiest I've been in a long time.
And here are some goals for work for 2023:
* Fully migrate away from #AspNetWebForms to #AspNetCoreMVC REST APIs and #Vue.
* Implement #Docker and #CICD to streamline our product development and deployments.
* Start moving the business logic out of #SqlServer database stored procedures and into a proper Business Logic Layer.
Welp, 2022 is over. It was a really productive year. Some personal achievements:
* Rewrote my calculator app, Replicalc, in #Go
* Got my #motorcycle license after putting it off for years
* Updated a work client's 150,000+ line #AspNetWebForms app to block unsafe-inline #JavaScript via #csp, and implement other modern web best practices
* Got my OG #RuneScape account back after it was stolen (https://dheinemann.com/posts/2022-04-02-how-my-runescape-account-got-stolen)
Looking forward to 2023!
Wrapped up implementation on a massive piece of work today: updating a 150,000+ line ASP.NET Web Forms codebase to support a Content Security Policy and block unsafe-inline JavaScript.
This has been a massive piece of work, especially because Web Forms generates and adds its own unsafe inline JavaScript at runtime!
Here's how we did it.
(continued)
Lots of folks have recently asked me about migrating from Web Forms to Blazor and what steps they need to take. There is actually an entire free eBook on this! Check it out https://docs.microsoft.com/dotnet/architecture/blazor-for-web-forms-developers/ #dotnet #aspnetcore #blazor #aspnetwebforms
