Common mistakes designers make and how to fix them
When you reference a .js framework or library from your ASP.NET application, it makes sense to use the development version when you’re working on your own machine.
Referencing the development versions brings more useful error messages and integration with the React Developer tools.
But, you wouldn’t want to use these in production for performance reasons.
When you run the site in production, you’d want to reference the minified production versions of the React scripts.
Also have a look at OWASP Top 10 Most Critical Web Application Security Risks: https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project
Logging information in .NET, or really in any production application, is invaluable. In many cases, developers don’t have direct access to the production environment to debug issues. Good quality logs are the difference between solving problems like Sherlock Holmes and stumbling upon solutions like Inspector Jacques Clouseau. As you can imagine, we’re pretty big on logging here at Stackify, and we’ve written quite a few other blog posts on .NET logging frameworks. I’d encourage you to try out the search and read a few of our previous articles.
Razor views are dynamically compiled by the ASP.NET runtime. If you want your views to be built at compile-time you could add the following option to your .csproj file:
You may take a look at the this article for more details.
Set up SSH with Sourcetree on Windows
Are you annoyed by the default project location in Visual Studio? Check out this tutorial and learn how to modify it to suit you needs.
I’m getting, “Could not load file or assembly ‘Bla’ or one of its dependencies. An attempt was made to load a program with an incorrect format.”
Login to azure portal
Goto your web app
Select the tab “Deployment credentials” and set username and password to be used for FTP access. (remember to save).
Goto the “Overview” tab (the top tab)
In the right column you find: