The document details a presentation on modernizing .NET applications using Docker, emphasizing the benefits such as consistency, portability, and isolation. It outlines steps for migrating applications to run in the cloud and production environments, highlighting specific configurations and tooling. Next steps include migrating as-is or adapting to new paradigms, ensuring improvements in various technical aspects such as monitoring, logging, and scaling.

1. Modernizing .NET Apps
@IrisClasson
Konstrukt
@EltonStoneman
Docker, Inc.

2. Agenda
Docker on Windows
Chat! – the Demo App
- Moving to Docker
- Running in the Cloud
- Running in Production
Modernizing .NET Apps
- The Spectrum
- Next Steps

3. Docker on Windows

4. sqlservr.exe
dotnet.exe
w3wp.exe

5. But Why?
●Consistency
●Portability
●Isolation
●Size
●Startup-time
●Rollback
●ROI
●Tooling & YOU

8. FROM microsoft/aspnet:windowsservercore
COPY UpgradeSample-1.0.0.0.msi /
RUN msiexec /i c:UpgradeSample-1.0.0.0.msi RELEASENAME=2017.02 /qn

9. # escape=`
FROM microsoft/windowsservercore
SHELL ["powershell", "-Command"]
RUN Add-WindowsFeature Web-server, `
NET-Framework-45-ASPNET, Web-Asp-Net45; `
Remove-Website -Name 'Default Web Site'
COPY ProductLaunchWeb /product-launch-web
RUN New-Website -Name 'product-launch' `
-PhysicalPath 'C:product-launch-web' -Port 80
EXPOSE 80
COPY bootstrap.ps1 /
ENTRYPOINT ./bootstrap.ps1

11. Chat!
The Demo App

12. “hi!”
AuditDB

13. “hi!”
AuditDB
BackplaneDB

14. “hi!”
AuditDB
BackplaneDB

15. > demo

16. “hi!”
BackplaneDB
AuditDB
WAF

17. Next Steps

18. Migrate
as-is
Adopt
platform idioms
Adapt
to new runtime
Extract
key features
Rebuild
and renew
• Configuration
• Monitoring
• Logging
• Fault-tolerance
• Scaling
• Statelessness
• Peformance
• Functionality
• Fast updates
• Architecture
• Tech stack
• Paradigms
• Binaries
• Setup
• Artifacts

19. @EltonStoneman
Thank you!
@ IrisClasson