Академический Документы
Профессиональный Документы
Культура Документы
Features OF MVC:
It includes a very powerful URL mapping component that enables you to build applications with clean URLs. URLs do
not need to have extensions within them. For example, I could easily map the /products/edit/4 URL to the "Edit" action of
the ProductsController class in my project above, or map the /Blogs/ /10-10-2007/SomeTopic/ URL to a "DisplayPost"
action of a BlogEngineController class.
The MVC framework supports using the existing ASP.NET .ASPX, .ASCX, and .Master markup files as "view templates"
(meaning you can easily use existing ASP.NET features like nested master pages, <%= %> snippets, declarative server
controls, templates, data-binding, localization, etc).
The ASP.NET MVC framework fully supports existing ASP.NET features like forms/windows authentication, URL
authorization, membership/roles, output and data caching, session/profile state management, health monitoring,
configuration system, the provider architecture, etc.
Because WCF can communicate using Web services, interoperability with other platforms that also support SOAP, such as
the leading J2EE-based application servers, is straightforward.
You can also configure and extend WCF to communicate with Web services using messages not based on SOAP, for
example, simple XML formats like RSS.
Performance is of paramount concern for most businesses. WCF is developed with the goal of being one of the fastest
distributed application platform developed by Microsoft. For a high-level performance comparison between WCF and
other Microsoft .NET distributed communication technologies
To allow optimal performance when both parties in a communication are built on WCF, the wire encoding used in this case
is an optimized binary version of an XML Information Set. Messages still conform to the data structure of a SOAP
message, but their encoding uses a binary representation of that data structure rather than the standard angle-brackets-andtext format of the XML 1.0 text encoding. Using this option makes sense for communicating with the call center client
application, because it is also built on WCF, and performance is an important concern.
Managing object lifetimes, defining distributed transactions, and other aspects of Enterprise Services are now provided by
WCF. They are available to any WCF-based application, which means that the rental car reservation application can use
them with any of the other applications it communicates with.
Because it supports a large set of the WS-* specifications, WCF helps provide reliability, security, and transactions when
communicating with any platform that also supports these specifications.
The WCF option for queued messaging, built on Message Queuing, allows applications to use persistent queuing without
using another set of application programming interfaces.
System.servicemodel is a namespace which we use it first when we start writing WCF class
We could declare some kind of Service Contract like
[ServiceContract (Namespace = http://microsoft.servicemodel.....)
WCF have some features:-
Messaging: SOAP is the foundation for Web services and defines a basic envelope that contains header and a body
sections. WS-Addressing defines additions to the SOAP header for addressing SOAP messages, which frees SOAP from
relying on the underlying transport protocol, such as HTTP, to carry addressing information. Message Transmission
Optimization Mechanism (MTOM) defines an optimized transmission format for SOAP messages with large binary data
contents based on the XML-binary Optimized Packaging (XOP) specification.
Metadata: The Web Services Description Language (WSDL) defines a standard language for specifying services and
various aspects of how those services can be used. WS-Policy allows specification of more dynamic aspects of a services
behavior that cannot be expressed in WSDL, such as a preferred security option. WS-MetadataExchange allows a client
to directly request descriptive information about a service, such as its WSDL and its policies, using SOAP.
Security: WS-Security, WS-SecureConversation, WS-Trust, and WS-Federation all define additions to SOAP messages for
providing authentication, data integrity, data privacy, and other security features.
Reliability: WS-Reliable Messaging defines additions to the SOAP header that allow reliable end-to-end communication,
even when one or more Web services intermediaries must be traversed.
Transactions: Built on WS-Coordination, WS-Atomic Transaction allows coordinating two-phase commit transactions in
the context of Web services conversations.
LINQ to Objects
LINQ to ADO.NET, which includes
LINQ to Entities
LINQ to Objects deals with in-memory data. Any class that implements the IEnumerable<T> interface (in the
System.Collections.Generic namespace) can be queried with SQO.
LINQ to ADO.NET deals with data from external sources, basically anything ADO.NET can connect to. Any class that implement
IEnumerable<T> or IQueryable<T>
LINQ to Entities will bring LINQ to the ADO.NET Entity Framework, which combines an Entity Data Model with an extended
version of SQL (eSQL) in yet another effort to address the data-object impedance issue. Since the Entity Framework is an ADO.NET
3.0 feature, we wont cover LINQ to Entities here.
Using LINQ to SQL
LINQ to SQL is a facility for managing and accessing relational data as objects. Its logically similar to ADO.NET in some ways but
views data from a more abstract perspective that simplifies many operations. It connects to a database, converts LINQ constructs into
SQL, submits the SQL, transforms results into objects, and can even track changes and automatically request database updates.
A simple LINQ query requires three things:
1.
2.
An entity class
A data context
3.
A LINQ query