Visual Studio 2008
I remember looking for a way to start a single project in a solution having multiple projects. Now, the Web Developer Tips team has put a nice post about it.
David Hayden has a new screencast on Data Access Application Block.
Somasegar has a nice post on SketchFlow – a add on for Expression Blend 3. It seems to be a great tool for providing prototypes in the early stages of the project. You might also take a look at Balsamiq for creating great UI mockups in no time.
Moses wrote a few days ago about his wish of having something like DataLoadOptions for ObjectContext. Stuart Little wrote today a very interesting post with a few extensions to ObjectQuery.Include to make it strongly typed. I think that it could be something that Moses can use for his approach.
Alex James continues his series of tips showing how we can use AttachTo() in combination with projections and avoid loading unnecessary properties.
Scott Galloway has a nice post on how to build a ASP.NET control to combine and compress CSS files, reducing the number of requests and the traffic between the client and the server.
If you are looking for a DataReader – JSON converter, go check Rick Strahl post!
Yves continues his saga showing the importance of assertions for controlling the effects of commands.
Peter Bromberg has a nice overview on Fluent NHibernate automapping.
After Oxite and Kobe, there is a lot of debate on the framework itself.
Karl Seguin asks whether ASP.NET MVC is half-baked or not. Jeffrey Palermo has a nice list of cases when ASP.NET MVC should NOT be used. Jeremy Miller has its own list of pros and cons for using ASP.NET MVC. Rob Conery has an excellent post on why we should learn MVC.
Scott Allen has a very interesting post on model binders.
CoNatural continues the series on asynchronous programming showing how to search asynchronously with ASP.NET MVC and JQuery.
Greg and Ayende continue their debate on the repository pattern. Greg says that having a repository makes an explicit boundary around our domain. By simply having a contract of those boundaries we can adhere to the “onion architecture”. Ayende replies to Greg about the lack of explicit boundaries in cases such as transparent lazy loading. He also presents his concerns about the need of abstracting away the persistence without having a clear requirement in this direction.
I think that both of them have interpreted each other statements without having the other’s complete context and as Ayende says in his post, not having the complete context invalidates the entire argument.
Luis Abreu talks about repositories in S#arp.
Karl Seguin starts a very interesting series of posts showing how we can roll our own validation framework.
Ayende has a nice post about the differences between infrastructure and architecture.