1629208800
While migrating the elmah.io app to ASP.NET Core, I had to re-implement the always signed in feature available to elmah.io users. In this post, I'll share how I implemented this and the findings I discovered on the way.
#azure #aspdotnet
1629201600
Most parts of elmah.io consist of small services. While they may not be microservices, they are in fact small and each do one thing. We recently started experimenting with ASP.NET Core for some internal services and are planning a number of blog posts about the experiences we have made while developing these services.
#aspdotnet
1628867767
While migrating our web app to ASP.NET Core, I had to find a new way for the user to upload and resize a profile photo. We used the WebImage class in ASP.NET MVC, which unfortunately isn't available in Core. In this post, I will show you how I solved it using file support in ASP.NET Core and the ImageSharp library.
1628854315
To help debug what is turning sideways, I created a quick request logging feature in ASP.NET Core. There are multiple posts on the subject already, but while most of them are really good posts, they often cover too much for my simple use case or leave out essential information about how to create the configuration. I simply want a log message for each request, with as little information as possible, but enough for me to be able to correlate the generated error with an HTTP request.
1628661079
In this virtual age, companies are moving online to have a aggressive facet over their competitors. But Performance of an software is one of the pivotal parameters for the fulfillment of your software. Regardless if you’re an ASP.NET internet developer or a enterprise proprietor who desires to construct a fast, robust, secure, and interactive internet software, you ought to comply with the great practices. Let’s communicate approximately the pinnacle 10 great practices in ASP.NET internet-primarily based software development. Read more here: https://thecompetenza.com/asp-net-best-practices/
#aspdotnet #aspnetdevelopment #aspnetbestpractices #dotnetdevelopment
1628654377
In previous shows, we've seen simpler REST services with the new minimal APIs in ASP.NET Core 6. How would that approach apply to web apps? Come join us as Damian Edwards shows some experiments in building web apps with minimal code APIs.
#dotnet #aspnetcoder #aspdotnet #webdev #api #webapp
1628596651
ASP.NET Core 2.2 introduces a range of new features. One of the more interesting (IMO) is Health Checks. You may use tools like Pingdom or elmah.io Uptime Monitoring to ping your website in a specified interval. Pinging a single HTML page may or may not reveal if your application is healthy or not. Health Checks to the rescue! Before trying out the code yourself, make sure to install the recent version of ASP.NET Core 2.2 and Visual Studio 2017.
1628595036
Three years ago I wrote a tutorial about security headers in ASP.NET MVC. A lot happened since then and ASP.NET Core is the framework everyone should be on eventually. Time for an updated version for Core! This post is part of the series ASP.NET Security.
I'll try to recap the different security headers in the post. If you are interested in more context, check out the original post. I'll go through each header like in the last post, but let's start by discussing how to modify headers in ASP.NET Core. Like ASP.NET (MVC) there are multiple ways of modifying headers. This post introduces two different ways:
1628571600
In this recent post in our Learn about .NET series, I'll present you with a list of books that I've read or got recommended from developer friends.
1628569800
We look to see how you can list and test all your endpoints in your ASP.NET Core Web API with Swagger.
This is a good alternative if you are used to using Postman to test out your ASP.NET Core Web API endpoints.
First, we will go ahead and install the Swashbucket.AspNetCore package into our ASP.NET Core Web API application. In addition, we will also add the necessary configuration changes to get the Swagger documentation working.
Next, we look at how we can change where the Swagger documentation is located in our application. Normally, Swagger is located at /swagger, but we look at moving it to root level.
Afterwards, we look at ways for adding comments to our endpoints in the Swagger documentation. Comments are good if you want more of an explanation as to what each endpoint does.
Finally, we look at ways to remove certain API endpoints from the Swagger documentation. This is beneficial if you want API endpoints to be hidden from view.
► More Information: https://www.roundthecode.com/dotnet/asp-net-core-web-api/test-your-endpoints-inside-your-asp-net-core-web-api-app-with-swagger
#aspnetcore #swagger #webapi #aspdotnet
1628460000
Building .NET 6, C# 10 minimal web APIs and deploying them continuously in Azure App Service using Azure DevOps Pipelines.
#azure #aspdotnet
1628449200
datatable asp.net core, jQuery DataTable CRUD ASP.NET Core Entity Framework Core Web API Example.
#aspdotnet #api
1628445600
ASP.NET Core MVC Image Photo Update Display Read Retrieve EF Core SQL Server Example. Upload Retrieve image asp.net core ef core sql server.
#aspdotnet #sql
1628438400
BULK Entry ASP.NET Core Example BulkInsert BulkSave BulkUpdate BulkDelete BulkMerge CRUD Operation.
#aspdotnet
1628434800
DataTable BULK Entry ASP.NET Core Example BulkInsert BulkSave BulkUpdate BulkDelete BulkMerge CRUD Operation.
#aspdotnet