dinesh k mandal
Get flash to fully experience Pearltrees
Overview This guide provides design-level guidance for the architecture and design of .NET Framework applications and services built on Windows 2000 and version 1.0 of the .NET Framework. It focuses on partitioning application functionality into components, walks through their key design characteristics, explains how security, management and communication apply to each layer, and provides information on how the components should be deployed Top of page
By Rick Strahl http://www.west-wind.com/ Last Update: August 12, 2008
Difference between Interface and Abstract Class is favourite question of interviewer while he wants to evaluate your knowledge about Object [Continue Reading...] For basic Interview Questions of MVC refer my first post of MVC Inter 1. What is main focus in Microsoft's Latest ASP.NET 4.0? Ans.
Microsoft Windows Communication Foundation (WCF) 3.5 Microsoft .NET Framework 3.5 Microsoft Visual Studio 2008 This how-to article shows you how to perform message validation using a schema in WCF. You will learn how to create a custom client message inspector and dispatcher message inspector that can be used to validate messages on both the server and the client.
The IDesign serviceware downloads is a set of original techniques, tools, utilities and even breakthroughs developed by the IDesign architects. The utilities are largely productivity-enhancing tools, or they compensate for some oversight in the design of .NET or WCF. The demos are also used during our Master Classes to demystify technical points, as lab exercises or to answer questions. The classes' attendees find the demos useful not only in class but after it.
In this sample chapter from his upcoming book (co-authored with Chris Farrell), Paul Glavich explains performance metrics and walks us through the steps needed to establish meaningful performance targets. He covers many metrics such as "time to first byte" and explains why you should add some contingency into your estimated performance requirements. Naturally, in order to achieve a goal, you first need to understand what that goal is . So, before you can determine whether your application performs well, you need to understand that means in terms of the metrics your application needs to produce. Whether or not your application performs well is a relative target; not all applications are the same.
Wednesday, April 01, 2009 10:44 PM Kazi Manzur Rashid [Also check out the next part of this series] In this post, I will share some of the best practices/guideline in developing ASP.NET MVC applications which I have learned in the hard way. I will not tell you to use DI or Unit Test instead I will assume you are already doing it and you prefer craftsmanship over anything. 1.
My Advice for .NET Application Architecture and Design | Peter Meinl – IT Architect & Lateral ThinkerThis post summarizes my general architecture and design guidelines for developing applications and points to some interesting NET technologies. Reading this post will not make anyone an architect, but working through it should give you a good foundation for understanding and discussing architecture and design decisions. BTW: Architects must write code to really understand what they are talking about and experience some of the pain their design decisions may cause for project managers, programmers, DBAs, operators and users (see MS WeSYP ). Table of contents:
You can create a database under the assumption that SQL looks after all the problems of concurrency. It will probably work fine under test conditions: Then, in the production environment, it starts losing data in subtle ways that defy repetition. It is every Database Developer's nightmare. In an excerpt from his acclaimed book, Alex explains why it happens, and how you can avoid such problems.
Table of Contents Introduction Again i repeat do not think you get an architecture position by reading interview questions. But yes there should be some kind of reference which will help you quickly revise what are the definition. Just by reading these answers you get to a position where you are aware of the fundamentals. But if you have not really worked you will surely fail with scenario based questions.
This (long) posting provides guidelines for using common patterns to control concurrency when using relational databases (RDBMS) via ADO.NET or the .NET Entity Framework (EF). MS SQL Server and Oracle are used as examples to sensitize you for the implications of RDBMS specific concurrency model implementations. When multiple sessions (users, processes) attempt to concurrently modify database data, modifications by one session can adversely affect modifications by simultaneous sessions or cause inconsistencies in the database(s).
We are very pleased to be allowed to publish the first chapter from Grant Fritchey's excellent new book, Dissecting SQL Server Execution Plans . You can download it for free here . Grant's book is also currently available in several eBook formats: PDF format from Lulu.com Mobipocket format Kindle format from Amazon.com ... and you can inspect an HTML version of the Table of contents here...
Learning how to read and analyze execution plans takes time and effort. But once you gain some experience, you will find them an essential skill for getting to grips with performance issues in SQL Server Queries. Grant here describes the range of execution plans for different simple SQL Queries. This is the second chapter from Grant Fritchey's excellent book, Dissecting SQL Server Execution Plans . You can download it for free here .