Contents tagged with WinFx
-
.NET Framework 3.0
Today, as Ecuador was beating Poland in the World Cup (way to go Ecuador!), Somasegar was announcing that what was previously known as WinFX (WCF, WPF, WF) plus other technologies like WCS (formerly Infocard) are an integral part of .NET Framework 3.0. Furthermore, *all* these components will be available for Vista, 2003 Server, and XP. I think it's time we download Beta 2.
-
Remoting vs. WCF becomes S/O vs. C/S
A few days ago I talked about my question on using Remoting or WCF. Well, I will now try to summarize the discussion on the RD list. First the arguments in favor of WCF:
-
Whither remoting?
You already know I'm a
new toy junkieearly adopter, so when a project that is just starting needed a light smart client talking back to a business logic server I immediately suggested using WCF. To my surprise, another architect and *my* lead developer preferred remoting, their reason? They've had very good experiences with remoting, my reason? If this system is going to live 5 years, it better uses the most looking forward technology. As I am an RD, I naively asked in the RD list for reasons to use WCF over remoting, and I got a few good responses but then the remoting camp reacted and gave good reasons for *not* using WCF. So it seems like the question is more interesting than what I thought and, before summarizing the answers I got, I would like to ask you what you think: if you were to create a client-server like application in your *intranet* would you use web services or remoting? Why? -
What is WinFX– an Executive Summary
Here you will find a *very high level* overview of WinFx. Good as a first step on selling the use of WinFx in that next projecto to your CIO. Courtesy of the nice guys at IDesign (also authors of these very usable coding standards).