Cool!, just a few days ago (Thu Sep 25 2008) Microsoft P&P have published a neat ‘Application Architecture Guide’ (v.2.0). It is great because “it is new”, so it covers most of the new Microsoft dev technologies and application/architecture types we’re dealing with,
This is my second post about “Updating data using Entity Framework in N-Tier and N-Layer Applications”. If you wanna read the basics, go to my first post here:
So!, I finished my first post saying that the code I showed does not cover scenarios where we want to manage “Optimistic Concurrency Updates &
First of all, we are talking about using Entity Framework and how it fits within N-Tier and N-Layer applications, ok?, that’s our initial scenario.
An N-Tier application is an application where you have 3 or more physical tiers. I mean with that things like,
.NET 3.5 creates an ACL (Access Control List) for the namespace “http://+:8731/Design_Time_Addresses” during the installation of Visual Studio so users without administrator privilege are able to develop WCF services. The ACL is set to (UI), which includes all interactive users logged on to the machine.
There is a very nice training kit (which I’m using quite a lot) about the new Visual Studio 2008 and .NET Framework 3.5. It covers most of all the new .NET 3.5 features, like WPF, WCF, Workflow, Workflow-Services (SILVER), LINQ, C# 3.0,