Visual studio feeds

All Visual Studio blogs in one place


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


Node.js Tools 1.0 on GitHub and VMs Available

AddThis Social Bookmark Button
With the start of a new season of Game of Thrones, folks are sitting on the edge of their seats waiting to see what’s coming. Unlike the Khaleesi who seems to be going nowhere fast, Node.js Tools for Visual Studio (NTVS) has made some moves recently. Over the last month, we released Node.js Tools 1.0 for Visual Studio, joined the vibrant open source community on GitHub, and created VM images so anyone can quickly get started with NTVS. 1.0 Release What is our goal with NTVS? We want to bring the power of Visual Studio to Node.js so you can
build, debug, and deploy a working application faster than ever before. Say goodbye to console.log(…) with our advanced debugging and profiling experiences—something as simple as allowing breakpoints goes a long way in increasing developer productivity! To learn more about the features in the NTVS 1.0 release, visit Node.js Tools for Visual Studio on If you prefer watching a video, check out this overview of Node.js Tools 1.0 for Visual Studio. Join the GitHub community We’ve listened to you all and have begun transitioning our workflow to GitHub. The most engaged members of the JavaScript and Node.js communities interact...(Read whole news on source site)

A First Look at ReactiveCocoa 3.0

AddThis Social Bookmark Button
This blog post takes a look at the new ReactiveCocoa 3.0 swift interface, which introduces generics, a pipe-forward operator and an interesting use of curried functions. This is the first of a couple of blog posts I intend to write about ReactiveCocoa 3 (RC3). The main focus of this post is the Swift Signal class itself, with the next post building on this to show a more complete application. Introduction I’ve been a big fan of ReactiveCocoa for a long time, having written a number of articles for Ray Wenderlich’s site, and a few conference presentations on the subject. When Swift first
came out it was possible to bridge the Objective-C ReactiveCocoa API to Swift which results in some significant syntactic improvements to ReactiveCocoa. However with features such as generics, a pure Swift implementation or ReactiveCocoa could be so much better! Thankfully the ReactiveCocoa team have been working on a brand new Swift API for many months. Just over a week ago they had their first beta release, which is the subject of this blog post. This post assumes that you are already familiar with ReactiveCocoa, although you certainly don’t have to be an expert! Creating RC3 Signals The easiest way to add ReactiveCocoa...(Read whole news on source site)

Xamarin.Android– Wearable Demo Project is now on Github

AddThis Social Bookmark Button
Originally posted on:’ve decided to put the demo project on github in case someone would want to see and run the demo project I’ve created about syncing data between wearable and handheld device. Here’s the link: If you are new to Android development and would like to explore it using Xamarin and Visual Studio then you can check my previous article about: Getting Started with Android Wearable using Xamarin and Visual Studio. You can also check my other blog posts below: Xamarin.Android and Visual Studio–Build Failed with no

ASP.NET MVC 6 formatters – XML and browser requests

AddThis Social Bookmark Button
A while ago I wrote a post about formatters in MVC 6. Since then, there have been some changes regarding XML handling and an interesting feature that was added recently that was not part of that post, so I think it warranties a follow up. XML formatter is now removed by default. On top of […]The post ASP.NET MVC 6 formatters – XML and browser requests appeared first on StrathWeb.

Work stealing in the presence of startup / shutdown costs

AddThis Social Bookmark Button
I mentioned that we have created our own thread pool implementation in RavenDB to handle our specific needs. A common scenario that ended up quite costly for us was the notion of parallelizing similar work. For example, I have 15,000 documents to index .That means that we need to go over each of the documents and apply the indexing function. That is an embarrassingly parallel task. So that is quite easy. One easy way to do that would be to do something like this:
foreach(var doc in docsToIndex) ThreadPool.QueueUserWorkItem(()=> IndexFunc(new[]{doc}));
Of course, that generates 15,000 entries for the thread pool, but
that is fine. Except that there is an issue here, we need to do stuff to the result of the indexing. Namely, write them to the index. That means that even though we can parallelize the work, we still have non trivial amount of startup & shutdown costs. Just running the code like this would actually be much slower than running it in single threaded mode. So, let us try a slightly better method:
foreach(var partition in docsToIndex.Partition(docsToIndex.Length / Environment.ProcessorCount)) ThreadPool.QueueUserWorkItem(()=> IndexFunc(partition));
If my machine has 8 cores, then this will queue 8 tasks to the thread pool, each indexing just under 2,000 documents....(Read whole news on source site)

The Morning Brew #1847

AddThis Social Bookmark Button
Information DRY out your policies – Eric Lippert Object Oriented, Test Driven Design in C# and Java: A Practical Example Part #5 | – Paul Mooney To improve testing, snoop on the competition – Gojko Adzic TDD Gamification – Dave M Bush All you need to know about Redis & An easy way to use […]

This Post Has No Value

AddThis Social Bookmark Button
I set out to write a post on Incremental Searching in Xamarin applications (which I will do next) but along the way I realized i need a goodly amount of data to search. This is a  problem that arises fairly … Continue reading → For the complete article and hyperlinks, please visit my blog at