Archive for February 24th, 2012

Ruby in Steel on Visual Studio 2008

The only professional Ruby development tool for Visual Studio, Ruby In Steel Developer 2 has powerful analytical IntelliSense, the fast ‘Cylon’ debugger, syntax-sensitive editing and comprehensive development support for Ruby and Rails.

– Go to: Ruby In Steel Download Page

Here we provide a brief overview of just a few of the major features of Ruby In Steel…

Ruby In Steel’s ultra-fast ‘Cylon’ debugger provides…

– Speed

The ultra-fast ‘Cylon’ debugger

Ruby and Rails debugging is notoriously slow. Not any longer. Ruby In Steel’s Cylon debugger blazes through your code.

– Breakpoints and Tracing

Step through your code

Step into/step-out/step-over code in Ruby and Rails applications.

– Hover and Drill-down

Drill-down debugging

Drill-down debugging lets you look inside objects and expand arrays and hashes in the docked debugging windows, in the code editor or even right inside the interactive Ruby console!

Docked debug windows

– Conditional Breakpoints

Add conditions in Ruby code

Break when a condition (a test of one or more values) is met.

Other debugging features:
– Tracepoints
– JRuby Debugger
– Break on exception
– Break on hitcount
– Run macro on break

The debugger is supported by a range of tools and windows including:
– Watch
– Locals
– Autos
– Quick Watch
– Breakpoints
– Call Stack.

Ruby In Steel provides extensive syntax-aware editing for Ruby and Rails.

– Code Coloring and Code Folding

Code coloring and folding

The code editors provide customizable coloring – even for Ruby code embedded into Rails Erb templates. Code folding operates on classes, modules, methods, if blocks and many other constructs – including user-defined collapsible regions…

– Bracket and Keyword/end Matching

Keyword..end matching

Opening and closing brackets are highlighted. A keyboard shortcut lets you move you cursor between brackets or Ruby keyword/end pairs such as class…end and def..end.

Ruby In Steel also has…

Snippets with ‘edit points’

– Snippets that auto-generate code blocks

Ruby and ERb Snippet editor

– A Snippet editor to let you create your own snippets without coding
– Smart or Block indenting to auto-align align your code
– Automatic code formatting (a selected block or an entire document)
Plus all the editing features you would expect such as multi-level undo/redo, bookmarks, split-window editing and user definable macros.

Ruby In Steel offers unparalleled analytical code completion and navigation tools for Ruby.

– Fast Code Completion Analyzes Code As It Is Written

Drop-down lists provide relevant and accurate information on the methods that are available to objects and classes (both those in the Ruby and Rails libraries and those that you write yourself).

‘Local scope’ (Common) code completion

Dual-page completion lists let you show class-specific detail, for clarity (see above) or the members of the class and all its ancestors, for completeness (see below).

Broader scope (All) code completion

Code completion is automatically triggered by a dot after an identifier and by the double-colon :: scope resolution operator. Completion lists may also be triggered by CTRL-Space. The IntelliSense engine analyzes code as it is written and updates completion lists as appropriate. You may optionally tailor completion lists by specifically omitting elements such as ancestor class methods, global variables and keywords. Notice that embedded (RDOC) documentation for members is shown in a tooltip. You can also hover over classes and methods in the editor to view RDOC.

– Tooltips and Parameter Completion

Parameter hints

Enter an opening bracket after a method name to see a highlighted hint showing parameters and their types.

Extra parameter information can be added via ‘type assertions’

In cases where classes cannot be inferred, add ‘type assertion’ comments for extra IntelliSense.

Tooltip hint for a variable

Hover over any object to see its fully-qualified (including ‘nested modules’) class name.

– Speed Unlike some other Ruby editors, the Ruby In Steel code completion is fast!
Ruby On Rails Tools

In addition to the Visual Rails Workbench, Ruby In Steel has deep support for Ruby On Rails Development

The Rake and Generate tools

It has project start-up wizards and (optionally) docked, tabbed and floating tool windows and dialogs such as:
– Generators
– Rake Tasks
– Gem Run
Tools and Wizards

Docked or floating consoles

– Fully integrated Ruby, Rails, Script and IRB consoles

Context-sensitive online documentation

– RDOC window shows formatted documentation when you hover over an object identifier in the editor

The Ruby Explorer

– The Ruby Explorer lets you navigate the class library – even into documentation extracted from C-source files

Context-sensitive Navigation Bars

– Drop-down Navigation Bars over the editor for fast code navigation

Manage projects in the Solution Explorer

Ruby In Steel projects are managed from the Visual Studio Solution Explorer. You can simply create, import or convert Ruby and Rails projects as well as add, move and delete files and folders. Ruby In Steel is fully configurable (colors, tab and formatting options etc.).

