Comment Feed for Channel 9 - WPF 3.5 SP1 App Model with Jennifer Leehttp://video.ch9.ms/ch9/d969/fe50fb49-1414-40d8-95fc-375774f1d969/WPF-35-SP1-App-Model-with-Jennifer-Lee_100.jpgChannel 9 - WPF 3.5 SP1 App Model with Jennifer LeeI spoke with Jennifer Lee about what's new in the Application Model realm for WPF 3.5 SP1. Topics include the improved cold start, splash screen and a demonstration of HTML and XBAPs using the new WebBrowser control.
Looking for more than application model? Check out the WPF 3.5 SP1 Overview video
enTue, 03 Mar 2015 20:27:42 GMTTue, 03 Mar 2015 20:27:42 GMTRev9Re: WPF 3.5 SP1 App Model with Jennifer Lee
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.

posted by CKurt

]]>
http://channel9.msdn.com/Blogs/AdamKinney/WPF-35-SP1-App-Model-with-Jennifer-Lee#c633465283190000000
Fri, 16 May 2008 09:51:59 GMThttp://channel9.msdn.com/Blogs/AdamKinney/WPF-35-SP1-App-Model-with-Jennifer-Lee#c633465283190000000CKurtRe: WPF 3.5 SP1 App Model with Jennifer Lee
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.

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.

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.

posted by DigitalDud

]]>
http://channel9.msdn.com/Blogs/AdamKinney/WPF-35-SP1-App-Model-with-Jennifer-Lee#c633466844650000000
Sun, 18 May 2008 05:14:25 GMThttp://channel9.msdn.com/Blogs/AdamKinney/WPF-35-SP1-App-Model-with-Jennifer-Lee#c633466844650000000DigitalDudRe: WPF 3.5 SP1 App Model with Jennifer Lee
Will the WPF WebBrowser control be a DependencyObject and therefore bindable? Could I, for example, do this:

<WebBrowser DocumentText="{Binding MyHtmlProperty}" />

??

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

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

posted by JenniLe

]]>
http://channel9.msdn.com/Blogs/AdamKinney/WPF-35-SP1-App-Model-with-Jennifer-Lee#c633470148530000000
Thu, 22 May 2008 01:00:53 GMThttp://channel9.msdn.com/Blogs/AdamKinney/WPF-35-SP1-App-Model-with-Jennifer-Lee#c633470148530000000JenniLeRe: WPF 3.5 SP1 App Model with Jennifer Lee
For my purposes I would only need to set the HTML string (a "OneWay" binding) since the browser control itself wouldn't be doing any updating. Perhaps I could define an attached property or something that called NavigateToString() when it was set?

I think the old example you often see of a WPF app that reads RSS feeds would be well-served by a simple property on WebBrowser that lets you bind directly to a string - that way the browser could be bound to the selected item in the feed and simply display
it as the user navigates through the list of items.

Matt

posted by mabster

]]>
http://channel9.msdn.com/Blogs/AdamKinney/WPF-35-SP1-App-Model-with-Jennifer-Lee#c633470944270000000
Thu, 22 May 2008 23:07:07 GMThttp://channel9.msdn.com/Blogs/AdamKinney/WPF-35-SP1-App-Model-with-Jennifer-Lee#c633470944270000000mabsterRe: WPF 3.5 SP1 App Model with Jennifer Lee
Yes, that sounds like the right thing to do. You might also try writing a custom control that has a child WebBrowser, if you want encapsulation.

We are working on putting together some WebBrowser samples, and I think the RSS scenario would be a good one, as well.

I am using the new wpf webbrowser control in .net 3.5 sp1 and I need some help trying to use the virtualearth control. Each time i try to load a map the internet explorer information bar
appears with the message "To help protect your security, your web browser has restricted this file from showing active content that could access your computer". Any ideas how I can prevent this from occuring?