By -
.NET Building Blocks is a set of core Internet Services.
Web Services
Web Services provide data and services to other applications.
Future applications will access Web Services via standard Web Formats (HTTP, HTML, XML, and SOAP), with no need to know how the Web Service itself is implemented.
Web Services are main building blocks in the Microsoft .NET programming model.
Standard Communication
Official Web standards (XML, UDDI, SOAP) will be used to describe what Internet data is, and to describe what Web Services can do.
Future Web applications will be built on flexible services that can interact and exchange data, without the loss of integrity.
Internet Storages
.NET offers secure and addressable places to store data and applications on the Web. Allowing all types of Internet devices (PCs, Palmtops, Phones) to access data and applications.
These Web Services are built on Microsoft's existing NTFS, SQL Server, and Exchange technologies.
Internet Dynamic Delivery
Reliable automatic upgrades by demand and installation independent applications.
.NET will support rapid development of applications that can be dynamically reconfigured.
Internet Identity
.NET supports many different levels of authentication services like passwords, wallets, and smart cards.
These services are built on existing Microsoft Passport and Windows Authentication technologies.
Internet Messaging
.NET supports integration of messaging, e-mail, voice-mail, and fax into one unified Internet Service, targeted for all kinds of PCs or smart Internet devices.
These services are built on existing Hotmail, Exchange and Instant Messenger technologies.
Internet Calendar
.NET supports Internet integration of work, social, and private home calendars. Allowing all types of Internet devices (PCs, Palmtops, Phones) to access the data.
These services are built on existing Outlook and Hotmail technologies.
Internet Directory Services
.NET supports a new kind of directory services that can answer XML based questions about Internet Services, far more exactly than search engines and yellow pages.
These services are built on the UDDI standard.

Comments

Post a Comment

Popular posts from this blog

By -
We are taking off for a new adventure in development: It's about developing a framework which will enable us to persist our business objects into databases, file systems or xml file system. STEP 1: CREATING A BUSINESSOBJECT ATTRIBUTE namespace ORMCore { /// /// This attribute is used to enable the ORMFramework /// to create an associate table on the RDBMS /// [ AttributeUsage(AttributeTargets.Class, AllowMultiple = false)] public class BusinessObjectAttribute:Attribute { private string _databaseName; public string DatabaseName { get { return _databaseName; } } private string _databaseConnexionString; public string DatabaseConnexionString { get { return _databaseConnexionString; } } public BusinessObjectAttribute(string databaseName) { this._databaseName = databaseName; } public B
Read more
By -
Image
Sql Server adapters for Biztalk Server One of the greatest difficulties I found when I started working with BizTalk 2004 was the lack of documentation about the SQL Adapter. In this article, I'm going to demonstrate how we can use this adapter in an Orchestration of BizTalk. The Example To build this example, we're going to use the Northwind database. We're going to simulate a hypothetical situation where we receive an XML message as a file, containing the order number, a customer ID, and the date of the order. In the orchestration, we will use SQL Server to search the additional information about the customer, using the SQL Adapter. Creating the Project We'll start this article by creating a new BizTalk Server project in Visual Studio. In the Visual Studio .NET menu, select the "New Project" option, and for the type of project, select "BizTalk Projects". Select the template "Empty BizTalk Project" and create a project named OrderManager.
Read more
By -
Writing effective adapters for Biztalk Server Introduction Many people, both within Microsoft and in third-party companies, have written successful adapters for Microsoft® BizTalk® Server. This task can be difficult, and this paper is intended to present some of the "tricks of the trade" that these developers have learned, in the hope that these will help others avoid common problems. This document is structured as a set of issues that programmers face when writing adapters, and provides guidelines for resolving these issues. These guidelines can be read in any order, although you may find that reading the whole document first will make the individual guidelines easier to understand. Effective Writing for Adapters Much of the complexity in writing adapters for BizTalk Server is centered on the problems of batched operations and that is what we will look at first. Operations, Messages, Batching, and Transactions Adapters commonly support sending messages to and receiving messa
Read more