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


Fine grained work control

AddThis Social Bookmark Button
With RavenDB 3.5, we are focusing on performance as one of the key features. I’ve already spoken at length about the kind of changes that we had made to improve performance. A few percentage points here and there end up being quite significant when you add them all together. But just sanding over the rough edges isn’t quite enough for us. We want to have a major impact, not just an avalanche of small improvements. In order to handle that, we needed to be much more aware of how we are making use of resources in the system. The result
of several months of work is now ready to enter into performance testing, and I’m quite excited about it. But before I show you the results, what is it? Well, RavenDB does quite a lot in the background, to avoid holding up a request thread when you are calling RavenDB. This mean that we have a lot of background work, indexing, map/reduce, etc. We have been using the default .NET thread pool for a long time to do that, and it has served us very well. But it is a generic construct, without awareness of the unique needs that RavenDB...(Read whole news on source site)

Microsoft Tuesday - Interesting Links - #09

AddThis Social Bookmark Button
It’s time for Microsoft Tuesday – the post with some interesting links for you to read and start the day with latest happening in Microsoft platform. Above the fold, you will find links on Azure, Skype for business and Windows 10 in today’s post. Keep reading and share your feedback. Did you try Windows 10 on your desktop, tablet or phone? What do you feel? Do share us your feedback on the same.   Announcing Azure Service Fabric: Reducing Complexity in a Hyper-scale WorldCloud computing continues to change the way that businesses reach their customers. In today’s hyper-competitive
environment, ISVs and startups are on the leading edge of this change. They are constantly challenged to find better ways to build scalable cloud services in order to get to market quickly. For developers, growing their businesses while designing for reliability and scale are equally challenging. Last month we released Azure App Service, a high productivity solution for developers who need to create enterprise-grade web and mobile app experiences. App Service provides a complete platform as a service solution that enables you to deploy and elastically scale applications in the cloud, and seamlessly integrate them with on-premises resources and SaaS...(Read whole news on source site)

Managing your Azure infrastructure as code - part 1 (VM configuration)

AddThis Social Bookmark Button
Azure PowerShell is a powerful scripting environment that you can use to control and automate the deployment and management of your workloads in Azure. Using Azure PowerShell cmdlet architects and developers can automate every manual and repeated tasks on the Azure infrastructure. Nearly everything you can do manually in the Azure management portal can be done using Azure PowerShell in the Microsoft Azure Automation service. In this blog, we'll see how you can leverage the power of Azure PowerShell cmdlets to create Azure virtual machines with the platform images. To start with, the first step is to create a Azure
virtual machine configuration object. The configuration object can be created using the New-AzureVMConfig cmdlets.

This object can then be used to perform a new deployment, as well as to add a new virtual machine to an existing deployment. To create a new virtual machine configuration, we’ll need a name for the virtual machine. We'll start the configuration object by specifying some initial characteristics. Later we'll modify the configuration object with the supporting cmdlets to create a VM. To start with, we'll need a valid name for the VM, the size for the virtual machine and the name of the...(Read whole news on source site)

Using RequireJS with Visual Studio

AddThis Social Bookmark Button
As applications become richer and more complex, it becomes important to structure code so that it’s easy to refactor components independently. To understand how one piece of code depends upon another, developers turn to the best practices of modularity and encapsulation to structure code as a collection of small, reusable parts. RequireJS is a popular script loading library that makes it easy to make your JavaScript modular, dividing it into these reusable parts. Visual Studio provides great JavaScript editor support for RequireJS, with IntelliSense that can discover the modules of your application and provide accurate suggestions. If you use TypeScript,
there’s built-in support for modules to compile into JavaScript that works with RequireJS. This post walks you through using RequireJS in Visual Studio with either JavaScript or TypeScript. To use the RequireJS support in Visual Studio, install Visual Studio 2013 Update 4 or later, or Visual Studio 2015 CTP 6 or later. To follow along, you can also download the source code for the sample app. Configuring your project Start by adding RequireJS to your project with the NuGet package manager. You can right click on the project to show the NuGet package manager, search for RequireJS, and install it.

The Morning Brew #1843

AddThis Social Bookmark Button
Information Saga Implementation Patterns: Singleton – Jimmy Bogard takes a look at using the Singleton patttern to implement jobs which provide the work for Saga processes with NServiceBus What is REST API? – Shawn Wildermuth discusses the need to move to more RESTful APIs as we move our applications to the public internet, and how […]

Prioritizing projects and tasks with minimum loss of time and money

AddThis Social Bookmark Button
Last week, I was so fortunate to attend a marvelous talk by Donald Reinertsen on a amazingly effective approach for prioritizing projects within an agile organization (and which is part of SAFe). Most managers will tend to prioritize their projects based on non-quantifiable attributes such as the strategic importance of a project or the risk of loosing a contract. But if you have a multitude of those projects, all equally important, how do you make a decision on what project should be done first? In his opinion, prioritization should happen on a principle named Weighted Shortest Job First.
In this principle two figures are of upmost important: The duration of the project The cost of delaying that project By dividing the former by the latter, you get the weighted value on which you prioritize. Consider for example three projects, A, B and C, all with the same cost of delay but with varying lengths. If you would put them on a graph like the picture below shows, it becomes pretty obvious which project should be done first. So although my first instinct would be to try to get that...(Read whole news on source site)

Parsing command line arguments with F#

AddThis Social Bookmark Button
Last year, I set out to write my first node.js application; a small web application for keeping lists of everything I consume. I had something working pretty quickly, deployed it to Heroku and still find myself using it today. Since there's very little use for having it running on a server, and because I wanted something to toy with getting better at F#, I decided to port it to an F# console application.

With the UI
gone, I need to resort to passing in arguments from the command line to have my program transform those into valid commands and queries that can be executed.

The set of commands and queries is limited; consume an item, remove an item and query a list of everything consumed.

Ideally I go from a sequence of strings to a typed command or query. However, when the list of arguments can't be parsed, I expect a result telling me what failed just the same.

Since we need the name to identify the command or query, I expect the input to...(Read whole news on source site)