It's been an interesting afternoon! At 4pm Pacific Time today (i.e. Feb 1st 2007 0000 GMT), the Windows version of the WPF/E December 2006 CTP runtime expired somewhat unexpectedly and prematurely (it was intended to timebomb in mid-February, but I guess we got that wrong). If you visited a page which required WPF/E, you'd see the following error message:
Within minutes, the "WPF/E" SWAT team (ably led by Joe Stegman and Mike Harsh) scrambled into action. It's fortuitous that we were in the final stages of getting the February CTP release ready, so we pushed it out this evening, a few days earlier than planned. Apologies for the lack of notice - this is a little embarrassing on our part, but hey - it proves that we're human and not the Borg after all! Here's links to the key components:
I'd recommend uninstalling the previous runtime before installing this fresh one.
As a workaround for anyone who really needs to keep running the December 2006 CTP on a Windows platform for a few more days, you can simply set the system clock back to a date prior to February 1st and you'll be all set. The Mac runtime is unaffected, but obviously the updated samples that we've posted are compatible with the February release.
We'll post an updated SDK and a list of changes as soon as we possibly can; in the meantime, the agHost.js should get you started.
We're sorry for any inconvenience caused!
Update - Joe has posted a list of the new features here: http://blogs.msdn.com/jstegman/archive/2007/01/31/feb-ctp-is-live.aspx
So I realize I haven't posted an update for a while... but the big-news is we just shipped the Feb CTP
Looks like the agile process came in handy! :-)
Turns out the new CTP for WPF/E shippped a little early , good news for us, scramble for Microsoft -...
Microsoft has hastily released the February 2007 CTP of the Windows Presentation Foundation Everywhere
Looks like there was a boo boo in the December CTP of WPF/E and it prematurely time bombed. Tim Sneath
Worth noting that you can now get your hands on the following: Beta 2 of Expression Blend - tons of bug
Tim Sneath has a post over here about a bit of a slip-up with the "WPF/E" CTP which means that it...
Please ensure there's an auto-update for the release version!
If this version had at least known about a link to send the user to automatically to get help/download the new version it would really help, at present it could just totally confuse a novice user.
Does the SDK and the Vs template still remains the same dec sdk or one need to download them too ?I ve uninstall everybits of dec sdk the runtime and vstemplate now i want to reinstall all the new bits.
Since we shipped WPF, I moved on to work on WPF/e. What is WPF/E? WPF/e is a cross-platform browser plug-in
Simon, absolutely - that's 100% part of our release criteria. WPF/E in its current CTP form isn't suitable for deployment on the home page of a consumer-facing site, and that's deliberate - we really don't want people like my parents installing these early releases and risking the integrity of their machine.
Shreeman, we'll have an updated SDK very soon, but in the interim Mike Taulty offers a simple workaround:
Tim Sneath : WPF/E Second CTP Shipped 12월 CTP가 Expire되어 새로 2월 CTP를 공개하였습니다. 원래는 2월 중순에 Expire될 것으로 생각했는데,
....then add the following files from the "WPF/E" download to this new directory: install.msi, MozillaControl1712.exe, WPFE.dmg, xcpctrl.cab, and xcpctrl.xpi...................
WHERE ARE THESE FILES. Does anyone know?
Must I sell my soul to some MS deamon to find them.
They are not in the install, and the MSDN sites seem to disavow them. Would be nice to have though
i also am looking for these files? i got all but the .cab and .xpi
Im sure i can live without the cab, but i dont know what the xpi is!
any feedback would help.