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


APress Deal of the Day 17/September/2014 - Expert F# 3.0

AddThis Social Bookmark Button
Originally posted on:’s Deal of the Day from APress at 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 unrivalled levels of programmer productivity, application performance and program clarity.”

Using Friendly URLs in Web Forms

AddThis Social Bookmark Button
Friendly URls help you eliminate query string parameters and file extensions from the URL line. So, instead of…
You use simple friendly URLs instead as shown below:
There are many benefits of using friendly URLs in your web applications. ·         Cleaner query string ·         User does not know the actual page name ·         Easier for users to use Friendly URLs are available in Web Forms and MVC. I see a lot of examples of using friendly URLs using MVC, but very few using Web Forms. So, I thought I would discuss how to use them in Web Forms. Actually, the process is almost
identical. First you need to download the Microsoft.Asp.Net.FriendlyUrls.Core.dll if you don’t already have it in your project. If you have an older ASP.NET application you probably don’t have it. If you are starting a new project in Visual Studio 2013, and choose the Web Forms template, this DLL is already present. If you want to use friendly URLs in an older project, select Tools | Nuget Package Manager | Manage NuGet Packages for Solution... from the Visual Studio menu. Search online for Microsoft.AspNet.FriendlyUrls and install the Microsoft.AspNet.FriendlyUrls.Core. You don’t need any of the other DLLs in the NuGet packages list, just the...(Read whole news on source site)

How To Think Like a Microsoft Executive

AddThis Social Bookmark Button
One of the things I do, as a patterns and practices kind of guy, is research and share success patterns.  One of my more interesting bodies of work is my set of patterns and practices for successful executive thinking. A while back, I interviewed several Microsoft executives to get their take on how to think like an effective executive. While the styles vary, what I enjoyed is the different mindset that each executive uses as they approach the challenge of how to change the world in a meaningful way. 5 Key Questions to Share Proven
Practices for Executive Thinking My approach was pretty simple.   I tried to think of a simple way to capture and distill the essence. I originally went the path of identifying key thinking scenarios (changing perspective, creating ideas, evaluating ideas, making decisions, making meaning, prioritizing ideas, and solving problems) ... and the path of identifying key thinking techniques (blue ocean/strategic profile, PMI, Six Thinking Hats, PQ/PA, BusinessThink, Five Whys, ... etc.) -- but I think just a simple set of 5 key questions was more effective. These are the five questions I ended up using: ...(Read whole news on source site)

Cuttable Scope

AddThis Social Bookmark Button
Early on in my Program Management career, I ran into challenges around cutting scope. The schedule said the project was done by next week, but scope said the project would be done a few months from now. On the Microsoft patterns & practices team, we optimized around “fix time, flex scope.”   This ensured we were on time, on budget.  This helped constrain risk.  Plus, as soon as you start chasing scope, you become a victim of scope creep, and create a runaway train.  It’s better to get smart people shipping on a cadence, and focus on creating incremental
value.  If the trains leave the station on time, then if you miss a train, you know you can count on the next train.  Plus, this builds a reputation for shipping and execution excellence. And so I would have to cut scope, and feel the pains of impact ripple across multiple dependencies. Without a simple chunking mechanism, it was a game of trying to cut features and trying to figure out which requirements could be completed and still be useful within a given time frame. This is where User Stories and System Stories helped.   Stories...(Read whole news on source site)