Resharper 8.0.1 RTM, Windows 8.1 RTM and Visual Studio 2013 RC

There are some recent releases (at the time of writing) that I think many of you will be interested in.



Resharper 8.0.1

This is a bug fix update for Resharper 8. It supports pre-release Visual Studio 2013 better and also Visual Studio 2012 as usual.

Summary of fix areas:

  • Unit test runner (freezes, crashes, incorrect test status, conflicts with NUnit Test Adapter etc.)
  • Export of settings
  • Code analysis (second check expression in a double-check lock reported as always true)
  • UI (License Information dialog box, VS2008 and VS2012 integration cosmetics)
  • Internationalization (Move HTML to Resource not working)
  • Code completion (double completion lists, broken IntelliSense in projects targeting Windows 8.1)
  • Performance (mostly with unit test runner and CSS)

For the entire list of fixes, please see ReSharper 8.0.1 release notes.

Learn more at:



Windows 8.1 RTM (And Windows Server 2012 RTM)

Windows 8.1 RTM was meant to be held until the retail version in October, but Microsoft changed their mind and made it available for MSDN & TechNet subscribers to allow developers to test their applications on the RTN version (which has several API changes from the preview). If you have an MSDN subscription, go ahead and check your subscriber downloads.

The versions available as of now are Windows 8.1, Windows 8.1 Pro, and Windows 8.1 N. Windows 8.1 Enterprise might be available in a week or two.

Note that many Microsoft partners, you should only use MSDN downloads for VMs not real machines, and should use the Microsoft Partner Network for the real machine installs. Unfortunately the Partner Network will et Windows 8.1 by October with everyone else.

Note that Windows Server 2012 RTM is also available with the same terms, which makes its availability as a hosting OS still practically on hold for many people, btu it’ll be useful for creating test labs, etc. inside environments that consider deploying it.

You can learn more about Windows Server 2012 RTM from:



Visual Studio 2013 RC (Release Candidate)

To help with application testing in Windows 8.1 without wrapping up Visual Studio 2013 RTM too early, Microsoft has released Visual Studio 2013 RC at the same time, with a go-live license (meaning you can use it for production applications). You don’t need a special MSDN subscription to use the RC, but if you plan to develop Windows Store applications, then you really need to install it on Windows 8.1.

There are many new features in Visual Studio 2013, several were available since the previous Preview, but also many have arrived with the RC, here’s a video and complete listing of what’s new in Visual Studio 2013 Release Candidate:

Before downloading, you may want to check out the compatibility information from:

Then you can download Visual Studio 2013 RC from:

On _references.js files in VS2012 – VS2015, or the state of JavaScript Intellisense in Visual Studio

If you downloaded Visual Studio 11 Beta, and tried to create a new ASP.NET MVC 4 empty project, looking at the “Scripts” folder, you’ll see this new file “_references.js”:


Which looks like the following:

/// <reference path="jquery-1.6.2.js" />
/// <reference path="jquery-ui-1.8.11.js" />
/// <reference path="jquery.validate.js" />
/// <reference path="knockout-2.0.0.debug.js" />
/// <reference path="modernizr-2.0.6-development-only.js" />

The VS <reference /> Syntax

As you probably know, the // &lt;reference path=”…” /&gt; syntax was introduced in Visual Studio long time ago to make you able to have intellisense in any JavaScript file to include everything defined in the JavaScript located at this path.

In easier words, if you write the very first line in any JavaScript file, say “my-page.js”, and make sure the path points to the proper jQuery file, when you write code in “my-page.js”, you’ll get intellisense for everything in the jQuery file. The quality of the intellisense will vary based on the referenced jQuery file, whether it’s minified file (least intellisense info, only member names, sometimes), just standard source/debug file, or even one that VsDoc comments (best intellisense, might even have notes on what types you need to pass to methods, when defined in VsDoc comments).

The Resharper Way

If you are using Resharper 6 or so, Resharper will give you intellisense from all files in the project. Generally speaking this is a good thing, but it has two drawbacks:

  • If you have so many JavaScript files in the project (for example, number of common files plus a file or two for every page in a big project), the JavaScript editor experience can be bit slow in times, as Resharper tries to evaluate all the JS files to get you intellisense
  • When you type the first letters of a member, the intellisense menu will bring so many results, because it will include all possible members from all files in the project, even the ones completely unrelated to what you are doing now. The way Resharper tries to make this less severe, is that it tells you which file it picked every intelisense item from.

