Being able to handle replication at the storage level is a really nice feature to have. More than that, it is a feature that can be broadly applied. But… a database is a lot more than just storage. And being able to just move the data around between machines is nice, but there are other things we have to take into account. In particular, when we replicate via storage changes, we don’t have a good way to take actions on changes. Most of the time, that means that we can’t actually rely on internal caches, and would probably
have to deal with that somehow in another fashion. But there are usually secondary processing that is done on a node that would have to be accounted for. For example, let us assume that we had the ability to replicate RavenDB (docs) changes between machines using storage replication. The problem here is that we would be replicating the documents, but not the indexes, and when we do that, we would need to index the changed documents on the destination node. However, that would actually require two data stores, one for the actual documents data, and one for all of the...(Read whole news on source site)
Software New Office REST APIs and Developer Tools for Visual Studio Update &Announcing Office Developer Tools for Visual Studio 2013 â€“ March 2014 Update - Somasegar and Keith Yedlin announce the release of the March 2014 update of the Office Developer Toosl for Visual Studio 2013 Information Living with unchecked exceptions - Eric Lippert takes [...]
Originally posted on: http://geekswithblogs.net/TATWORTH/archive/2014/03/04/apress-deal-of-the-day-for-4mar2014---expert-f.aspx Today's $10 deal of the day from APress at http://www.apress.com/9781430246503 is Expert F# 3.0 "Expert F# 3.0 is about practical programming in a beautiful language that puts the power and elegance of data-rich functional programming into the hands of professional developers and analytical programmers. Through simplicity and interoperability, F# achieves unrivaled levels of programmer productivity, application performance and program clarity. "
Retrofitting software architecture Structure101 Studio, combining the award-winning Structure101 and Restructure101 products, is now generally available. Structure101 Studio makes it feasible to discover, define, communicate, and enforce an architecture for an existing codebase, without major upfront surgery. Structure101 achieves this by letting the software architect construct an external model of the architecture while simultaneously mapping the... Read more »
While naked ALM Consulting can help you install and configure TFS you may want to take advantage of the upcoming TFS Upgrade Weekend from Microsoft for free.The post Team Foundation server 2013 Update 2 RC is coming, are you ready? appeared first on naked ALM - Experts in ALM, TFS & lean-agile with Scrum.
Originally posted on: http://geekswithblogs.net/bjackett/archive/2014/03/04/powershell-script-to-limit-sharepoint-2010-or-2013-site-templates.aspx I had a customer request recently to limit the which site templates were available to end users to create subsites. Below is a short PowerShell script to do just that. Problem If you are using a Publishing Site you can restrict the available site templates by going to Site Settings –> Look & Feel and clicking on Page Layouts and Site Templates (see following screenshot). If you are not on a Publishing Site then there is not an easy (supported) way to accomplish this through out of the box means.
Solution The SPWeb class has methods GetAvailableWebTemplates and SetAvailableWebTemplates that can be used in conjunction with each other to get the current list of templates and then filter down to only the desired templates. The filtered down results can then be set and updated on the SPWeb. A version of this script can be downloaded from the TechNet Script Repository: Limit available web templates for a SharePoint site. Note: Be sure to modify the “