.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Realizing a Service-Oriented Architecture with .NET

Posted By: Faizal     Posted Date: January 02, 2010    Points: 2   Category :ASP.Net
This article is meant to be a practical discussion guide to building a .NET application in a service-oriented architecture. We will consider real-world goals, real-world obstacles, and experience-based solutions. I quickly concede the approaches discussed here are not exhaustive or infallible. This paper is focused on application development, not application integration. We will specifically consider architectural issues and component design issues.

The Potential of Web Services

View Complete Post

More Related Resource Links

Editor's Note: A Service-Oriented Editor's Note


Here is what Howard Dierking has to say about the differences between services and distributed applications and how he has approached services in his projects.

Howard Dierking

MSDN Magazine April 2008

Microsoft .NET Framework: Delivers the Platform for an Integrated, Service-Oriented Web


The Microsoft .NET Framework is a new platform for building integrated, service-oriented applications to meet the needs of today's Internet businesses; apps that gather information from, and interact with, a wide variety of sources, regardless of the platforms or languages in use. This article, the first of a two part series, illustrates how the .NET Framework enables you to quickly build and deploy Web services and applications in any programming language. Microsoft Intermediate Language and JIT compiler, which make this reuse possible, are described as well as managed components, assemblies, and the Common Type System (CTS).

Jeffrey Richter

MSDN Magazine September 2000

How to design a Centralised Business or Service Authendication Architecture in ASP .Net


Hi All,

i want to create a centralised business or Service authendication architecture in .net. for example, we have a clients like c1, c2, c3, c4, ... etc. everybody logins seperatly as well as grouply. ie, if client  "C1" logins [with login authentication] he can access c2 , c3, c4 also without login authendication. So its like a google.  if we enters gmail  account, we can access orkut, picasa like that.. i need the cetralised architecture.

And, client "c1" seperately asks seperately how will be the authendication architecture.

so give me the single solution for both these two scenarios.... how will be the architecture for these two and how is the Data Base (Login) Structure.

Thanks in Advance.

with Regards


WCF Service Architecture for database driven application??

Hi everyone.
I am developing a database driven wcf service.

Sir I just want to confirm if you have to number of entities(like Products, Orders) in your database then how will you implement those entities operation(each have min 5) in your service (Like three tier architecture) you

1. Will you create different contract for different entities??
2. Will you implement those different contract in different classes??
3. Will they be hosted on different endpoints??

Please reply soon i am waiting 

Sharepoint Service Applications question, architecture



I read an article in documentation:

When for example u want to use service applications you need to connect your service
applications to the WFE’s. This is done using a proxy (don’t think WCF/ASMX proxy… think of it
in the more generic term for now (as compared to 2007)).

I donnt exactly undestand this - so what is this proxy and what is communication Protocol between WFE and the application server?

Second question is if it is truth, then if there are two farms or more then could you search content through all of them using one Search Service Application? And would it be enough to have ONE search server in total and on the other farm there would be only some proxy to search sevice?

WCF Architecture: AppFabric Service Bus Discovery


Learn how to roll your own discovery mechanism as we walk you through a small framework the author wrote to support discovery over the service bus, bringing it on par with the built-in support for discovery in WCF.

Juval Lowy

MSDN Magazine October 2010

Chapter 10: Developing Service-Oriented Applications for SharePoint 2010

Read an online chapter that discusses web services that are native to SharePoint 2010, building custom web services, and implementing custom web services by using different client solutions in SharePoint 2010.

Architecture Tools in VSTS 2010

Designing new functionality on existing applications can be daunting. There are always differences between the original design and the current implementation.

The new Architecture tools within Visual Studio Team System 2010 help you understand the application you have, design new functionality you need, and validate that your design and your implementation do not deviate.

Windows Service Applications Tutorials

You can easily create services by creating an application that is installed as a service. For example, suppose you want to monitor performance counter data and react to threshold values. You could write a Windows Service application that listens to the performance counter data, deploy the application, and begin collecting and analyzing data.

SharePoint Tutorial - SharePoint Logical Architecture

The SharePoint logical architecure consists of nested and isolated levels. These levels provide benefits for security, navigation, search, branding and ect. depending on the level

SharePoint Farm
The base level for any SharePoint implementation is the SharePoint farm. Physically a farm can consist of one server or many servers. An organization may implement one or more farms. This usually depends on security and performance needs.

SharePoint Tutorial -SharePoint Physical Architecture

The SharePoint physical architecture consists of services running on one or more servers.

There are three types of services that together run the SharePoint farm: web, application and database services. Web services through Internet Information Server is what processes the ASP.Net and sends back the html to a user's browser. Application services is where the "brains" of SharePoint are located. All of the SharePoint specific logic and services are processed there. Database services are run by SQL Server and it's where all the data/content for SharePoint is stored.

MVC Architecture

The main aim of the MVC architecture is to separate the business logic and application data from the presentation data to the user.

Here are the reasons why we should use the MVC design pattern.

They are resuable : When the problems recurs, there is no need to invent a new solution, we just have to follow the pattern and adapt it as necessary.
They are expressive: By using the MVC design pattern our application becomes more expressive.

MVC architecture in ASP.Net using C# and Microsoft Data Access Application block

The Model-View-Controller (MVC) pattern separates the modeling of the domain, the presentation, and the actions based on user input into three separate classes [Burbeck92]:

Model. The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller).

View. The view manages the display of information.

Controller. The controller interprets the mouse and keyboard inputs from the user, informing the model and/or the view to change as appropriate.

Project Example: ASP.NET MVC + SubSonic Architecture

use of SubSonic to provide the DAL in association with some ASP.NET MVC sites and was waylaid in my original intent to throw up a post summarizing the architecture we're using for the effort. Well I've finally gotten around to it. Recall that in his fake it till you need it post, Dave provided a window on our architecture that I'll build upon here

Three Tier Architecture with ASP.NET

ASP.NET supports layered architecture, and this article will illustrate how it can work with the ASP.NET presentation controls. This article focuses mainly on the GridView control, mostly because it is prevalently used in .NET development. However, the concepts work for other controls as well.

ASP.NET 2.0 (III) Architecture and Tools

In this third article we'll take a look at the changes to the architecture of ASP.NET v2.0. In particular we'll look at the changes to the compilation and deployment model.

High-Performance .NET Application Development & Architecture

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.
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend