Visual Studio 2017 StyleCop Analyzers template for .NET Core

With the new Visual Studio 2017 out you might have been busy upgrading your .NET Core solutions to the new format and accidentally found out that StyleCop Analyzers stopped working? Automated upgrade will just upgrade projects, however will not adjust Visual Studio 2017 StyleCop Analyzers settings. Therefore, I’ve updated my template’s source code and added this quick guide.

Continue reading Visual Studio 2017 StyleCop Analyzers template for .NET Core

Migrate away from Facebook app to Disqus comments

I was helping one old university project and as part of user experience and SEO tweaks we decided to move away from Facebook app comments to Disqus comments. The main reason was problems with comments/replies not appearing on the website, and on top of this we wanted to boost SEO having comments that could be indexed by search engines.

disqus comments

Continue reading Migrate away from Facebook app to Disqus comments

Clean and shrink SQL database

Sometimes you need to clean and shrink SQL database, since once database grows even if all records get deleted, the database file would still take the space as before clean up. To achieve this we can manually delete records and call SHRINKFILE command. However, it’s important to delete records in small batches in transaction not to clog up the database server.

Continue reading Clean and shrink SQL database

Swashbuckle and Swagger for .NET Core 1.0 validator issue

I’ve decided to write this blog post when I came across an issue with Swashbuckle trying to validate JSON file in Swagger and was failing since Swagger’s online validator was trying to fetch JSON file from an development server which is not accessible from external networks.

Swashbuckle-swagger-error

Continue reading Swashbuckle and Swagger for .NET Core 1.0 validator issue

.NET Core projects with StyleCop Analyzers

Different developers have different coding styles, however when you work as a team you want to make sure everyone can quickly pick up any part of code and could get their head around in no time. For this reason, it’s great when code has unified style. This can be done manually (not recommended :)) or by using code analyzers in Visual Studio. Default set of rules check for the most common issues, however do not keep the coding style itself unified. Therefore, such tools like StyleCop Analyzers become really handy in such cases. Continue reading .NET Core projects with StyleCop Analyzers