Hosting applications on Windows Azure is simple but there are things to change when cloud-enabling existing web applications because cloud is conceptually different than on-premises or shared hosting environment. This sessions goes through main issues one will face when moving applications to cloud. Real-life examples provide elegant solutions to problems and through demos the audience will see how to deploy applications to cloud and how to test and run cloud and hybrid applications on your development machine.

1. Porting ASP.NET applications to
Windows Azure
Gunnar Peipman
ASP.NET/IIS MVP

2. About me
• Name: Gunnar Peipman
• Job: Chief Everything Officer
• Company: Peipman Consult
• Hobbies: Coding, reading,
travelling, cooking, beers, heavy
metal music
• MS: ASP.NET MVP (since 2008)
• Community: ENETA
• Blog: gunnarpeipman.com
• E-mail: me@gunnarpeipman.com

3. Agenda
• Windows Azure services
• Problems with classic web applications
• Think different
• Sample solutions
• Demo
• Q&A

4. Windows Azure services

5. Windows Azure services
Web Sites
Virtual
Machines
Mobile
Services
Cloud
Services
SQL DB Storage
Media
Services
Service
Bus
Cache

6. Application types
• In-premises: we host everything on our servers
• Cloud: everything is hosted on Windows Azure
• Hybrid: mix of cloud and in-premises

7. Problems in classic web
applications

8. Local files
• Direct use of local directories to keep files
• File system support is hardcoded to application
• Not proper use of temporary files
• Using folders above web application root

9. Local database
• Systems of developed and tested using SQL Server on
development machine
• Database is located in network but not much test data is
available

10. In-proc and local data
• Session data is kept in server memory
• Cache data is kept in server memory
• Some shared data is kept in static variables

11. Think different

12. Change in mindset
• Your code must work in multi-server environment
• There will always be network
• Instead of modules there are pluggable components
• Everything can be service

13. Breaking dependencies
• Most of the work you do is breaking dependencies
• While breaking dependencies you make generalizations
• You move to modularized code
• You make it easier to test your code

14. Sample solutions

15. Generalizing file storage
• Local file system: paths up to 248 chars
• Blob Storage: account -> container -> blob
• Other services:
o Amazon
o OneDrive
o Google Drive
o SharePoint
• Considering all those limits try to get things done 

16. IFileClient interface

17. IFileClient interface

18. ILogger interface

19. ILogger interface

20. Sessions and cache
• Stop using in-proc session and cache
• Use SQL Server or some distributed cache
• Test for performance and monitor traffic
• If needed ask session values once per request

21. Demo: Hybrid applications

22. Upcoming events
UXify Bulgaria, June 7
Sessions, training day and more
http://uxify.org/
SQLSaturday #311 in October!
http://www.sqlsaturday.com/311/
jQuery Bulgaria, November 22
http://www.jquerybulgaria.com/

23. Thanks to our Sponsors:
Global Sponsor:
Gold Sponsors:
Swag Sponsors: Media Partners:
More Global Sponsors:
Silver Sponsors: