WCF vs .NET Remoting 2.

0
by Rakesh Yadav on Wednesday, July 27, 2011 at 5:28pm WCF: - WCF is Microsoft recommended direction - WCF was released on January 2006 with Go-Live Licenses, but it will be officially released on November of this year - WCF is a 100% Service Oriented Architecture application development platform - WCF Security Architecture is interoperable, based on WS-* specifications and its designed for On-Machine, Cross-Machine, and Cross-Internet scenarios. - WCF Transaction Architecture is full flexible, declarative and has method level granularity - WCF binary messages are smaller and faster than Remotings.- Services versioning is better dealt with WCF than with Remoting. .Net Remoting for .Net Framework 2.0: - Remoting is not recommended by Microsoft - Remoting for .Net Framework 2.0 was released in December 2005 - Remoting is tightly coupled Object Oriented technology and not loosely coupled Service Oriented. - It has security limitations, though now it has the new secure TcpChanne l- With System.Transactions we can get similar transaction management capabilities but not in a declarative way.

differences between the XML Web service and .NET Remoting technologies:
by Rakesh Yadav on Wednesday, July 27, 2011 at 5:16pm

XML Web services are more restricted than objects exposed over .NET Remoting. An XML Web service works in a similar way to a SingleCall .NET Remoting object. It isn't possible to create a singleton or a client-activated object.

Because of the restricted nature of XML Web services, the design issues are simplified. XML Web services are generally easier to create than remotable components (and easier to design well).

Communication with .NET Remoting can be faster than XML Web service communication if you use a binary formatter. XML Web services support only SOAP message formatting, which uses larger XML text messages.

XML Web services support open standards that target cross-platform use. For example, each .NET XML Web service has an associated WSDL document that describes how a client can interact with the service. Therefore, any client that can parse an XML message and connect over an HTTP channel can use an XML Web service, even if the client is written in Java and hosted on a UNIX computer.

XML Web services are designed for use between companies and organizations. They can use a dynamic discovery mechanism or a UDDI registry that "advertises" services to interested parties over the Internet.

XML Web services don't require a dedicated hosting program because they are always hosted by ASP.NET. That also means that they gain access to some impressive platform services, including data caching, Web farm-ready session state management, authentication, and an application collection for global, shareable objects. These features, if required, can be extremely difficult to recreate by hand in a component exposed through .NET Remoting.

Because XML Web services work through Microsoft Internet Information Services (IIS) and ASP.NET, they can communicate with clients using the default HTTP channel (usually port 80). This means that consumers can use XML Web services just as easily as they can download HTML pages from the Internet. There's no need for an administrator to open additional ports on a firewall.

Difference between WPF and SilverLight

by Rakesh Yadav on Friday, July 1, 2011 at 5:02pm WPF is for desktop applications- you create an .exe file when you build WPF applications. To run a WPF exe requires you to have Framework 3 or higher on your pc.

Silverlight is on the web. What you create is an application that can be hosted either in an html page or an asp.net page. To watch it from your browser it requires to have installed in your browser the silverlight plugin. Silverlight uses very fewer libraries than WPF does, and that's pretty logical because silverlight's CLR is in the plugin which is about 5-10 MB.

- WPF and silverlight though use the same logic in development and the same technology.

- Basic difference between WPF & Silverlight is that WPF is for desktop applications & silverlight is for Web application.

1. Silverlight is simply a subset of WPF. 2. Silverlight is meant to be used online, while WPF is for local use. 3. You can use Silverlight applications regardless of the operating system you use, while WPF applications are restricted to later versions of the Windows operating system. 4. Silverlight lacks access to local resources, while WPF can utilize local resources. 5. Silverlight only has perspective 3D support, while WPF is capable of full 3D images.

ASP.NET Applications to IIS 7

by Rakesh Yadav on Monday, June 27, 2011 at 1:35pm the ASP.NET request-processing stages that are exposed to modules are directly connected to the corresponding stages of the IIS 7 pipeline. The complete pipeline contains the following stages, which are exposed as HttpApplication events in ASP.NET:

1. 2. 3. 4. 5. 6.

BeginRequest. The request processing starts. AuthenticateRequest. The request is authenticated. IIS 7 and ASP.NET authentication modules subscribe to this stage to perform authentication. PostAuthenticateRequest. AuthorizeRequest. The request is authorized. IIS 7 and ASP.NET authorization modules check whether the authenticated user has access to the resource requested. PostAuthorizeRequest. ResolveRequestCache. Cache modules check whether the response to this request exists in the cache, and return it instead of proceeding with the rest of the execution path. Both ASP.NET Output Cache and IIS 7 Output Cache features execute.

