ust caught this little gem from John Lam on Twitter
Several drops ago we introduced a ViewModel composition spike. The purpose of this spike was to introduce a different way to compose your UI that WPF offers. That is instead of having your views and regions be UI-Elements, having them as pure models.
Scott has a great post where he dispels the following two myths about using LINQ to SQL.
LINQ to SQL requires you to start with a database schema.
LINQ to SQL requires your classes to implement INotifyPropertyChanged and use EntitySet<T> for any associated collections.
First let me start off by allaying all your fears, “No it’s not another factory”. 🙂
For a while we’ve been hearing a lot of requests from customers for patterns & practices to deliver guidance on SharePoint. For several weeks now we’ve been exploring this space,
On the forums, Bil asked the questions below.
Just wondering about guidance here. I have clients who are not ready or able to move to 3.5/VS2008 yet but need to start developing new Smart Client applications. They’re also not ready to move to WPF as they don’t see a lot of value in it for the type of apps they need.
Early on we decided that we needed the RI to have a better look in feel so that it delivered a more real world WPF experience. We hired a design firm to create XAML proofs based on our implementation. The process on their end was two fold. First there we a graphic designer who created non XAML proofs. Then a XAML developer converted those proofs to XAML.
There's been a bunch of talk on the net comparing Prism to other frameworks that exist. In many cases comparisons are being made based on feature parity and such. I think it's important to make the distinction of why Prism is different.
It can be done! Go read Chris’s post for more. Jared if you are listening, we need this for PrismContrib. (which I still need to post about)
What do you do before you head over to a day of grueling open-space sessions? Why head to Ruby’s diner for breakfast of course.
Here’s my table with Jeremy Miller, Jason Grundy and Jarod Ferguson.
We weren’t the only ones who showed up.
Clarification: We are not against using Unity, the Prism RI uses Unity, and we’ve been very happy with it’s implementation. We are after all one of Unity’s first internal customers. On the other hand, we want to make it easier for customers to use their IOC container of preference,