I've been having a discussion with some of my colleagues regarding how good a job we've done (and are doing) at explaining what WinFX actually contains.
In the interests of keeping everyone on the same page, I'm talking about a description of WinFX like this:
WinFX is the .NET Framework 2.0 with the addition of four specific new technologies: Windows Presentation Foundation, Windows Communication Foundation, Windows Workflow Foundation, and Infocard (codename).
The part I'm concerned about is the part in bold ie that WinFX is the .NET Framework...with additional pieces.
Do you think that the bulk of developers realise this? It's really easy for us, who live with this stuff every day, to forget that most people have real lives to live and so might have missed the fact that WinFX is an evolution of the .NET Framework, so all of the good stuff you associate with .NET accrues to WinFX.
It may be a non-issue but I wanted to see if anyone had experience of this being a problem...or whether it's just me.
Feel free to email me or leave a comment if you have a view.
Well, I'm really impressed by Ian's observation:
>>It's really easy for us, who live with this stuff every day, to forget that most people have real lives to live <<
Microsoft, and now Sun, keep ramping up the number and breadth of development packages which play together and don't - - it is quite dizzying to a developer who needs to support a number of platforms - or choose a platform.
I wonder if the "real" marketing ploy is for a vendor to make so many packages which require so much investment to figure out, that a developer would stick with whatever we invest so much time getting familiar with. [ending on a preposition, geezsh :-)].
If that's not the case, then much more time needs to be spent funneling in developers with varied familiarity -- that is, if I need to look away from Microsoft for a year, I could really use great documentation to find my way back. I agree that this sounds like COM/DCOM/ActX, etc. IUnknown++