WPF 3.5 SP1 App Model with Jennifer Lee | AdamKinney

CKurt
while( ( !succeed=try() ) ) { }

Hi, nice video !

Still can't help but wonder why they just didn't call it "WPF 3.6" it would be allot more clearer for developpers, because some things just don't run on 3.5 , most things are not updates/bug fixes but new features.

OrigamiCar

PLEASE - enough with starting every sentence with 'So...'.

I know this seems to be the Microsoft way, but in this video almost every sentence Jennifer says begins so it.
Normally I don't notice these kind of things, but it was really off putting for me!
Sorry to rant - interesting information, but the delivery just grated on me.

shatterstar6457

I know this is off-topic, but she's hot!.

John Melville-- MD
Equality Through Technology

DukeNukem wrote:
Hi, nice video !

Still can't help but wonder why they just didn't call it "WPF 3.6" it would be allot more clearer for developpers, because some things just don't run on 3.5 , most things are not updates/bug fixes but new features.

Agreed -- or even just drop the whole SP and call it .Net 3.51

As hard as it may be to covince developers that its "a service pack with features" convincing users is even harder.

BTW I like the agility of the wpf team to come out with three really solid (looking) releases in such a short time frame. I just think that there is no reason to conflate a service pack with a release.

justbitchin

Why can't you guys remember to post a link to the LOW-RES file on every video that you do? Mad

It's very irritating when downloading with BITS to have to wait on 600Mb files.

---dup---dup---

braveness23

shatterstar6457 wrote:
I know this is off-topic, but she's hot!.

Beavis has spoken!

DigitalDud

OrigamiCar wrote:
PLEASE - enough with starting every sentence with 'So...'.

I know this seems to be the Microsoft way, but in this video almost every sentence Jennifer says begins so it.
Normally I don't notice these kind of things, but it was really off putting for me!
Sorry to rant - interesting information, but the delivery just grated on me.

I've heard its a northwestern thing.

mabster

Will the WPF WebBrowser control be a DependencyObject and therefore bindable? Could I, for example, do this:

??

ps. You're right about the "so", guys - both Adam and Jennifer started almost every sentence with it! Expressionless

JenniLe

Soooo... (point taken) Wink

I'm taking this to mean you want to be able to bind an HTML string to some property on the WebBrowser and cause the WebBrowser to navigate when the data bound to the property is updated.

A few things here -

Yes, the WebBrowser control is a DependencyObject. However, we would have to expose navigating to an HTML string as a property (specifically, a DependencyProperty) for the databinding to work, and for it to work in XAML, which we do not. The functionality of navigating to an HTML string is achieved by calling the WebBrowser.NavigateToString() method. You will need to implement your scenario in code by calling the NavigateToString() method.

Therefore, the answer is NO, you could not do this:
<WebBrowser DocumentText="{Binding MyHtmlProperty}" />

I can see how the above would be useful and convenient. The change would mean you could 'get' the html string loaded as well as 'set' it (which is what the method achieves). We may look into adding it for a future release. As always, your feedback and specific affected scenarios certainly help in these matters, so please keep it coming!

Thanks!
Jennifer