Ian Ellison-Taylor and Kevin Gjerstad on WPF 3.5 SP1

Posted By: Adam Kinney | May 12th @ 9:45 AM

Dr. Sneath speaks with Ian Ellison-Taylor and Kevin Gjerstad about new improvements and features in WPF 3.5 Service Pack 1. Topics of the conversation range from Graphics, Deployment, Performance, Application Model and Tools. And while discussing the current state and the future of WPF a few applications are mentioned including Lawson "Mango" and Yahoo Messenger .

Not only does this video provide you with a great overview of WPF 3.5 SP1, but it is kicking off WPF Week on Channel 9. Each day this week we’ll be publishing a video focused on one area of WPF to give you a detailed look at what’s new.

SP1 Download links:

Tags: 3D, DirectX, Ian Ellison-Taylor, Interoperability, Kevin Gjerstad, Silverlight, Visual Studio, WPF, WPFWeek

Rating:

Views (23,618)

Comments (22)

Downloads

DigitalDud

When did WPF get to 3.5? I thought it was 1.0.

littleguru
let's partaaaay!

DigitalDud wrote:

When did WPF get to 3.5? I thought it was 1.0.

Jumped right into it.

Ian Ellison-Taylor

Ah, good point - we should be clearer about what we're talking about here. v1 of WPF shipped first as part of .Net 3.0 (and included in Vista), our next version was in .Net 3.5 and what we're talking about here is our 3rd release as part of .Net 3.5 SP1.

Sorry for the confusion,

Ian.

dnjake

The 3.5 refers to the .net version. The problem I saw with the additions of WPF that shipped with .net 3.5 has to do with the documentation. The documentation of the WPF base release is generally pretty good. The documentation for the first set of additions is skimpy at best and not integrated with the base documentation. You need to a better job with the documentation of future additions.

mawcc
Make it so

After reading Scott Guthrie's (excellent as usual) description of all the updates in VS 2008 & .NET Framework 3.5 SP1, it seems as if WPF gets more updates from 3.5 RTM to 3.5 SP1 as it has from 3.0 RTM to 3.5 RTM.

So the versioning might seem a little bit odd, but of course WPF is part of the larger .NET Framework and thus doesn't have it's own version numbers.

figuerres
???

SOunds almost like .Net 3.6 and VS 2008 + .5

lot's of good stuff in them bits...

now just gotta wait for them to bake and cool off to use them Smiley

I have an app on 60 desktops that I want to move from .net 2.0 to 3.5 soon... must find out if the boot strap will work for a low-trust user account ??

figuerres
???

Ian Ellison-Taylor wrote:

Ah, good point - we should be clearer about what we're talking about here. v1 of WPF shipped first as part of .Net 3.0 (and included in Vista), our next version was in .Net 3.5 and what we're talking about here is our 3rd release as part of .Net 3.5 SP1.

Sorry for the confusion,

Ian.

I just posted and if not covered in the video:

Can a non-admin user who does not have full access but has a .net 2.0 app today get an update that will boot-strap to .net 3.5 and then get the app w/o an admin logon??

it's a click once app on about 60 pc's that are in remote locations.

if an admin login is required then it will take days to update them.

so to recap:

can I boot-strap from a click once app with net 2.0 to a new version of the app with .net 3.5 with a limited user account?

PerfectPhase
"This is not war, this is pest control!" - Dalek to Cyberman

mawcc wrote:

After reading Scott Guthrie's (excellent as usual) description of all the updates in VS 2008 & .NET Framework 3.5 SP1, it seems as if WPF gets more updates from 3.5 RTM to 3.5 SP1 as it has from 3.0 RTM to 3.5 RTM.

Looks like DBPro's not getting any love Sad

CRPietschmann
Chris Pietschmann

Why would you add new features in a service pack to the framework? Why not just release a feature pack now, then bake those features into the next point release of the framework?

By adding new features in a service pack, you'll generate potential confusion. I'll say my app requires .NET 3.5, but then I'm using some SP1 features, then my client installs the app and it doesn't work because they don't have SP1 installed.

I can understand improving performace in a service pack, but why add new features to a service pack? Why not release them in a feature pack, like how the ASP.NET team did with the ASP.NET AJAX Extensions v1.0?