7. 8. 9.

PostResolveRequestCache. MapRequestHandler. This stage is internal in ASP.NET and is used to determine the request handler. PostMapRequestHandler.

10. AcquireRequestState. The state necessary for the request execution is retrieved. ASP.NET Session
State and Profile modules obtain their data.

11. PostAcquireRequestState. 12. PreExecuteRequestHandler. Any tasks before the execution of the handler are performed. 13. ExecuteRequestHandler. The request handler executes. ASPX pages, ASP pages, CGI programs,
and static files are served.

14. PostExecuteRequestHandler

15. ReleaseRequestState. The request state changes are saved, and the state is cleaned up here.
ASP.NET Session State and Profile modules use this stage for cleanup.

16. PostReleaseRequestState. 17. UpdateRequestCache. The response is stored in the cache for future use. The ASP.NET Output
Cache and IIS 7 Output Cache modules execute to save the response to their caches.

18. PostUpdateRequestCache. 19. LogRequest. This stage logs the results of the request, and is guaranteed to execute even if errors
occur.

20. PostLogRequest. 21. EndRequest. This stage performs any final request cleanup, and is guaranteed to execute even if
errors occur.

By using the familiar ASP.NET APIs, the ability to execute in the same stages as IIS 7 modules makes tasks that were only previously accessible in native ISAPI filters and extensions now possible in managed code.

What is an Assembly?
by Rakesh Yadav on Sunday, June 26, 2011 at 6:59pm Any .NET code (be it an EXE or a DLL) on compilation is stored as an Assembly. The entire .NET code (any language) gets converted in the form of IL code. Hence an assembly is .NETs approach to code reuse.

In addition to the IL code, an assembly also contains Assembly Metadata, Type metadata and Resources. Assemblies are hence self-describing. Its no longer necessary to pay attention to registry keys or type library. Assemblies include metadata that describe the assembly. Following figure shows the composition of an assembly created after compiling a DLL called myassembly.dll.

The Assembly Metadata is also called the Manifest. A manifest is a data structure that serves the same purpose as the type library and associated registry entries do, for a COM component. Manifest contains more information than a type library. The Type Metadata includes the types (classes, methods and properties) exported from the assembly.

Some of the salient features of assemblies are as follows:

Assemblies can be loaded using the side-by-side technique. This means two different versions of the same assembly can be used inside a single process.

Assemblies support Zero-impact installation. Installation can be as easy as copying the files that belong to an assembly.

An assembly may represent one file or might be spread across several files.

Microsoft Entity Framework 4.1

by Rakesh Yadav on Tuesday, June 21, 2011 at 5:31pm ADO.NET Entity Framework 4.1 introduces two new features:

The DbContext API is a simplified abstraction over ObjectContext and a number of other types that were included in previous releases of the ADO.NET Entity Framework. The DbContext API surface is optimized for common tasks and coding patterns. DbContext can be used with Database First, Model First and Code First development. Code First is a new development pattern for the ADO.NET Entity Framework and provides an alternative to the existing Database First and Model First patterns. Code First is focused around defining your model using C#/VB.NET classes, these classes can then be mapped to an existing database or be used to generate a database schema. Additional configuration can be supplied using Data Annotations or via a fluent API.

Cloud computing
by Rakesh Yadav on Tuesday, June 21, 2011 at 2:44pm Cloud computing refers to the use and access of multiple server-based computational resources via a digital network (WAN, Internet connection using the World Wide Web, etc.). Cloud users may access the server resources using a computer, netbook, pad computer, smart phone, or other device. In cloud computing, applications are provided and managed by the cloud server and data is also stored remotely in

the cloud configuration. Users do not download and install applications on their own device or computer; all processing and storage is maintained by the cloud server.

Windows Azure Platform

by Rakesh Yadav on Tuesday, June 21, 2011 at 2:41pm The Windows Azure Platform is a Microsoft cloud platform used to build, host and scale web applications through Microsoft datacenters. Windows Azure Platform is thus classified as platform as a service and forms part of Microsoft's cloud computing strategy, along with their software as a service offering, Microsoft Online Services. The platform consists of various on-demand services hosted in Microsoft data centers and commoditized through three product brands. These are Windows Azure[3] (an operating system providing scalable compute and storage facilities), SQL Azure (a cloud-based, scale-out version of SQL Server) and Windows Azure AppFabric (a collection of services supporting applications both in the cloud and on premise).