Beginning .NET Core development with docker for windows

-

Step 1:

Open up visual studio and add your .Net Core app. Here, I have created an MVC application on .NET Core 2.0. Also I have Docker for Windows (Community Edition) installed in my machine.

Step 2:

Add a file named "Dockerfile" or any custom name of your preference to the project directory. Below is sample content of the docker file to build docker image of a simple MVC app. More details about Docker commands: https://docs.docker.com/engine/reference/builder/.

# Use dotnet sdk as base image for building this app
FROM microsoft/dotnet:sdk AS build
# create and move into directory named 'app' in the destination container
WORKDIR /app
# Copy csproj file into the app directory
COPY *.csproj ./
# Restore all required packages
RUN dotnet restore
# Copy everything else into app directory
COPY . ./
# Build the project and publish the artifacts into 'out' directory
RUN dotnet publish -c Release -o /out
# Build runtime (final) image
FROM microsoft/dotnet:runtime AS runtime
WORKDIR /app
COPY --from=build /out .
# Specify the entry point to this app
ENTRYPOINT ["dotnet", "docker-demo.dll"]
view raw Dockerfile hosted with ❤ by GitHub

Step 3:

Add docker support to the app from Project menu. It will add a new docker-compose project to the solution.

























Set the new project as startup project for debugging. Here is a snapshot of how it should look like:
























Step 4:

Update the contents of docker-compose.yml and docker-compose.override.yml. Below are sample contents from the example app (dockerfile command can be skipped if default filename is used). More details about docker compose: https://docs.docker.com/compose/compose-file/.

version: '3.5'
services:
auth:
image: dockerdemo
build:
context: ../docker-demo
dockerfile: Dockerfile
container_name: docker-demo-container
view raw docker-compose.yml hosted with ❤ by GitHub

version: '3.5'
services:
demo:
ports:
- "8080:80"
environment:
- ASPNETCORE_ENVIRONMENT=Development
view raw docker-compose.override.yml hosted with ❤ by GitHub

Finally: 


Hit F5 to run the project and open up a browser with URL: http://localhost:8080/ (8080 is the port configured in docker compose file). And it your app should be running! 

You can right click on the docker-compose project to set the properties (ServiceName, ServiceURL etc.) so that every time you hit F5, it would start a new browser window with the application URL.


HAPPY CODING 👌

Comments

Post a Comment

Popular posts from this blog

Adding security headers to prevent XSS and MiTM attacks in .Net Core

-
Image
As a developer, we need to consider security when designing and building web applications. HTTP Response Headers allow server to pass additional information to instruct browsers how to handle sensitive data and content of the application and/or from external or untrusted sources. HTTP response security headers provide an extra layer of protection to help mitigating vulnerabilities and attacks. One way to add those security headers from .Net Core application is by writing a custom action filter that would be executed before serving any response from the application. Below is a example of the custom attribute: To apply this globally for all responses, we can add this to the Startup class as in below: To apply trusted source for any particular action: And here is the outcome: HAPPY CODING   👌
Read more

Microsoft.IdentityModel.Protocols.OpenIdConnectProtocolInvalidNonceException

-
I was using openId connect authentication with IdentityServer (v4) in a recent project and my client application was throwing following error: Microsoft.IdentityModel.Protocols.OpenIdConnectProtocolInvalidNonceException: IDX10311: RequireNonce is 'true' (default) but validationContext.Nonce is null. A nonce cannot be validated. If you don't need to check the nonce, set OpenIdConnectProtocolValidator.RequireNonce to 'false'. at Microsoft.IdentityModel.Protocols.OpenIdConnectProtocolValidator.ValidateNonce(JwtSecurityToken jwt, OpenIdConnectProtocolValidationContext validationContext) in c:\workspace\WilsonForDotNet45Release\src\Microsoft.IdentityModel.Protocol.Extensions\OpenIdConnectProtocolValidator.cs:line 332 at Microsoft.IdentityModel.Protocols.OpenIdConnectProtocolValidator.Validate(JwtSecurityToken jwt, OpenIdConnectProtocolValidationContext validationContext) in c:\workspace\WilsonForDotNet45Release\src\Microsoft.IdentityModel.Protocol.Extensions\OpenIdCo...
Read more

Executing synchronous methods asynchronously

-
We can achieve certain advantages by writing asynchronous methods. It's pretty simple to write them in C# code: we just need to use  async  and  await keywords properly. Grammar of these keywords can be found in detail in MSDN . In this post I will try to focus on writing few code to invoke a regular synchronous method asynchronously. Let's assume a scenario where we need to perform an expensive database operation when a particular information is changed from the front end. For example: I have an application to manage employee information and I've changed the basic salary for a particular grade using my application. Now I need to update salary of all the employees under that grade. The later operation will be slower one and I don't want this to block me from doing other stuffs. Here is a piece of synchronous code to update salary information: public   bool   UpdateEmployeeSalary ( string   grade ) {      try  ...
Read more