Cloud Cover Episode 18 - ASP.NET Providers
- Posted: Jul 09, 2010 at 9:52 AM
- 37,537 Views
- 3 Comments
Join Ryan and Steve each week as they cover the Microsoft cloud. You can follow and interact with the show at
@cloudcovershow
In this episode:
In this episode:
- Learn how to configure and hook-up the ASP.NET providers in Windows Azure web applications.
- Learn about the differences between using the Windows Azure table provider and the SQL Azure provider.
- Discover a tip on how to locally use the providers (and table storage) in the development storage service.
Show Links:
Layered Architecture for Windows Azure
Introducing the Archivist
Windows Azure AppFabric July Release
ASP.NET Provider Scripts for SQL Azure
PhluffyFotos
Using the Sample Windows Azure ASP.NET Providers (via jnak)
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
More episodes in this show
-
Cloud Cover Episode 17 - Using Queues
-
Cloud Cover Episode 18 - ASP.NET Providers
-
Cloud Cover Episode 19 - Silverlight and Blob…
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Hi,
Great show guys, very informative and quirky!
You invited us to provide topics that interest us, well here is one.
A topic I would like you to cover is the "environments". By that I mean "dev", "Staging" & "Production". For instance, can we have more environments than those three (e.g. UAT), what is carried around from one environment to the other, what is isolated (e.g. storage?), how to manage configuration transition (e.g. connection string SQL Server in dev, SQL Azure in staging & prod) and how could you manage "secrets" (e.g. if I don't want my developers to have access to the login / password of a write-account in SQL Azure Production)?
Otherwise, Steve mentionned the storage in production isn't based on SQL Server in production (as opposed to the dev fabric). I'm curious about how the actual implementation looks like. Is there any article around that give us an idea of how it's built in production?
Cheers,
Vincent-Philippe
Remember, you did have one show where you swapped names. It was obvious to most of us, but maybe if you only saw that one show it would be confusing to someone.
asd asd asd
Remove this comment
Remove this thread
close