I created this technical article for Signals company in cooperation with their marketing team and the original post is published on Signals Tech Blog.
I created this technical article for Signals company in cooperation with their marketing team and the original post is published on Signals Tech Blog.
Many of us use the async/await feature in C# projects, as we know the benefits of asynchronous programming related to IO bound operations. But did you ever look under the hood to check what's going on in your app's threads?
Programming an application with Entity Framework and Code First does not mean you won't write any raw SQL anymore. C# code is great for the basic CRUD operations, but as the application grows, there are cases when you need to write complex queries containing various joins (on multiple columns) and aggregate functions
One of the best books I've read about agile methodologies and agile design, or better said, about the software design in general.
When you're working on an application which uses some sort of database, there is always a point when you need to test some functionality directly on the database server - e.g. complex LINQ queries, transactions handling etc.
Hosting an ASP.NET app in IIS has its benefits. However, the consequences of on-demand loading and app pool recycling actions are sometimes undesirable. One of them is that after the app pool has been recycled, the application is not initialized until some user hits it.
Most of you know the Dependency Inversion Principle (DIP) and use abstractions when designing modular, flexible and maintainable systems. But do you have your abstractions defined in the correct layers?