The Visual Studio 2012 Way: Or The _references.js File

In VS 11, Visutal Studio will give you intellisense from all files that have references in the “_references.js” file. This way you can define the global / common files you use all the time. This might include some library files like jQuery, or some files you use everywhere in the project like some internal utilities files.

For related files, you can use the “<reference >” syntax on top of every file to connect them (from intellisense point of view).

File Location

Note that there is only one _references.js file for each project. It doesn’t work like web.config where you have have web.config files in site folders affecting only those folders.  An _references.js file in any other location than “~/Scripts/_references.js” will be just like any other JS file and won’t be used for global intellisense. Even putting the file in the root of your web project will not work as well.

Update (March 21, 2012)

After reading Scott Hanselman’s post on hidden web features in Visual Studio 11 beta (posted yesterday), turns out you can add files to the global JavaScript intellisense from the Visual Studio Tools –> Options Dialog:


In the options windows, go to Text Editor –> JavaScript –> Intellisense –> References node in the tree view at the left, then from the dialog that comes, choose “Implicit (Web)” for “Reference Group”. You can see that the _references.js file itself is just an entry in the list, and you can add other entries below.

You can pick specific files, or use the “~/path-to-file” to use a path relative to the root of your web project.


Resharper Support For VS11 – Download Link & Installation Hints

In case you haven’t noticed the update of my previous post about VS 11, Resharper 6.1 nightly build supporting VS 11 has been out already.



Notes On Installing Resharper 6.1 Nightly Build For VS11

  • The file you download is not an EXE, but it is still an installer. All You need to do is run the file and press "Install"
  • You can use the license key mentioned in the download page, but, you may try your existing Resharper 6.0 key as well and see if it works.
  • Likely the Resharper keyboard shortcuts won’t work directly. You need to enable them yourself. More on that below…
  • UPDATE: If you install a nightly build, then a new build comes out and you try to install it, you get "This extension is already installed to all applicable products.". More on that below…


To enable the Resharper keyboard shortcuts:

In Visual Studio 11, go to Resharper Options menu:


In the left side, choose "Visual Studio Integration"


Under "Keyboard Shortcuts", press "Apply Scheme"


Some quick dialog will show with "Cancel" button (don’t press it!). Wait until it disappear, and you are done. Click OK to close the Options dialog, and start enjoying the Resharper shortcuts!



To Solve: "This extension is already installed to all applicable products." Error

If you try to install the Resharper VSIX installer file for VS11 when you have an earlier Resharper VS11 build, you may get an error that looks like:


Visual Studio thinks the two builds are the same. The likely cause is that Resharper is using the same version number in the installer.


This can be easily fixed by opening VS 11, going to Tools -> Extension Manager, finding the Resharper extension (yes, in VS11 it’ll be there, in  earlier VS version, it won’t), click the Resharper extension in there then click "Uninstall", accept the confirmation, and close VS11 afterwards.


The installer should then work normally.

Quick Hints: Solving VS 2010 Beta1 only showing Splash Screen; AnkhSVN works; R# in June

Check the add-ins you installed before Visual Studio 2010 if you enabled VS 2010 integration in them. Particularly TestDriven.NET is the problem. Go to “Add Remove Programs” / “Programs and Features”, find Test Driven.NET, click “Change”, and then modify it to remove VS2010 integration from it.


Also, if you are using AnkhSVN, make sure to download a new latest daily update build and use that, otherwise, you’ll get an exception when starting VS 2010.


I’ll be writing more about VSTS 2010 and .NET 4.0 in the next coming months (if God will), since now I can run it :D (before, I did not have the fix that extends the Virtual Machine expiration after January 1st, 2009).


BTW, for R# deep lovers (like me), Resharper for VS 2010 is expected next month.


Have fun, please!


Resharper 4 BETA Released

Avoid Much Talk

I wrote about Resharper 4 performance improvements in an earlier blog post today showing my VS Color Scheme including use of R# nightly builds. My friend Mohamed Tayseer pointed me out that Resharper 4 BETA was released yesterday. If you already know Resharper, skip the blah blah blah talk and get to the download.

Resharper, AKA R#, Who ???

Resharper used to be a must-have add-in for Visual Studio. It completes the features existing in Visual Studio like intellisense (not just smarter intellisense, but also available everywhere, like those areas in ASP.NET markup when you start typing non-standard code to Visual Studio to hook some properties and you get lost alone usually).

