WCF VS Web Services
Rich Set of Protocol
WCF supports more protocols for transporting messages than ASP.NET Web services. ASP.NET Web services only support sending messages by using the Hypertext Transfer Protocol (HTTP). WCF supports sending messages by using HTTP, as well as the Transmission Control Protocol (TCP), named pipes, and Microsoft Message Queuing (MSMQ). More important, WCF can be extended to support additional transport protocols. Therefore, software developed using WCF can be adapted to work together with a wider variety of other software, thereby increasing the potential return on the investment.
WCF provides much richer facilities for deploying and managing applications than ASP.NET Web services provides. In addition to a configuration system, which ASP.NET also has, WCF offers a configuration editor, activity tracing from senders to receivers and back through any number of intermediaries, a trace viewer, message logging, a vast number of performance counters, and support for Windows Management Instrumentation.
26 January 2011
WPF vs. Silverlight in .net
WPF vs. Silverlight in .net
Both WPF and Silverlight use XAML (Extensible Application Markup Language) under the covers.
Let's look at some of the different characteristics of each technology:
WPF:
* Ships as part of the .NET Framework (version 3.0 and onward)
* Runs as Windows application or as web "browser application" (called XBAP, for "XAML Browser Application"). Note that XBAPs run only in Internet Explorer with .NET 3.0 and in both Internet Explorer and Firefox with .NET 3.5.
* Runs on Windows machines only (Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008)
* Richest functionality, including 3D graphics
Silverlight:
* Ships independently
* Runs in web browsers only (Internet Explorer, Firefox, Safari)
* Runs on Windows or Mac operating systems (also on Linux via Moonlight,which is an open source implementation of Silverlight based on Mono)
* Functionality is a subset of WPF's feature set
WPF is a more mature technology and was designed with a richer feature set. It also has the advantage of being able to run in a browser or as an installed Windows-Form-type app.
Silverlight has a broader reach.You can access Silverlight from many operating systems and web browsers.
The most important reason to choose one over the other should be based on the intended audience for the application. For example, if a corporation is designing an application for internal use only and every employee has Windows XP as the company standard OS, then go with WPF to leverage the richer feature set. If a corporation is designing an external-facing website, then Silverlight is the better choice because potential customers can access the website from a variety of different operating systems and browsers.
Both WPF and Silverlight use XAML (Extensible Application Markup Language) under the covers.
Let's look at some of the different characteristics of each technology:
WPF:
* Ships as part of the .NET Framework (version 3.0 and onward)
* Runs as Windows application or as web "browser application" (called XBAP, for "XAML Browser Application"). Note that XBAPs run only in Internet Explorer with .NET 3.0 and in both Internet Explorer and Firefox with .NET 3.5.
* Runs on Windows machines only (Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008)
* Richest functionality, including 3D graphics
Silverlight:
* Ships independently
* Runs in web browsers only (Internet Explorer, Firefox, Safari)
* Runs on Windows or Mac operating systems (also on Linux via Moonlight,which is an open source implementation of Silverlight based on Mono)
* Functionality is a subset of WPF's feature set
WPF is a more mature technology and was designed with a richer feature set. It also has the advantage of being able to run in a browser or as an installed Windows-Form-type app.
Silverlight has a broader reach.You can access Silverlight from many operating systems and web browsers.
The most important reason to choose one over the other should be based on the intended audience for the application. For example, if a corporation is designing an application for internal use only and every employee has Windows XP as the company standard OS, then go with WPF to leverage the richer feature set. If a corporation is designing an external-facing website, then Silverlight is the better choice because potential customers can access the website from a variety of different operating systems and browsers.
Base Class of all classes in the .NET Framework
Base Class of all classes in the .NET Framework
Object Class is Base Class of all classes in the .NET Framework
Object Class is Base Class of all classes in the .NET Framework
Root Namespace of Dotnet
Root Namespace of Dotnet
The System namespace is the root namespace for fundamental types in the .NET Framework. This namespace includes classes that represent the base data types used by all applications
The System namespace is the root namespace for fundamental types in the .NET Framework. This namespace includes classes that represent the base data types used by all applications
What is WebService in asp.net?
What is Web Service in ASP.net?
A web service is a special kind of web site. It is different from a traditional ASP.NET web site that produces HTML code. In fact, a web service had no graphical user interface and produces XML. A web service exposes one or more methods that your application can call remotely. This is called a remote procedure call. It basically means that you can have web service A sitting on a web server and another ASP.NET web application B sitting on a different server, and application B can call or communicate with web service A, even though they are in separate physical machines.
It turns out that this feature of web services makes them very useful for many reasons: scalability, encapsulation of logic, and security.
Web services are implemented internally using an Internet protocol called SOAP, which passes XML messages back and forth between a web service client application and a web service. The SOAP protocol is an Internet standard which makes web services interoperable or cross-platform (e.g. Java can communicate with .NET and .NET can communicate with Java); the two can integrate with each other seamlessly by using web services. You don’t have to understand how SOAP works in order to program an ASP.NET web service, and a lot of programmers probably don’t. That is one of the strengths of the .NET framework and the Visual Studio IDE.
A web service is a special kind of web site. It is different from a traditional ASP.NET web site that produces HTML code. In fact, a web service had no graphical user interface and produces XML. A web service exposes one or more methods that your application can call remotely. This is called a remote procedure call. It basically means that you can have web service A sitting on a web server and another ASP.NET web application B sitting on a different server, and application B can call or communicate with web service A, even though they are in separate physical machines.
It turns out that this feature of web services makes them very useful for many reasons: scalability, encapsulation of logic, and security.
Web services are implemented internally using an Internet protocol called SOAP, which passes XML messages back and forth between a web service client application and a web service. The SOAP protocol is an Internet standard which makes web services interoperable or cross-platform (e.g. Java can communicate with .NET and .NET can communicate with Java); the two can integrate with each other seamlessly by using web services. You don’t have to understand how SOAP works in order to program an ASP.NET web service, and a lot of programmers probably don’t. That is one of the strengths of the .NET framework and the Visual Studio IDE.
10 January 2011
Difference Between Oracle and Sql Server 2008
Difference Between Oracle and Sql Server 2008
1.The FIRST biggest difference: Transaction control.
In Oracle EVERYTHING is a transaction and it is not permanent
until you COMMIT.In SQL Server, there is (by default) no transaction control.
2.SQL Server supports only windows based platforms.
Oracle:Its a platform independent
3.Oracle includes IFS (Internet File System), Java integration,
SQL is more of a pure database
1.The FIRST biggest difference: Transaction control.
In Oracle EVERYTHING is a transaction and it is not permanent
until you COMMIT.In SQL Server, there is (by default) no transaction control.
2.SQL Server supports only windows based platforms.
Oracle:Its a platform independent
3.Oracle includes IFS (Internet File System), Java integration,
SQL is more of a pure database
Subscribe to:
Posts (Atom)