Strange ... we haven't seen that before. I think it might be due to the Project Properties window being visible and the Rake window being undocked.
Try docking the Rake panel to the bottom set of tool windows. That should stop it popping up every time VS thinks there a context switch.
You're a bit out of date on the releases. 2.1 is our 'official' release. There aren't very many bug fixes between 2.0.1 and 2.1 but here's the release notes:
This is Ruby In Steel 2.1.0 build 1280.
1) The synchronization between RubyType and the ruby interpreter has been improved so that a type mismatch (debugger failing to load, etc.) is minimised.
2) JRuby 1.6.4 for Rails 3.3.1 has problems with SQLite3 - it cannot build the Gem - when running under Windows.
3) Ruby 1.9.3 is supported
4) Improved handling of exceptions by the debugger (1.9.2 and above)
Bugs fixed in build 1280
I736 File glyphs in Solution Explorer sometimes have a warning symbol (for example, those with no extension)
I737 The Ruby type should be displayed as well as the Ruby Interpreter field in the Application tab
I738 JRuby debugger needs to have the path to SteelCylon explicitly set in the command environment
I739 RubyType should not be visible in default options
I740 Check for updates produced the wrong information
I741 Debugger did not break if the breakpoint was on the first line
I742 SQLite3 should be the default option when creating a new Rails project
I743 '.gitkeep' should be in the list of extensions that are excluded from the project by default
I744 'Exclude files with no extension' should be set to false by default (for Rakefile and Gemfile)
I745 'Just in time' debugging did not work for Ruby 1.9.2
I746 boot processing should be enabled in webrick_service.rb
I747 F5 not visible when a .erb file had the focus
I748 Debugger looped in large Rails projects
I749 Rails Intellisense was broken by the new Ruby 1.9 'json: @posts' syntax
You can donload 2.1 from the downloads apage on the website.