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


10 Personal Productivity Tools from Agile Results

AddThis Social Bookmark Button
“Great acts are made up of small deeds.“ -- Lao Tzu The best productivity tools are the ones you actually use and get results. I'll share some quick personal productivity tools from Agile Results, introduced in the book, Getting Results the Agile Way. Agile Results is a Personal Results System for work and life, and it's all about how to use your best energy for your best results. With that in mind, here are some quick productivity tools you can use to think better, feel better, and do better, while getting results better, faster, and easier
with more fun ... PRODUCTIVITY TOOL #1 - THE RULE OF THREE Think in terms of Three Wins each day, each week, each month, each year. You can apply the Rule of 3 to life. Rather than get overwhelmed by your tasks, choose three things you want to accomplish today. This puts you in control. If nothing else, it gives you a very simple way to focus for the day. This will help you get on track and practice the art of ruthless prioritization. Consider the energy you have, what's the most important, what's the most...(Read whole news on source site)

HubShots – Aussie HubSpot Podcast

AddThis Social Bookmark Button
Lately I’ve been working on a new project with my friend Ian Jacob. Together we co-host a new HubSpot focussed podcast called HubShots. There’s 6 episodes available so far (and two more recorded and currently being edited). If you’re interested in inbound marketing, content marketing and HubSpot, then I think you’ll really like the podcast.... Continue reading → The post HubShots – Aussie HubSpot Podcast appeared first on Craig Bailey.

Back to Basic : Displaying detailed output of MSBuild in Visual Studio output Window

AddThis Social Bookmark Button
I have received this question as a follow-up from one of my pervious post Back to Basic – Building Solutions in Visual Studio – Build Vs. Rebuild . There I explained the details of different types of build and how things works under the hood, and shows how you can view the detail inside output window.  Question [...]

The Morning Brew #1977

AddThis Social Bookmark Button
Happy Thanksgiving to my US based readers. Information The road to DNX – part 2 & The road to DNX – part 3 – Marc Gravell continues his series of posts looking at migrating to the .Net Corel, exploring the porting of an existing library to the framework, and looking running the .NET Framework under […]

C# 6.0 String Interpolation, FormattableString, and Code Analysis CA1305: Specify IFormatProvider

AddThis Social Bookmark Button
C# 6.0 introduces a syntactic sugar string interpolation, it is safer and more readable than composite formatting. Here is a small example:using System; using System.Diagnostics; internal static class Program { private static void Main() => Trace.WriteLine($"Machine name: {Environment.MachineName}."); } However, string interpolation does not get along with code analysis. By default, the $ syntax will be compiled to composite formatting, by calling the string.Format overload without IFormatProvider parameter:using System; using System.Diagnostics; internal static class Program { private static void Main() => Trace.WriteLine(string.Format("Machine name: {0}.", Environment.MachineName)); } As a result, Code Analysis/FxCop issues a CA1305 warning for every interpolated string:
Specify IFormatProvider. This is very annoying. Interpolated string has a infamous feature, it can be also compiled to System.FormattableString:namespace System { using System.Globalization; public abstract class FormattableString : IFormattable { protected FormattableString() { } public abstract string Format { get; } public abstract int ArgumentCount { get; } public abstract object[] GetArguments(); public abstract object GetArgument(int index); ...(Read whole news on source site)

Information Exchange With Transformations

AddThis Social Bookmark Button
In the industry that I work in, Public Safety, there is a standard called NIEM, which stands for National Information Exchange Model ( It is an XML-based standard for sharing information between law enforcement agencies, first responders and other organizations. The various exchange scenarios are documented/described as XML schemas (.xsd’s), which are very complex schemas. I have been using simple Typed DataSets since the early days of .NET (1.0 was buggy, 1.1 was much better). They are easy to fill from a database and easy to pass around between the layers/tiers of any application that I have
written. However, to pass data from a law enforcement application to a fire department application, for example, there needs to be a common schema between them. Clearly, the simple Typed DataSet I use for a Police application will look totally different than the Typed DataSet I use for a Fire application. The way to solve this dilemma is to transmit the data with a common schema … NIEM to the rescue! Transformations are used to Transform the Police DataSet to the common NIEM schema, then transmit the data as XML in the NIEM format to the Fire application, which...(Read whole news on source site)