Hello,Having spent the past couple of weeks looking into DD, I'm impressed with the ease and speed with which you can get a CRUD web site up and running.However, I've come across a few things in the last day or so that make me think I'm missing a major part of DD. I've seen hints of much, much more in there. For example, some of the posts on Stephen Naughton's blog mention all sorts of things that look really clever, but are a bit past my understanding of DD at the moment. This makes me feel there's a lot more in there that I have realised.So, can anyone give me an overview of the full picture of what DD offers? Is there more to it than just scaffolding?Thanks

When I deploy the cube which is sitting on my PC (local) the following 4 errors come up:
ErrorÃÂ 1ÃÂ The datasource , 'AdventureWorksDW', contains an ImpersonationMode that that is not supported for processing operations.ÃÂ ÃÂ 0ÃÂ 0ÃÂ ErrorÃÂ 2ÃÂ Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'Adventure Works DW', Name of 'AdventureWorksDW'.ÃÂ ÃÂ 0ÃÂ 0ÃÂ ErrorÃÂ 3ÃÂ Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Customer', Name of 'Customer' was being processed.ÃÂ ÃÂ 0ÃÂ 0ÃÂ ErrorÃÂ 4ÃÂ Errors in the OLAP storage engine: An error occurred while the 'Customer Alternate Key' attribute of the 'Customer' dimension from the 'Analysis Services Tutorial' database was being processed.ÃÂ ÃÂ 0ÃÂ 0

I have been learning ASP.NET from the ground up. I only recently stumbled onto the concepts of separating the data access layer and data access layers for larger, enterprise applications. As I started exploring this I realized I was a few years behind. To make sure I'm not shooting at the wrong moving target again I am trying to find out what the current best/recommended practices that people are learning today. It seems that Linq to SQL replaced a lot of what was used in ASP.NET 2.0 in terms of the DAL/BLL logic. Is this correct? Also, is the MVC framework the official pattern to be used to replace the presentation/BLL/DAL approach of a few years ago?

Moss high level visio view integration with SCOM 2007 is not working? It used to work and I know that I restarted my SCOM server and noticed that the high level visio view when clicking on a icon does not pull the information regarding the health state
from SCOM. I receive a authentication error-you do not have permission from my SCOM RMS server despite my being a SCOM admin. Also when I click on a email alert from SCOM the link for additional information has the same authentication error.
I am new to MOSS so can someone let me know how to troubleshoot this issue??dsk

I am trying to learn some datamining with SQL Server. I have some demo projects I am trying to run under my test environment: Windows Server 2008 + SQL Server 2008 R2 Enterprise. Sample projects seems to be ok, but when I try to process a mining structure,
I get this error:

"Errors in the high-level relational engine. The following exception occurred while an operation was being performed on a data source view: The type initializer for 'System.Xml.Schema.XmlSchemaComplexType' threw an exception.;Bad IL range.."

This article lists the techniques that you can use to maximize the performance of your ASP.NET applications. It provides common issues, design guidelines, and coding tips to build optimal and robust solutions.

If you ever wanted to restore your database from a SQL backup file (.bak), but there are still users connected to your database, the backup operation will fail causing the error: Exclusive access could not be obtained because the database is in use.

It has always been a goal of project architects to plan an effective strategy from the ground up in regards to an new application. All relevant factors are taken into consideration with respect to the application, from its design and layout to a functional website infrastructure. Pre-.NET strategies and design guidelines still effective now were developed with Microsoft's DNA (Distributed interNet Application) platform. This model successfully served the purpose of architecting N(any number of)-Tier (levels) applications. In its basic sense, as in most robust, distributed applications, you'll architect 3 main layers or Tiers: presentation, business rules and data access.

have been writing a series of blog posts, which I have named High Performance ASP.NET Websites Made Easy! There is no rhyme or reason to the order of these posts and certainly can be read in any order:

ASP.NET is a powerful platform for building Web applications, that provides a tremendous amount of flexibility and power for building just about any kind of Web application. Most people are familiar only with the high level frameworks like WebForms and WebServices which sit at the very top level of the ASP.NET hierarchy. In this article I'll describe the lower level aspects of ASP.NET and explain how requests move from Web Server to the ASP.NET runtime and then through the ASP.NET HTTP pipeline to process requests.

Writing a Web application with ASP.NET is unbelievably easy. So easy, many developers don't take the time to structure their applications for great performance. In this article, I'm going to present 10 tips for writing high-performance Web apps. I'm not limiting my comments to ASP.NET applications because they are just one subset of Web applications. This article won't be the definitive guide for performance-tuning Web applications-an entire book could easily be devoted to that. Instead, think of this as a good place to start.

I've been building web sites and for my next project I will be creating a web application. I use a 'BasePage' class in all my projects but, since web applications do not contain the 'App_Code' folder, what is the best place/practice for the 'BasePage' class?