Ever worked with a source control system where you have single user lock on files? This interferes to much with work. You rarely want a locking mechanism in place (that would degrade the ability to work together). I have a nagging feeling that files and folders should not be locked by a single process/applikation. It interferes with many of the things I do. Just look at onenote. Instead of the easy way (locking), the program merges the changes. It's often easier to deal with the edge cases when they arise[...]

Whats wrong with Commerce Server 2009 from a developer perspective? Configuration: There is no single source of object mapping configuration. Multiple places to insert properties. FaultException does not include the original exception. The CS2009 api's look very dynamic... It promises a lot more than it can deliver since it is based upon CS2007 API and thus quite limited. No transactions for some of the entities. For instance profiles and catalog.  Integration with SharePoint by putting the configuration[...]

Whats wrong with Commerce Server 2009 from a developer perspective? Configuration: There is no single source of object mapping configuration. Multiple places to insert properties. FaultException does not include the original exception. The CS2009 api’s look very dynamic… It promises a lot more than it can deliver since it is based upon CS2007 API and thus quite limited. No transactions for some of the entities. For instance profiles and catalog.  Integration with SharePoint by putting the confi[...]

Easy way of making something simple hard.

Thanks to r# we do not need to add interfaces for internally accessible code unless there is a need for it. Of course this is not the same if the interface is an implementation (or part of) of an externally visible api.