July 2008 MSDN mag on-line

submitted by wisemx 2 days, 3 hours ago

msdn2.microsoft.com — Come and get it. ;-) read more...

add a comment | category: ASP.NET | Views: 18

Microsoft cracking down on community extensions

lovethedot.blogspot.com — Microsoft released a tool called Microsoft Source Analyzer, or StyleCop. It analyzes source code for standards violations. It's a 1.0 release, so it doesn't do some things ... like have a published API for custom rules or MSBuild integration. So the community dug in and figured out how to do these things and now MS is firing off license-violation emails. Don't they get it? The community wants to use the product, but it's too limited ... these extensions help make it better. read more...

3 comments | category: C# | Views: 352

IIS7 GAC Viewer

submitted by wisemx 2 days, 12 hours ago

blogs.iis.net — DiscountASP.net who has been a very close partner of the IIS Team leading several offerings of our platform - including IIS Manager Remote Delegated Access to the Web Site and many other cool tools - has just built and released yet another cool module that extends the IIS Manager capabilities by having a GAC Viewer for their customers. read more...

add a comment | category: ASP.NET | Views: 5

Literate Programming - Before we discuss the acronyms.....

submitted by dcarr 3 days, 4 hours ago

literateprogramming.com — All to often (as it is far easier) people relish the technical discussions without digging into the 'how and why does this fundamentally help me' at a few levels of abstraction higher. I for one think code comments are the exception not the rule. Why? 1) If you need to comment it you likely need to refactor it. THis is why ReSharper is so mandatory. It's the practice not the tool. Why refactor? 90% of most cost is in maintenance. 2) Code comments are as often as node misleading and incorrect as they are not kept up to date. 3) Improvements in automated developer generated API docs are sufficient in most cases. This leaves the 'domain-specific' or 'contextual' documentation as the mandate. Here your focus is not on the how, but the why and the what. If you discuss the abstraction's rationale, and reason for existence, not how it internally works, you're safe. There are always exceptions to any rule however this is just to get the ideas flowing. For example, CruiseControl.NET is a fantastic tool. However it's not about the tool, it's about the practice. The fact that Microsoft 'patterns and Practices' has no ' and tools' at the end is because tools change quickly and their abilities dramatically but the concepts from 10 years ago are still not used if there is in general no easy 'tool support'. People don;t like to think this iway in general and if there was perhaps one reason some evolve into 'architects' or whatever you want to call them, it is this. The site listed helps.. DAmon read more...

add a comment | category: Architecture | Views: 7

Dependency Injection is Dead!

blogs.msdn.com — The author claims that AOP-assisted Dependency Resolution, where dependencies are resolved on-demand without plumbing code and use of factories, can supersede Dependency Injection... at least in some scenarios. A refreshing view on a topic that tends to become sanctified and therefore undiscussed in our community. read more...

1 comment | category: Architecture | Views: 365

Blog Engine.NET1.4 Upgrade Guide

published 4 days, 16 hours ago, submitted by mdopp 5 days, 1 hour ago

nyveldt.com — The upgrade process is fairly easy but there are a few things to be aware of. more.... read more...

add a comment | category: Community | Views: 113

NHIbernate 2.0 Goes Beta 1 after Microsoft ‘Linq to Entities’ receives

published 5 days, 4 hours ago, submitted by dcarr 5 days, 9 hours ago

damon.agilefactor.com — The first official beta for NHibernate 2.0 was released today. This comes on the heels of the damaging ‘boycott’ of the Microsoft ‘Linq to Entities’ upcoming release, which was anticipated to be a serious competitor to NHibernate. LAST MINUTE UPDATE FROM THE NHIBERNATE TEAM There has been a change in how NHibernate is packaged as the core and contrib aspects now have dedicated locations. Since NHibernate 2.0 Alpha 1, ONLY THE CORE of the project is included at the link above. The Contrib Projects are now in a dedicated location: http://sourceforge.net/projects/nhcontrib There are a few new projects that are essential to investigate for your needs (for example the Burrow project). Also be sure to visit the wiki for these significant projects: http://nhcontrib.wiki.sourceforge.net See the end of this post for a partial list of these contrib efforts. The team at domain.dot.net has been working with 2.0.X since the first alpha, and following the progress of the trunk. In our opinion this beta has the high quality of prior betas and we recommend it for non-critical systems immediately as your risk policy allows. We’re working on a more detailed analysis coming soon on some of the key improvements. To download the code direct from the trunk use this SVN URL: https://nhibernate.svn.sourceforge.net/svnroot/nhibernate This is no minor update, as with this release they will align with the widely used and praised ‘Hibernate 3.2’ for Java. Here is a listing of the planned new features which are represented to varying degrees of complexness in this beta: read more...

4 comments | category: Linq | Views: 211

Google App Engine: the Goods and the Bads

itscommonsensestupid.blogspot.com — After trying Google App Engine for some time, there are goods and bads to it. Here's a list: read more...

add a comment | category: Other | Views: 5