Reply to thread

Message

This is true for the switch from V1.1 to V2.0 but not for v2.0 to v3.0. When you install Framework 3.0 the Framwork V2.0 is installed first. After this the WCF assemblies are added. So .NET 3.0 is .NET 2.0 with some new assemblies.

Indigo (WCF) and Avalon (WPF) was introduced 2 years ago for Windows Vista. They decided to make it backwards compatible to Windows XP and had to find a name for this. Unluckily they choosed ".NET Framework 3.0" for marketing reasons.

.NET Framework 3.0 is:

1) NET Framework 2.0
2) WCF (former Indigo)
3) WPF (Windows presentation Foundation, former Avalon (has all this XAML stuff))
4) WF (Windows Workflow Foundation)

It is true that you have to be careful with new technologies but the current use of remoting in the TV server is outdated. I think we both agree on this. And if you want to host a web service in XP home without IIS you HAVE to go with WCF (or use the even more outdated Web Service Extension).

From my experience WCF works very well. As I posted before my company is currently developing a business solution with WCF for allmost a year and we do not have any special problems.

WCF is standard SOAP. So this schould not be an issue.

Regards,
Christoph

<blockquote data-quote="chrispi" data-source="post: 125430" data-attributes="member: 20307">This is true for the switch from V1.1 to V2.0 but not for v2.0 to v3.0. When you install Framework 3.0 the Framwork V2.0 is installed first. After this the WCF assemblies are added. So .NET 3.0 is .NET 2.0 with some new assemblies.Indigo (WCF) and Avalon (WPF) was introduced 2 years ago for Windows Vista. They decided to make it backwards compatible to Windows XP and had to find a name for this. Unluckily they choosed &quot;.NET Framework 3.0&quot; for marketing reasons..NET Framework 3.0 is:1) NET Framework 2.02) WCF (former Indigo)3) WPF (Windows presentation Foundation, former Avalon (has all this XAML stuff))4) WF (Windows Workflow Foundation)It is true that you have to be careful with new technologies but the current use of remoting in the TV server is outdated. I think we both agree on this. And if you want to host a web service in XP home without IIS you HAVE to go with WCF (or use the even more outdated Web Service Extension). From my experience WCF works very well. As I posted before my company is currently developing a business solution with WCF for allmost a year and we do not have any special problems.WCF is standard SOAP. So this schould not be an issue.Regards,Christoph</blockquote>

[QUOTE="chrispi, post: 125430, member: 20307"] This is true for the switch from V1.1 to V2.0 but not for v2.0 to v3.0. When you install Framework 3.0 the Framwork V2.0 is installed first. After this the WCF assemblies are added. So .NET 3.0 is .NET 2.0 with some new assemblies. Indigo (WCF) and Avalon (WPF) was introduced 2 years ago for Windows Vista. They decided to make it backwards compatible to Windows XP and had to find a name for this. Unluckily they choosed ".NET Framework 3.0" for marketing reasons. .NET Framework 3.0 is: 1) NET Framework 2.0 2) WCF (former Indigo) 3) WPF (Windows presentation Foundation, former Avalon (has all this XAML stuff)) 4) WF (Windows Workflow Foundation) It is true that you have to be careful with new technologies but the current use of remoting in the TV server is outdated. I think we both agree on this. And if you want to host a web service in XP home without IIS you HAVE to go with WCF (or use the even more outdated Web Service Extension). From my experience WCF works very well. As I posted before my company is currently developing a business solution with WCF for allmost a year and we do not have any special problems. WCF is standard SOAP. So this schould not be an issue. Regards, Christoph [/QUOTE]