For more details, refer to The Feature List.

Minimum Requirements: Visual Studio 2010 Standard Edition or above; alternatively, use the Ruby In Steel ’All-in-one installer’ to install a free Ruby-language copy of Visual Studio 2010.

Link : Ruby in Steel

Ruby In Steel -> Visual Studio 2008 Edition

Free VS 2008 upgrade
by Huw Collingbourne, Employee @ SapphireSteel Software

Quite a few of our customers are already using the beta version of our Visual Studio 2008 edition of Ruby In Steel. Now that Microsoft has shipped the final release of VS 2008, we are going through a last round of testing prior to launching the first official VS 2008 edition of Ruby In Steel. That should be along in a few weeks.

Visual Studio 2008 has a number of new and useful features – such as the ability to make completion lists transparent when you press the Control key – very useful if you want to check the code under the list.

Over the past week or so we have had a number of enquiries from potential purchasers wanting to know if we will be charging extra for our VS 2008 edition. The answer is: No.

If you buy Ruby In Steel Developer today you will be able to upgrade your software to all subsequent editions of the version 1.x product at no additional cost. It makes no difference whether you want to carry on using the VS 2005 edition or if you prefer to switch to the VS 2008 edition. We’ll issue updates to both editions and all of the updates will be free to registered users. In fact, if you like, you may download and install both the VS 2005 and the VS 2008 updates. According to the terms of our license:

“If you wish to install the software onto more than one computer, you may do so. If a second person wishes to use the software, however, then you need to buy a second license.”

As we’ve previously stated, the price of Ruby In Steel will increase with the next major release (1.2) from $199 to $249. However, anyone who buys at the current lower price will have all the upgrades – free of charge – to all VS 2005 / 2008 editions throughout the lifetime of Ruby In Steel 1.x.

We shall shortly release a version of Ruby In Steel 2008 which, to the best of our knowledge, will be functionally equivalent to our VS 2005 product. However, until we are sure that there are no major incompatibilities with VS 2008, this version will be released as a beta. Our final release will follow after a further period of testing.

VisualStudio as my IronPython editor

The following steps are what I did to get Visual Studio ready as my IronPython (and IronRuby) editor.

* Install the latest internal dogfood build of Visual Studio 2008.
o you may use Visual Studio 2005 or download the VS 2008 public beta2;
* Download and install ASP.NET futures release (July 2007). This will give me the nice syntax coloring and (well… limited) intellisense for python code.
o you may download VSSDK 2008 CTP, and build the IronPython integration sample, which will give you the similar editing experience;
* Download the attached add-in binary zip (poorly named as DlrToolsAddin); for my Vista box, I extract them under “%USERPROFILE%\Documents\Visual Studio 2008\Addins”. I wrote this add-in basically to allow me to run the script inside the Visual Studio, and show the output in the output window.
o if you consider using it for VS 2005, you will need put it in “Visual Studio 2005\Addins”.

Say, I am trying the example in my previous post, I create a new C# file (sample.cs) without creating solution/project, I can press Ctrl+1 (or the first button in the DlrTools toobar) to get it compiled to sample.dll in the local directory. You see the compile result at the bottom output window. Then I create a python file ( in the same directory, type in some code (shown in color). Again, I can press Ctrl+1, the result are shown in the output window. I do not need leave VS and run these files in the cmd.exe window.

Sometimes I want to run the same code with different tools (for example, to check IronPython compatibility, I often run the same .py file against C-Python 2.5 too). That is the first combo box comes to play.

The second combo box is to set the working directory: “.” means the current directory where the active file lives, “..” for the parent directory of the current file, or you may use the absolute path. Such support is needed to run C-Python regression tests. (For the add-in implementation side, I feel what I really want is a combo box of type vsCommandControlTypeDynamicCombo, which seems not available for add-in development).

The delete button is to remove your tool choice for those files you pressed “Run Script”. By clicking the last button, an XML file (specifying which tools for which file extension) is opened so you may change it. You must update it with your tool paths, since the default setting is suited for myself.

You may also run part of the file by selecting those lines first (A temporary file is created and will be deleted after VS shutdown).

One bad thing I noticed of this add-in is that sometimes I press the “run script” button to start debugging, both icons have similar shapes.

To uninstall it, delete DlrToolsAddin.* files under “Addins”; and then run once “devenv.exe /resetaddin DlrToolsAddin.Connect”.

The source code (VS2008 project) is also attached. Disclaimer: THE CODE IS PROVIDED “AS IS”, WITH NO WARRANTIES INTENDED OR IMPLIED. USE AT YOUR OWN RISK. Hope you like Visual Studio as your IronPython editor.

Download Source Code Attached

%d bloggers like this: