Something on the way… there’s Umbraco again!

To be honest.. over the past 6 months I’ve been spitting against Umbraco. Have told aroudn that they will never be able to release version 3, that their codebase is unordered, the organisation of the devteam definitelly is terrible, etc. But… although I didn’t expect that they we’re going to make it, the first Release Candidate of version 3 is finally released. So I guess I need to say sorry to Niels Hartvig and all the others. I’ve to sent my best regards to them and congratulate them with this excellent release!

One of the coolest thing compared to the version I’ve seen before is the incredible cool wizard on the first run. It’s clear and usefull( it forces you to change the ‘admin’ password with the strange name ‘umbraco’ instead of the regular ‘admin’).
The setup of your datatypes is really simplistic and the folderstructure seemed to be cleared up a lot.

Working on my new posts on config management, I’ll properly try to create them for both Sitecore and Umbraco. As Umbraco is XCopy deployable, which is less recommended to do with Sitecore these days(which is not a bad thing). Hopefully will it prove the flexibility of my views on this subject.

So far: good job :D!

Sitecore Software Configuration Management

What a nice title: SSCM… 😉 During the last year(-s) I’ve seen how good configuration management should work for several specific projects. Since a year now, I’m trying to get everything ready to run in a non-custom way trough all steps of the buildprocess, with the primary focus on ‘making sure developers stay developers’. I don’t want to introduce new project roles such as Config Managers, I also don’t want to make the whole SSCM-thingie be modified per project.
Last but not least, in my opinion config management is the first part of the Software Factory vision.

As I don’t get the expected response from my employer on the plans I’ve introduced, I’ve decided to do it totally my own way by writing Whitepapers-like blogsposts.

So what will I build? In one sentence:
A structured CMS developer street with the solutions for data-design, automated deployment and consistent naming tools.

Why reinvent the wheel?
Well so far I’ve seen that we’re able to create such a solution for one specific product. This time it will be the way around: a solution for any CMS with Sitecore specific examples.

What to expect:

  1. Virtualisation
  2. Continuous Integration
  3. Guidances
  4. Design tools
  5. Reportage
  6. Customer expectation management

Become capable

There are way to many architects and lead developers in this world who really think they can create reusable and extremely scalable applications. I’m definitelly not going to give an example, there are way to much examples. And as a self-respecting developer you properly have worked with a solution like that.

When you don’t want to become such a jurk(!!!!), the Thursday Architectural Series of Microsoft is a good idea. Also take a look at the blog of Siemens’ Architect Michael Stal.
Next to it, there a books I suggest these days: The Software Factory Book

Here will my spam end for now :).

5.3.1: Validation Pipeline Component – Update

In this comment, Sander – of eFocus, a dutch Sitecore partner – is pointing me on a bug in my pipeline processor. I’ve to confirm his bug. It could be resolved by adding the following line after the retrieving of the original item and around the start and reject edit:

                //Retrieve the last saved version of the item

                Item orgItem = Context.ContentDatabase.Items[saveItem.ID, saveItem.Language, saveItem.Version];

 

                if (orgItem.Paths.IsContentItem)

                {

                    //Start editing the item and overwrite the field with the saved ones

                    orgItem.Editing.BeginEdit();

 

                    […]

 

 

                    //Reject the changes, savind will be done in a later stage of the pipeline

                    orgItem.Editing.RejectChanges();

                }

Just Remoting? Gimme WCF support!

I want to point on the following post of Runi Thomson, a former developer of the Sitecore:
http://runithomsen.blogspot.com/2007/04/net-remoting-removed-from-sitecore.html

He’s talking about the support of remoting in the early builds of 5.3. I’ve been blogging about it as well.
Runi is a way better developer as I’m, I’m 100% sure about that, but in this case he forgets about WCF. Enabling ‘just remoting’ for Sitecore would be a dramatical architectural mistake, as WCF includes way more possibilities but has the exact same pain while implementing. Implementing ‘just remoting’ will ‘just’ limit the system.

Runi is totally right on that Sitecore should include way more possibilities to communicate with other systems. It’s hardly impossible to make Sitecore the fundamental system  of an enterprise environment without customising the whole system…

Thanks Runi for refreshing the subject, making Ole and Jakob again aware of that we want to see them blogging and for inspiring me on to think again about WCF…

The world is moving

Yes I’m back from the mountains! Had some excellent days with wonderfull people around me. Sun, snow, snowboards, beers and some beautifull women ;-). It also have been some pretty good days to clear up your mind. That’s just necesarry sometimes!

While I’ve been relaxing, etc, the world of .NET development has started shaking! MIX ’07, ADO.NET vNEXT release changes, Silverlight, etc. I’m not going to discuss everthing with you guys on this blog, but some of them are definitelly influencing (the domain of) Sitecore, so they are worth to discuss:

  1. ADO.NET vNext
    The next version of ADO is delayed. The reasons are clear: the product isn’t finalized and even more obvious, the product is influencing products way more as Microsoft might expected. Microsoft is going to work on the product until the end of the year. Some improvements: IDE integration & Jasper.
    There are a lot of discussions about the how and what of this delay, I think that the delay of any new technology is an advantage these days. As the world is changing and growing way to fast.
    And the delay might also provide Ole and Jakob the possibility to take a closer look at it. As it might be extremely interesting to change the Sitecore dataprovder model…
  2. Silverlight
    The old name was ‘WPF/E’, these days called SilverLight. An incredible new technology which is going to change the world of animations. It might not replace Adobe’s Flash(Macromedia is aquired by Adobe a while ago), but it’s at least a good start. Some much things have changed. Take a look at http://silverlight.net/ and the Developer Reference Poster. And if you want to have everything in the right order and context, take a closer look at this Scott Hanselman’s blogpost.
  3. Astoria
    This is the last one to speak about today. As I’ve to clean up my whole feed and I think this amount information is more then enough to drink over 3 cups of coffee with ;-).
    Back to the brand new technology called ‘Astoria‘ – what a brilliant codename – which is a way to request (rellevant) data using the web. The concept is way from new, but it’s never described before as Microsoft these days.

That’s it for now. Have to write down some ideas which came up during my vacation :D.