Yes, that was VS 2008. Unfortunately the demo contained some unreleased
features so I couldn’t publish the code. But the idea was simple - an
addin-manager (C#) that hosts DLR and allows ruby scripts to create and
handle menu commands:
require ‘rubyaddin’
class TestRunnerAddin < RubyAddin
set_command_label “Run Test”
set_command_tooltip “Run selected test”
set_command_menu “Code Window”
def self.execute()
ctx = get_vs_context()
file = ctx.ActiveDocument
...
end
end
But then to make something useful you still need to cope with EnvDTE
(which was provided as part of context).
–
Oleg
From: [email protected]
[mailto:[email protected]] On Behalf Of Jimmy
Schementi
Sent: Friday, February 06, 2009 6:23 PM
To: [email protected]
Subject: Re: [Ironruby-core] automating VS
Na, that was definitely VS 2008. We just had our VS ninja Oleg write a
VS extension that hosts the DLR, so Ruby code could control VS. But
beats me if I know where that VS extension is.
~js
From: [email protected]
[mailto:[email protected]] On Behalf Of Michael
Letterle
Sent: Thursday, February 05, 2009 11:12 AM
To: [email protected]
Subject: Re: [Ironruby-core] automating VS
Ivan,
The RubyConf2008 talk? It’s on
confreaks:http://rubyconf2008.confreaks.com/ironruby.html
I’m pretty sure it’s using the new managed API for VS2010… EnvDTE is
painfull…
On Thu, Feb 5, 2009 at 1:30 PM, Ivan Porto C.
<[email protected]mailto:[email protected]> wrote:
Hi
A while ago I remeber seeing a screencast where John L. shows how to
use ironruby to automate visual studio.
I can’t find the screencast anymore but I would be interested to know
which API was used. Was that just using EnvDTE ?
I’m asking because at work we are using GAT to automate visual studio
and to create a kind of software factory (without the visual designers)
When it comes to developing with GAT I think most of us will agree that
there are more pleasant ways to develop and debug your work.
So I may get the chance to get them to use IronRuby for some of that
stuff as long as we can hide from the use case/LOB developers.
Using GAT for us is a hazard to make our sprints. Most of our story
points for example go into GAT development and debugging, granted that
we do make it do some crazy stuff too.
Thanks