Content Preview: rss
25 days ago
As already the Weepies said in their very own way, things inevitably change. Nearly 8 years ago, I joined one of the best companies I've always known and I probably will know in the future. Working for netzkern was not only fun and a great experience, the team became somewhat like family to me during these years. The things I learned in my various roles and having very different responsibilities were more valuable to me than most other things I came across in my life (including the years at school, university and in all other educational programs combined). But as all great times come to an end, so does this endeavor. Tomorrow I will start my new job at Avanade, an international IT consulting company founded by Microsoft & Accenture. I feel a little bit like the former Chief Software Architect of Microsoft, Bill Gates, these days (see the great video "Bill Gates' last full day at Microsoft"). As you can imagine, this change has been in the planning for quite some ...
45 days ago
Okay guys, here is a very short list of the good and bad things in SharePoint 2010 from my perspective as software architect. Let's get started... The Good: Improved integration with VisualStudio 2010 that goes beyond the available features in VSeWSS. Support for LINQ and extended support for XSLT, which will - among other things - be used for list generation (although CAML will unfortunately stay an important part of the platform). Better AJAX support (and I don't mean the Ribbon UI, because CSS and JavaScript have nothing to do with AJAX). The Bad: SharePoint 2010 will be based on .NET 3.5 and Windows Workflow Foundation 3.5 (instead of the rewritten version of 4.0). This is especially sad because I rejected WF 3.x from the very beginning and was very pleased to see Microsoft creating a complete rewrite. Unknown: It is still unknown if Microsoft fixed the annoying performance and development issues with undisposed objects (see ...
47 days ago
Before continuing my series on SharePoint and Sitecore development from a software engineering perspective, I created a revised edition of my last post. The series now covers the CTP version of VSeWSS 1.3, which makes developing custom SharePoint solutions much easier. Table of Contents: - Introduction (Part 1) - Installation and General Architecture (Part 2) - Configuration (Part 3) - Customization and Designer Experience (Part 4) - Integration with Developer Tools (Part 5) - Feature Deployment (Part 6) - API und Data Model (Part 7) - Integration with other systems (Part 8) - Conclusion (Part 9) By the way, part 6 is currently in development and will hopefully be ready in a couple of weeks.
58 days ago
There are great things to come in .NET 4.0, especially Code Contracts and the Parallel Extensions. Take a look: http://msdn.microsoft.com/de-de/magazine/ee428166(en-us).aspx
59 days ago
There has always been one area in the religious war between .NET and JEE where Java Enterprise developers had the right to lean back and start smiling: Packaging and deployment features for web and service applications. While Java EE has been offered very well integrated mechanisms like JAR, WAR, EAR and OSGi for years now, deploying .NET web and service application has always been cumbersome, painful and half-baked at best. Of course there are XCOPY, the "Publish..." feature in Visual Studio, the Web Deployment Project Template for Websites and Web Applications (although that did not always work as expected in the latter case), the option to use MSI, and numerous application specific mechanisms like the SharePoint Solution Framework and the Sitecore Packaging API, but lets be honest, deploying web applications with .NET is a painful obstacle course and if you don't know how to handle certain build and automation tools (especially MSBuild, NAnt and FinalBuilder), it really, ...
