I just wanted to say thank you, Tim. Three years ago, I wrote my first line of C# code. Today, I am working as a full-time software developer, and your videos and tutorials have been fundamental in my learning journey. I could not be happier! Thank you!
@@IAmTimCorey Thanks. Also expecting one full video on Blazor Class library. Can we create component library with page and code behind which we can reuse from nuget.
And how are you supposed to know about that Jammy-chiselled nonsense? Is it something that's documented somewhere as to what the options and included base images are?
Hello Tim, I am wondering if there is a need of Docker in development phase for .NET. I never faced a situation where a project was running fine in X machine but not in Y. The only need of docker during development phase i think is if you need components like Redis etc (so you don't have to install them in your PC). I am a bit confused of purpose of docker. It is more for development or for hosting/running applications after the deployment?. Because all the time i tried to use docker during development it make me slower. And if it works on my machine it will probably work in any other machine with .NET SDKs.
There are huge benefits to using Docker in development. First, it is first-class at setting up environments just like production very quickly. For instance, I can set up a SQL Server and deploy my database scripts to it in less than 2 minutes. Then, when I'm done, I can tear it all down. Second, you can more easily do integration and end-to-end testing by having your test suite spin up new containers, deploy the database, redis, etc. and then perform tests on it. Integration tests can actually fully reset the environment between tests in order to ensure a clean test every time. Third, we should have our development environment mirror production as closely as possible. That's why web projects now use https. It isn't for security on your own machine. It is because web apps can sometimes behave differently with http compared to https and we will be using https in production. In the same way, our applications may be deployed in containers in production. Therefore, we deploy them into containers on our dev machines in order to test our systems before pushing to central dev (or worse, production). Using containers in production allows us to deploy more safely and it allows us to scale more easily. These are just some of the reasons why Docker is so valuable in development.
I use Windows Terminal. I've tweaked it with Oh My Posh. Here is a post that will help explain tweaking the Terminal: www.hanselman.com/blog/taking-your-powershell-prompt-to-the-next-level-with-windows-terminal-and-oh-my-posh-3
The docker course is very basic, most are. There needs to be a course that teaches you how to setup docker for a full .NET project to use docker compose and actually run and debug the code as well as docker for integration testing and UI testing. There is literally no point in learning docker unless it full scope of how you would use it professionally.
My actual Docker course (not just my videos here on RUclips) does go into a lot of detail on how to use Docker. However, what you are talking about is one specific use case, not the only way to use it professionally. If you have specific suggestions (like Docker compose or integration testing with Docker), you can put them on suggestions.iamtimcorey.com for others to vote on.
Ok, do they go into detail on how to a docker compose project inside visual studio to debug, setup multiple services and have them depend on each other with health checks etc, how to setup the frontend and backend to talk to each other and how to setup integration testing of an API and UI and how to include docker in the ci/cd pipeline and deploy to azure from github or azure devops? I am asking because that would awesome if it did @@IAmTimCorey
@@IAmTimCorey The main way docker is used professionally is docker compose. It would be nice to have a course that taught you how to use a docker compose project in visual studio and setting up a frontend, backend and db with ssl as well as integrating docker with ci/cd and integration testing for api and ui
I don't have that specific configuration in a video, but you could add it to the suggestion site. As for the most common way to use docker is with Docker Compose, I don't know that this is true. You can use multiple containers without using compose.
@@IAmTimCoreyfair point, but there are probably similar concepts just different names? You could choose the most popular and do a series on how to work with that from small mvc app to full scale micro services or even modular monoliths?
MISSING important things. How to access storage? Let's say i want to container my Website.. how to access wwwroot? where temp files like session data is created?
That's well outside the scope of this 10-minute tutorial. That's a deeper Docker discussion and one that probably takes a better understanding of how Docker works first. For example, you really don't want to store things in wwwroot that aren't a part of the container. For instance, image files associated with your website can be stored in wwwroot, and can be accessed with relative paths like normal. However, if users are uploading files, those should be stored in another location like cloud storage. The reason is because containers are meant to be scaled. If your host creates five containers off of your image, and a user uploads a file to one of them, the other four won't have access to that image. Now, if you are talking about doing this locally, you can set up your dockerfile to map a folder from your local disk into the container.
Think of containerization as "running the app on a virtual machine". A container is a small VM, with everything that's not essential stripped down. That's why you see in the video, Tim is publishing his app for Linux, even though he runs Windows. The goal is making development and deployment easier. And it's not only for your app, it's for the dependencies. Normally, with local development you had to install a database, maybe RabbitMq locally. What if you work with apps, one uses the latest version of Postgres and one uses an older version? That's when running the mini-VMs becomes handy.
Another huge benefit of containers is the ease of scaling. You can easily scale up to 100s or 1000s of instances to meet demand. Also you can easily automate scaling the number of instances up or down based on traffic.
Containerization makes configuration and deployment easy. If it works locally, it will work in the cloud. This allows you to be able to easily deploy your app to an Azure Web App, then move it over to a container service for scaling for instance. It also allows you to easily have an application that will always run at that point in time. There are a LOT of reasons to use containers.
I just wanted to say thank you, Tim.
Three years ago, I wrote my first line of C# code. Today, I am working as a full-time software developer, and your videos and tutorials have been fundamental in my learning journey. I could not be happier!
Thank you!
Fantastic! I’m glad my content had a part in your journey. Well done!
For anyone struggling Docker containerization is a steep learning curve. But once you get it, it is very easy.
Here is training on Docker to get you up to speed: ruclips.net/video/WcQ3-M4-jik/видео.htmlsi=Fq1uL6k489YgprAm
This is the perfect tutorial I wanted - Docker and C# - thanks!
You are welcome.
perfect, exactly what I needed to get me going on docker.
Excellent!
Thank you Tim for all your amazing youtube content!!
You are welcome.
This is very useful video we need more videos like this "docker with dotnet"
Thanks for sharing!
Thanks Tim, explanation is clear and simple.
You are welcome.
Thanks, Master, for showing us new things and keeping us inspired.
You are welcome.
Amazing content, great explanation
Thank you.
Thanks Tim
You are welcome.
Is there a way to add this command to Docker Compose, or do I still need a Docker file to build multiple projects?
Good day Tim. Can I please request a tutorial for implementing 2 factor authentication for .NET Blazor applications?
Thanks for the suggestion. Please post it at suggestions.iamtimcorey.com so others can vote on it.
Hello Tim,
I'm just curious, what cmd extension are you using in command prompt
OhMyPosh with some tweaks.
Thanks Tim, do I have to install a dependency to use Container family? It is not reducing the image size when I use in my app.
No, you do not. My guess is that you got the syntax slightly wrong, which caused that flag to be ignored.
That's really helpful. I request what's your view on No code low code platform like Salesforce or Power Platform. If you can.
Here you go: ruclips.net/video/ah1tEvAkojI/видео.htmlsi=NYOGPCFiR098jAl6
@@IAmTimCorey Thanks. Also expecting one full video on Blazor Class library. Can we create component library with page and code behind which we can reuse from nuget.
You can add that suggestion to suggestions.iamtimcorey.com
i didnt kno you could shrink it..great viddeo
I am glad it was helpful.
And how are you supposed to know about that Jammy-chiselled nonsense? Is it something that's documented somewhere as to what the options and included base images are?
They are all published here: hub.docker.com/_/microsoft-dotnet-runtime/
@@IAmTimCorey Thanks! My knowledge is 15 years out of date and I'm slowly playing catch-up. So much to learn, but your videos are much appreciated.
Yep, that can be overwhelming, but chipping away at it will get you there. I’m glad my tutorials have been helpful to you.
Hello Tim,
I am wondering if there is a need of Docker in development phase for .NET. I never faced a situation where a project was running fine in X machine but not in Y. The only need of docker during development phase i think is if you need components like Redis etc (so you don't have to install them in your PC).
I am a bit confused of purpose of docker. It is more for development or for hosting/running applications after the deployment?. Because all the time i tried to use docker during development it make me slower. And if it works on my machine it will probably work in any other machine with .NET SDKs.
There are huge benefits to using Docker in development. First, it is first-class at setting up environments just like production very quickly. For instance, I can set up a SQL Server and deploy my database scripts to it in less than 2 minutes. Then, when I'm done, I can tear it all down.
Second, you can more easily do integration and end-to-end testing by having your test suite spin up new containers, deploy the database, redis, etc. and then perform tests on it. Integration tests can actually fully reset the environment between tests in order to ensure a clean test every time.
Third, we should have our development environment mirror production as closely as possible. That's why web projects now use https. It isn't for security on your own machine. It is because web apps can sometimes behave differently with http compared to https and we will be using https in production. In the same way, our applications may be deployed in containers in production. Therefore, we deploy them into containers on our dev machines in order to test our systems before pushing to central dev (or worse, production).
Using containers in production allows us to deploy more safely and it allows us to scale more easily.
These are just some of the reasons why Docker is so valuable in development.
what for shell are using? and how is configured:)
I use Windows Terminal. I've tweaked it with Oh My Posh. Here is a post that will help explain tweaking the Terminal: www.hanselman.com/blog/taking-your-powershell-prompt-to-the-next-level-with-windows-terminal-and-oh-my-posh-3
@@IAmTimCorey I think i have done it somewhere in the past once, unfortunately i do not have it any more:(, thanks a lot
The docker course is very basic, most are. There needs to be a course that teaches you how to setup docker for a full .NET project to use docker compose and actually run and debug the code as well as docker for integration testing and UI testing. There is literally no point in learning docker unless it full scope of how you would use it professionally.
My actual Docker course (not just my videos here on RUclips) does go into a lot of detail on how to use Docker. However, what you are talking about is one specific use case, not the only way to use it professionally. If you have specific suggestions (like Docker compose or integration testing with Docker), you can put them on suggestions.iamtimcorey.com for others to vote on.
Ok, do they go into detail on how to a docker compose project inside visual studio to debug, setup multiple services and have them depend on each other with health checks etc, how to setup the frontend and backend to talk to each other and how to setup integration testing of an API and UI and how to include docker in the ci/cd pipeline and deploy to azure from github or azure devops? I am asking because that would awesome if it did
@@IAmTimCorey
@@IAmTimCorey The main way docker is used professionally is docker compose. It would be nice to have a course that taught you how to use a docker compose project in visual studio and setting up a frontend, backend and db with ssl as well as integrating docker with ci/cd and integration testing for api and ui
I don't have that specific configuration in a video, but you could add it to the suggestion site. As for the most common way to use docker is with Docker Compose, I don't know that this is true. You can use multiple containers without using compose.
@@IAmTimCoreyfair point, but there are probably similar concepts just different names? You could choose the most popular and do a series on how to work with that from small mvc app to full scale micro services or even modular monoliths?
👍
👍
MISSING important things. How to access storage? Let's say i want to container my Website.. how to access wwwroot? where temp files like session data is created?
That's well outside the scope of this 10-minute tutorial. That's a deeper Docker discussion and one that probably takes a better understanding of how Docker works first. For example, you really don't want to store things in wwwroot that aren't a part of the container. For instance, image files associated with your website can be stored in wwwroot, and can be accessed with relative paths like normal. However, if users are uploading files, those should be stored in another location like cloud storage. The reason is because containers are meant to be scaled. If your host creates five containers off of your image, and a user uploads a file to one of them, the other four won't have access to that image.
Now, if you are talking about doing this locally, you can set up your dockerfile to map a folder from your local disk into the container.
Huge container at 221MB... Playing around with AI and the CUDA containers that's up to 22 GB each :) Cheers!
Yeah, AI containers can be really large.
But why do you need to containerise .Net applications in the first place, I thought .Net was open source and cross platform?
Think of containerization as "running the app on a virtual machine". A container is a small VM, with everything that's not essential stripped down.
That's why you see in the video, Tim is publishing his app for Linux, even though he runs Windows.
The goal is making development and deployment easier. And it's not only for your app, it's for the dependencies.
Normally, with local development you had to install a database, maybe RabbitMq locally. What if you work with apps, one uses the latest version of Postgres and one uses an older version? That's when running the mini-VMs becomes handy.
Another huge benefit of containers is the ease of scaling. You can easily scale up to 100s or 1000s of instances to meet demand. Also you can easily automate scaling the number of instances up or down based on traffic.
@@achavis ya and have you ever actually scaled to 1000 instances?
Containerization makes configuration and deployment easy. If it works locally, it will work in the cloud. This allows you to be able to easily deploy your app to an Azure Web App, then move it over to a container service for scaling for instance. It also allows you to easily have an application that will always run at that point in time. There are a LOT of reasons to use containers.