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


Why Is The First Start Of An Application Slow?

AddThis Social Bookmark Button
Originally posted on: of us have experienced it but very few of us have gone into the details to really find the reasons for it. First of all why should I care? After the first time the application starts much faster. Well you should care if you want to give your customer not only a good second startup time but also a decent first startup experience. To do that you need to do repeated tests. The first startup is commonly referred to cold startup and all subsequent runs are warm startup scenarios. To test a cold startup scenario
you need to reboot your computer every time and start your application. Not very practical and I have no one ever seen going down that road. The difference between warm and cold startup time is that the first time the dlls and data of the application need to be loaded from disc which can take quite some time. All subsequent runs can read the data not from disk but from the in memory file system cache which is managed by the operating system. What Is The File System Cache? Windows uses the memory of your system in...(Read whole news on source site)

Version Control, Git, and your Enterprise

AddThis Social Bookmark Button
Version Control, Git, and your Enterprise

article is about understanding Git – both its benefits and limits
– and deciding if it’s right for your enterprise. It is
intended to highlight some of the key advantages and disadvantages
typically experienced by enterprises and presents the key questions to be
contemplated by your enterprise in determining whether Git is right for you
and what you need to consider in moving to Git.

A Day in the Life of Visual Studio Send a Smile Feedback

AddThis Social Bookmark Button
Last time we talked about the Feedback Tools in Visual Studio 2015 RTM and I shared how you can send us feedback. In this post, I am going to share what happens to the feedback after you send it to us. There are two key goals that we have for the feedback that you share: Look at it as quickly as possible Act on it as quickly as possible The action taken could be any of these listed below (and I will elaborate on these in the post below): Determine the problem and fix Contact you to get more information, if required Communicate a solution
or work around to you Flag it to fix in an upcoming release Determine that it’s not something we will fix, and communicate the reason back to you Or acknowledge that you like the product or a feature (or don’t), but haven’t filed a bug We get a LOT of feedback on Visual Studio. To give you some idea of the volume, we have already received over 10,000 Send a Smile feedback items for VS2015 alone since we released on July 20! To ensure your feedback doesn’t get lost in this volume, we do a lot to get it to the right folks quickly! We...(Read whole news on source site)

Containers: Docker, Windows and Trends | Microsoft Azure Blog

AddThis Social Bookmark Button
Containers: Docker, Windows and Trends | Microsoft Azure Blog

ScottGu's Blog - Announcing Windows Server 2016 Containers Preview

Preview of our Visual Studio Tools for Docker

demonstrated at DockerCon,
we are excited to create a unified and open experience for developers
and system administrators to deploy their containerized applications
comprising both Windows Server and Linux. We are developing this in the
open Docker GitHub repository.

C++/CLI Enumerable::GroupJoin example for MSDN

AddThis Social Bookmark Button
Originally posted on: to the “Missing from MSDN” series of posts: I find tremendous benefit in the Enumerable::GroupJoin method for mimicking the function of a left outer join in SQL --
the construct where the system reports back to you all “keys” and “values” even if the values (results) are null or empty. With the regular Enumerable::Join, only the Key-Value pairs or groupings are returned when there is an associated result.
I had found a nifty way of inverting the join to retrieve non-matching results and it was of use until I discovered

For all of my uses of Enumerable.* in C++/CLI, I always create a helper class to hold methods and the Funcs that will be used as delegates.
This helps prevent clutter and allows for easier reuse. Keeping with the tradition of creating an examples that COULD HAVE BEEN in MSDN, please examine the code below.
I took the liberty of using IEnumerable^ instead of List^ to remove unnecessary code (well, sort of…).
I also chose to not give Magnus Hedland a pet, so the alternate benefit could be shown (a record with no result). #include "stdafx.h" using namespace System;
using namespace System::Collections::Generic;
using namespace...(Read whole news on source site)

Microsoft Hates Enterprise Developers? -Telerik Developer Network

AddThis Social Bookmark Button
Microsoft Hates Enterprise Developers? -Telerik Developer Network

With hundreds of thousands of downloads
per week, tools like Bower, Grunt, Gulp, and Node have become
mainstream. Microsoft chose to not resist the trend but embrace it by
supporting these new tools in Visual Studio. As a result some enterprise
developers will be faced with tough choices. Those choices are to adopt
new processes, learn and bring it safely and securely to their
enterprise, or resist and hold on to what will eventually be legacy

Unsafe operations are required in the real world

AddThis Social Bookmark Button
There is a pretty interesting discussion in the Raft mailing list, about clarifying some aspects of the Raft protocol. This led to some in depth discussion on the difference between algorithms in their raw state and the actual practice that you need in the real world. In case you aren’t aware, Raft is a distributed consensus protocol. It allows a group of machines to reach a decision together (a gross over simplification, but good enough for this). In a recent post, I spoke about dedicated operations bypasses. This discussion surfaced another one. One of the things that make
Raft much simpler to work with is that it explicitly handles topology changes (adding / removing nodes). Since that is part of the same distributed consensus algorithm, it means that it is safe to add or remove a node at runtime. Usually when you build a consensus algorithm, you are very much focused on safety. So you make sure that all your operations are actually safe (otherwise, why bother?). Except that you must, in your design, explicitly allow the administrator to make inherently unsafe operations. Why? Consider the case of a three node cluster, that has been running along...(Read whole news on source site)

The Morning Brew #1932

AddThis Social Bookmark Button
Information The Zen of Code Reviews: Best Practices – Michael Sorens Usage of into and let keyword in Query Expression C# – Ashish Kumar Switchable Actor Behaviour in Akka.NET – Jason Roberts The series Microsoft #Azure Essentials: Free #eBooks – Sergio Govoni Deploying to Linux & Windows Docker Containers, Why doesn’t Docker Tools for Visual […]