All Visual Studio blogs in one place

AddThis Social Bookmark Button
You probably didn’t notice that we did our sprint 63 deployment last week.  I didn’t blog about it because there wasn’t much to say.  We announced a whole bunch of new stuff at Build the week before and there wasn’t much new in sprint 63 beyond consolidating on the Build feature set and preparing for our next event – TechEd in early May.  I suspect next sprint’s deployment will also be light as it’s the last deployment before TechEd and most of the work will be preparing for those announcements.  I hope to see you at TechEd and, if not,
I’ll see you online. Brian
...(Read whole news on source site)

AddThis Social Bookmark Button
No. This is an example of the power of social media.  I had planned to ignore it but I’ve had enough requests for “official confirmation” that I guess I have to say something :). Last week someone tweeted “Microsoft phasing out the TFS version control repository and moving to Git. Unofficially confirmed at a TFS presentation” It caught on and created a minor retweet storm. It’s simply not accurate.  I’ve been told it was the result of a misunderstanding generated in a hallway conversation between one of our MVPs and a customer at a presentation on
TFS.  Misunderstandings happen – it doesn’t worry me.  Social media just allows them to go global quickly :) As I said when I announced Git support in VS/TFS, our intent is to provide the best centralized version control system and the best distributed version control system.  We fully intend to support both, enhance both, etc indefinitely.  Both types of version control are useful to different teams and both benefit from the tight integration and enterprise class hosting that we can provide inside TFS and Visual Studio.  At the moment, a significant majority of our customers use TFVC.  That...(Read whole news on source site)

AddThis Social Bookmark Button
I’ve been using Lucene for the past six or seven years, and after my last post, I thought it would be a good idea to talk a bit about the kind of things that it isn’t doing well. We’ve been using it extensively in RavenDB for the past 5 years, and I think that I have a pretty good understanding of it. We used to have one of Lucene.NET committers working at Hibernating Rhinos, so I’ve a high level of confidence that I’m not just stupidly not using it properly, too. Probably the part that caused us the most pain
with Lucene was the fact that it isn’t transactional. That is, it is quite easy to get into situations where the indexes are corrupted. That make it… challenging to use it in a database that needs to ensure consistency. The problem is that it is really not a use case that Lucene is well suited for. In order to ensure that data is saved, we have to commit often, the problem is that in order to ensure good performance, we want to commit less often, but then we will the changes if we crash. For that matter, Lucene doesn’t do...(Read whole news on source site)



Enter your email address:

Delivered by FeedBurner

Increase your website traffic with


Anti-spam: How many eyes has a typical person?

Follow us on FB