What is the difference between self-hosting and IIS-hosting in WCF?

Question

ICSM Computer · Answer

The main difference between self-hosting and IIS-hosting in WCF lies in
who controls the service lifecycle and what protocols are supported. Here's a detailed comparison:
1. Hosting Control
Feature
Self-Hosting
IIS-Hosting
Service lifecycle
Controlled by your application code (ServiceHost)
Managed by IIS — automatic activation
Process management
Your app must start and keep the service alive
IIS handles process lifecycle
Manual setup required
Yes (write code to open/close host)
No (service activates on HTTP request)
2. Supported Protocols
Feature
Self-Hosting
IIS-Hosting
HTTP
Yes
Yes
TCP, Named Pipes, MSMQ
Yes
No (unless using WAS)
Flexibility
High — supports all bindings
Limited to HTTP (IIS 7+ supports WAS for others)
3. Deployment and Scalability
Feature
Self-Hosting
IIS-Hosting
Hosting environment
Console app, Windows Service, WPF/WinForms
IIS web server
Suitable for
Lightweight apps, internal tools, testing
Enterprise, production web services
Scalability
Manual load balancing required
Built-in scalability, process recycling
4. Security and Monitoring
Feature
Self-Hosting
IIS-Hosting
Built-in security
Must be coded or configured manually
IIS provides integrated authentication, SSL
Logging/Monitoring
Manual setup or third-party tools
Built-in IIS logging and monitoring
Example of Self-Hosting
ServiceHost host = new ServiceHost(typeof(MyService));
host.Open();
Console.WriteLine("Service is running...");
Console.ReadLine();
host.Close();
Summary
Aspect
Self-Hosting
IIS-Hosting
Startup
Manual
Automatic
Protocols
All (HTTP, TCP, Pipes, MSMQ)
Primarily HTTP (others via WAS)
Control
Full control by developer
Managed by IIS
Scalability
Manual
Built-in
Ideal For
Testing, internal tools, non-HTTP services
Web-based services requiring stability

interview

What is the difference between self-hosting and IIS-hosting in WCF?

ICSM Computer

Can you answer this question?

1 Answers

1. Hosting Control

2. Supported Protocols

3. Deployment and Scalability

4. Security and Monitoring

Example of Self-Hosting

Summary

Liked By

Feature	Self-Hosting	IIS-Hosting
Service lifecycle	Controlled by your application code (`ServiceHost`)	Managed by IIS — automatic activation
Process management	Your app must start and keep the service alive	IIS handles process lifecycle
Manual setup required	Yes (write code to open/close host)	No (service activates on HTTP request)

Feature	Self-Hosting	IIS-Hosting
HTTP	Yes	Yes
TCP, Named Pipes, MSMQ	Yes	No (unless using WAS)
Flexibility	High — supports all bindings	Limited to HTTP (IIS 7+ supports WAS for others)

Feature	Self-Hosting	IIS-Hosting
Hosting environment	Console app, Windows Service, WPF/WinForms	IIS web server
Suitable for	Lightweight apps, internal tools, testing	Enterprise, production web services
Scalability	Manual load balancing required	Built-in scalability, process recycling

Feature	Self-Hosting	IIS-Hosting
Built-in security	Must be coded or configured manually	IIS provides integrated authentication, SSL
Logging/Monitoring	Manual setup or third-party tools	Built-in IIS logging and monitoring

Aspect	Self-Hosting	IIS-Hosting
Startup	Manual	Automatic
Protocols	All (HTTP, TCP, Pipes, MSMQ)	Primarily HTTP (others via WAS)
Control	Full control by developer	Managed by IIS
Scalability	Manual	Built-in
Ideal For	Testing, internal tools, non-HTTP services	Web-based services requiring stability