- 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 it’s 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 Remoting’s.
- 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 TcpChannel
- With System.Transactions we can get similar transaction management capabilities but not in a declarative way
What is WCF?
Windows Communication Foundation (formerly code-named "Indigo") is a
set of .NET technologies for building and running connected systems.
It is a new breed of communications infrastructure built around the
Web services architecture.
in technical terms
Windows Communication Foundation is Microsoft's unified programming
model for building service-oriented applications with managed code.
It extends the .NET Framework to enable developers to build secure
and reliable transacted Web services that integrate across platforms
and interoperate with existing investments. Windows Communication
Foundation combines and extends the capabilities of existing
Microsoft distributed systems technologies, including Enterprise
Services, System.Messaging, Microsoft .NET Remoting, ASMX, and WSE
to deliver a unified development experience across multiple axes,
including distance (cross-process, cross-machine, cross-subnet,
cross-intranet, cross-Internet), topologies (farms, fire-walled,
content-routed, dynamic), hosts (ASP.NET, EXE, Windows Presentation
Foundation, Windows Forms, NT Service, COM+), protocols (TCP, HTTP,
cross-process, custom), and security models (SAML, Kerberos, X509,
Creating a Webservice Proxy with jQuery:
WCF Security Guidance, Video Index:
WinHttpCertCfg och CertMgr:
X.509 Certificates in .NET
Importing Certificates Using MMC (biztalk...)
Eight tips for working with X.509 certificates in .NET
Fundamentals of WCF Security:
The page you are requesting cannot be served because of the extension configuration.
If the page is a script, add a handler. If the file should be downloaded, add a MIME map."
To verify that the svc file type is mapped correctly in IIS 7.0
1.Open a command prompt window and type "start inetmgr" to open the Internet Information Services (IIS) MMC snap-in.
2.In the left pane, expand the node with the computer's name, then expand the Web Sites node, and then select the Default Web Site.
3.Double-click Handler mappings in the Features View.
4.In the list of application mappings, verify that the .svc file is mapped to the aspnet_isapi.dll. If the file has not been mapped:
4.1.Click Add Managed Handler.
4.2.Type "*.svc" into the Request path:.
4.3.Type "System.ServiceModel.Activation.HttpHandler, System.ServiceModel, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b77a5c561934e089" into the Type textbox.
4.4.Type "svc-Integrated" into the Name: textbox.
4.6.Click "Add Script Map".
4.7.Type "*.svc" into the Request path:.
4.8.Type "%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" into the Executable: text box.
4.9.Type "svc-ISAPI-2.0" into the Name: text box.
4.10.Using the Move Up/Move Down controls, ensure that the managed handler (svc-Integrated) appears before the aspnet_isapi (svc-ISAPI-2.0) handler in the list.