Of course it makes the expected enhancements to standard VS editor like parentheses and semicolon completion and other similar features, although it takes you w while to get used to stopping writing those after R# writes them for you!

It also has interesting stuff like SPEED find options (instead of this “Compiling the Solution” messages whenever you want to “Find Reference”) also extended for things like 2-way jump between the base classes / interfaces and their children classes/methods. ad also tons of “Guideline promoting” features like intellisense for  VARIABLE names (like when you type “MailMessage” for local variable type, it recommends names like “mailMessage”, “message”, etc…), and options to detect unused variables and “using” namespace directives, and many other features.

It also offers very handy icons that do interesting stuff like inverting “if” statements and reversing assignments (very handy in ASP.NET donkey code behind files, in an edit page, call on page load a method with all txtProductName.Text = currentProduct.ProductName;, copy that to the method that’s called from the “Save” button click, select it and click “Reverse Assignment”), and many great other features appearing as very small icons to the left of the code to not interrupt your work.

It’s also smart. It can realize that Console.WriteLine(“{0}, {1}”, object0); will fail because the string format method is a “string formatter method” and it expects two objects while I passed only one! It has tons of interesting warnings and recommendations like this. Leave apart small features like quick use of “var” instead of type and suggesting and quickly applying conversion of normal static method to extension method, and so many other features.

For more advanced users than me it has advanced code snippets style and advanced template engine and advanced plug-in model for extending all features it offers (some interesting plug-ins), but I never used those … too advanced for my “code monkey” use of VS :D. It even has integration with Testing frameworks, although TestDriven.NET already also handles this for me.

Resharper – Major Turnoff Removed

Earlier, the worst thing that prevented me totally from recommending it to friends (besides the price, I believe it is expensive [$199 for personal use, $149 if skipping VB.NET support], especially when you convert US dollar$ to Egyptian pounds :D) was the performance issue. With a 15+ VS solution each of over 15 classes (not small ones), you get slow down at project opening and many times at typing (while it’s trying to get the smart intellisense or other great features to me).

This also cost A LOT of memory. I had a friend who installed it only in code review sessions and uninstalled it just after the code review because how greedy it is in terms of RAM. Things got a little better from R# 2 to 3, but also my work got bigger at the same time, so, it felt tedious.

Now with Resharper 4 (still in BETA) this is no longer an issue. I totally do not notice a difference in Visual Studio whether Resharper is there or not. This makes it great to develop and complete the parts that are missing and are actually must-have features Microsoft is missing in Visual Studio. It’s a really elegant piece of work.

I’d still worry about pricing, especially vs. FREE Visual Studio (you get via your company’s MSDN subscription usually, so, it “feels” free to you), but this is another story.

Reshaper 4 BETA News / Download

In my last post, I put a note about R# 4 nightly builds performance that more than anybody targeted mainly Mohamed Tayseer, my colleague who used R# only in some code review sessions and uninstalled it just after. A few hours later he returned the favor by pointing me out that R# 4 BETA was announced yesterday.

BTW, if you haven’t guessed already, R# 4 BETA is a FREE evaluation version.

Here are the related resources:

Dark Visual Studio W/ Resharper – My VS Settings (Colors, Windows Layout, …) – V2


I blogged my old Visual Studio settings before for Visual Studio 2005, using a dark color theme and optimizing it for Resharper features like Resharper colorings and “Current Line Highlight”.

Today I’m sharing with you my settings for VS 2008. Things have changed a bit since the first time, so, you’ll find the layout different and colors as well, although still dark as well.

The one thing to notice is using “Lucida Console” font instead of the popular “Consolas”. Also, if things look a bit small to you, this is because I’m using “Lucida Console” with size 9, and my entire Windows OS layout is using “Arial Unicode MS” font with size “7”. It’s killing for someone with sight shortage, but you never get enough of a 15 inch laptop screen, even if wide one!

By the way, the version of Resharper used with VS 2008 is the latest of the nightly builds of Resharper 4. The best thing I like about it besides supporting C# 3.0 of course is the performance improvements. Now “Solution Wide Analysis” is off by default and I still get most of the features I need of Resharper. Maybe This is the reason for the massive performance increase or whatever the reason, it’s just nice.

<code><p> <br /><b></b>

You can download my settings right here:

File iconVS_Dark_Colors-W-Resharper-20080522.vssettings


By the way, if you are interested in how my old VS settings looked like, check this: