Best WPF/E Description Yet

Thursday, March 23, 2006

Jon Galloway has the best description of WPF/E I've seen yet. Most interesting details:

target plugin size less than 2 MB
MSIL engine included: my assumption is that you will first compile your C#, vb, etc. into some kind of client WPF/E DLL?... if so you could get something like Ruby support too... just wait till you see what that does to Ruby on Rails. ;)
Supports: Audio, Video, Vector Graphics, Composition, etc.

So, basically, if I was working for Adobe/Macromedia, I would be pissing my pants right now. Microsoft has a tendancy to take good ideas and do them right.

http://weblogs.asp.net/jgalloway/archive/2006/03/23/440933.aspx

7 Comments

Well, if you consider the fact that Microsoft takes 3 times to get anything right... sure...

Eric Newton - Thursday, March 23, 2006 8:40:00 PM

I like to say that WPF is like "Fire".

Lots of idiots will burn themselves with it, but when used right will give us all a warm fuzzy feeling :)

Sahil Malik - Thursday, March 23, 2006 9:15:00 PM

Therefore by definition, WPF/E is Fire-Browser. Kinda Foxy IMO.

Sahil Malik - Thursday, March 23, 2006 9:16:00 PM

Someone asked a question about support for other .NET languages at the Mix06 WPF/E session. The answer is that this will only work if the language compile to IL with no other dependencies. The presenter said that most of the other .NET languages (IronPython, etc.) require another DLL, and there's no support for referencing other assemblies.

Jon Galloway - Thursday, March 23, 2006 11:32:00 PM

Well, you don't really need to reference other DLLs if there is no support for it. I'm sure those compilers with other dependancies could bundle the dependancy classes together with the output DLL if they wanted (hell, you could probably merge the DLLs on your own if you had to).

Jesse Ezell - Friday, March 24, 2006 1:12:00 AM

Asina - Wednesday, December 3, 2008 2:17:27 AM

Semil - Saturday, December 6, 2008 9:48:27 AM

Comments have been disabled for this content.