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


X things every JavaScript developer should know: Comparisons

AddThis Social Bookmark Button
Another item of things every JavaScript developer should know is how comparisons work. Just like with some of the other JavaScript, or I should really say ECMAScript, features anything you know about C# or Java could actually be misleading here.   To == or to === One of the weird things is there are actually two comparison operators in JavaScript, the double and the triple equals. The == is called the equals operator, see section 11.9.1 of the ECMAScript standard, and was the original equality operator. Unfortunately the way this operator works is quite some cause
for confusion and as a result the === or Strict Equals operator was introduced, see section 11.9.4 of the ECMAScript standard. It would have been nice if they had just fixed the original problem but if they had they would have broken existing JavaScript applications. In general I would always advise you to use the Strict Equals Operator or === whenever you do a comparison unless you have a specific need for the behavior or the original operator.   What is the problem with == I mentioned that == has problems and should be avoided...(Read whole news on source site)

#1,114 – Culture Codes

AddThis Social Bookmark Button
In developing applications for Windows, a culture can be thought of as the combination of a particular language and the country or region where the language is being spoken. Examples of specific cultures, representing a language and a region, include: English / United States English / United Kingdom French / Belgium French / France German / Germany […]

Welcome to Worldwide Partner Conference 2014 Day 2! Some things to know…

AddThis Social Bookmark Button
Welcome to Day 2 of Worldwide Partner Conference 2014 in Washington, D.C.! For those of you that joined us yesterday, the conference got started off with a lot of excitement, energy, and great information in our series of keynotes, followed by a full day of sessions and meetings. If you are not here with us at WPC 2014, remember that you can participate and follow along virtually in many ways, and here’s how to stay connected, participate in, and follow all of the amazing Worldwide Partner Conference information! Also, don’t forget that I’m looking forward to
the 2014 Fantastic People of Worldwide Partner Conference, so be sure to come up and say, “Hi,” while you’re here and let’s grab a picture together for this year’s collection. Here are a few things that you should know for today: BREAKFAST: There are no Vision Keynotes today, so remember that breakfast is at the CONVENTION CENTER on the Lower Level, not at the Verizon Center like it was yesterday. We are serving breakfast from 7:30 – 9:30 am today. REGISTRATION: Don't have your badge...(Read whole news on source site)

Message passing, performance–take 2

AddThis Social Bookmark Button
In my previous post, I did some rough “benchmarks” to see how message passing options behave. I got some great comments, and I thought I’ll expand on that. The baseline for this was a blocking queue, and we managed to process using that we managed to get: 145,271,000 msgs in 00:00:10.4597977 for 13,888,510 ops/sec And the async BufferBlock, using which we got: 43,268,149 msgs in 00:00:10 for 4,326,815 ops/sec. Using LMAX Disruptor we got a disappointing: 29,791,996 msgs in 00:00:10.0003334 for 2,979,100 ops/sec However, it was pointed out that I can significantly improve this if I
changed the code to be:
var disruptor = new Disruptor.Dsl.Disruptor(() => new Holder(), new SingleThreadedClaimStrategy(256), new YieldingWaitStrategy(), TaskScheduler.Default);

After which we get a very nice:
141,501,999 msgs in 00:00:10.0000051 for 14,150,193 ops/sec
Another request I got was for testing this with a concurrent queue, which is actually what it is meant to do. The code is actually the same as the blocking queue, we...(Read whole news on source site)

O’Reilly Half-Price E-Book of the Day Offer for 15/July/2014 - SignalR Real-time Application Cookbook

AddThis Social Bookmark Button
Originally posted on:’s half-price offer from O’Reilly at is SignalR Real-time Application Cookbook. “SignalR is a recent addition to ASP.NET, which allows you to add real-time functionalities to your applications. SignalR enables bidirectional communication between client and server over HTTP, transparently, and ensures you're always provided with the experience of a persistent connection.”

West Wind WebSurge - an easy way to Load Test Web Applications

AddThis Social Bookmark Button
A few months ago on a project the subject of load testing came up. We were having some serious issues with a Web application that would start spewing SQL lock errors under somewhat heavy load. These sort of errors can be tough to catch, precisely because they only occur under load and not during typical development testing. To replicate this error more reliably we needed to put a load on the application and run it for a while before these SQL errors would flare up. It’s been a while since I’d looked at load testing tools, so I spent
a bit of time looking at different tools and frankly didn’t really find anything that was a good fit. A lot of tools were either a pain to use, didn’t have the basic features I needed, or extravagantly expensive. In  the end I got frustrated enough to build an initially small custom load test solution that then morphed into a more generic library, then gained a console front end and eventually turned into a full blown Web load testing tool that is now called West Wind WebSurge. I got seriously frustrated looking for tools every time I...(Read whole news on source site)