Help yourself by exploring below resources on ADO.NET Data Services (aka "Project Astoria").
I am very much excited as I should be to start with my First Windows Azure Application. I did install the Azure related bits in my machine and got the token for uploading my test application. Then with the passion cherished by created the application which I am running at http://wriju.cloudapp.net, so let us enjoy.
There are lots and lots of resources available at http://www.microsoft.com/azure/. I compiled them and put in a single location for you. You can also go to https://sessions.microsoftpdc.com/public/timeline.aspx and open the “Azure” tag. You will experience the PDC 2008 announcement.
Technical Videos for Windows Azure
Download the SDKs
Explore and experiment with the Azure SDK’s locally
Ø Windows Azure SDK
Ø Windows Azure Tools for Microsoft Visual Studio
Ø Microsoft .NET Services SDK
Ø Microsoft SQL Data Services SDK
Ø Live Framework Documentation and Resources
Register for Services*
This will give you an unique opportunity to create your own Azure Services and host in Microsoft Windows Azure Platform
Good to Know
Azure Services Training Kit - PDC Preview
Windows Azure PDC 2008
Ø Azure for web developers
Ø Azure for corporate developers
Ø Azure for ISVs
Ø Azure for systems integrators
Ø Azure for business
As always enjoy
I have done setup in my dev machine for Cloud development.
Now my Visual Studio looks different,
There are four papers on
Introduction to Microsoft .NET Services
Microsoft .NET Access Control Service
Microsoft .NET Service Bus
Microsoft .NET Workflow Service
Actual Application Architecture Guide 2.0 is of 300+ pages. So it is very difficult to carry every time. Patterns and Practices team have came up with smaller editions depending upon the interests and areas.
Find all of them here,
There are many more books available. Go and grab them
· Acceptance Test Engineering Guidance
· Application Architecture Guidance
· Common Service Locator
· Composite Application Guidance for WPF
· Design for Operations
· Enterprise Library
· ESB Guidance
· GAX Extensions Library
· Guidance Explorer
· Performance Testing Guidance for Web Applications
· Performance Testing Guidance Project
· SharePoint Development Guidance
· Smart Client Guidance
· Team Development with Visual Studio Team Foundation Server
· Unity Application Block
· VSTS Guidance Project
· WCF Security Guidance
· Web Client Software Factory
· Web Service Software Factory
This one is small and concise. I love the work on standards. You may or may not agree to it. But take a look here and download the pages,
This work is from Clint Edmonson, Architect Evangelist for Microsoft.
This indeed a good news for us, there has been many freely available guides. Why you should be paying others? Get the copy now for free
There have been many talks going on while deciding between LINQ to SQL and Entity Framework.
There is one article published in MSDN at
When do I use LINQ to SQL?
I want to
LINQ to SQL is applicable
Use an ORM solution and my database is 1:1 with my object model
Use an ORM solution with inheritance hierarchies that are stored in a single table
Use my own plain CLR classes instead of using generated classes or deriving from a base class or implementing an interface
Leverage LINQ as the way I write queries
Use an ORM but I want something that is very performant and where I can optimize performance through stored procedures and compiled queries
When to use LINQ to Entity?
LINQ to Entities is applicable
Write applications that can target different database engines in addition to Microsoft SQL Server
Define domain models for my application and use these as the basis for my persistence layer.
Use an ORM solution where my classes may be 1:1 with the database or may have a very different structure from the database schema
Use an ORM solution with inheritance hierarchies that may have alternative storage schemes (single table for the hierarchy, single table for each class, single table for all data related to specific type)
Leverage LINQ as the way I write queries and have the query work in a database vendor agnostic manner.
For more you must visit Introducing LINQ to Relational Data at MSDN.
I am pretty sure that many of you do not want to learn EntitySQL J. But for those who would may follow the below links
Entity SQL Overview
An overview of Entity SQL.
Entity SQL Reference
Provides syntax for the Entity SQL functions and operators.
There is a correction for this Post, so do I have changed the title. Thanks to Chris Love who pointed me the faults with earlier post,
I got few question on some of the popular paging methods of LINQ which does not work on LINQ to Entity. This is by design and quite logical. In LINQ to SQL scenario they do translate to native TSQL and uses some of its properties and functions. Thus this cannot be made generic for other databases like Oracle/DB2.
There is a list published in MSDN with the operators at,
Projection and Restriction Methods (LINQ to Entities)
Lists the supported and unsupported projection and restriction methods.
Join Methods (LINQ to Entities)
Lists the supported and unsupported joining methods.
Set Methods (LINQ to Entities)
Lists the supported and unsupported set methods.
Ordering Methods (LINQ to Entities)
Lists the supported and unsupported ordering methods.
Grouping Methods (LINQ to Entities)
Lists the supported and unsupported grouping methods.
Aggregate Methods (LINQ to Entities)
Lists the supported and unsupported aggregating methods.
Type Methods (LINQ to Entities)
Lists the supported and unsupported type methods.
Paging Methods (LINQ to Entities)
Lists the supported and unsupported paging methods.