SapphireSteel Forum
Welcome,
Guest
. Please
login
or
register
.
May 20, 2013, 11:17:41 AM
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
Search:
Advanced search
Welcome to the SapphireSteel forum - for discussion of the Ruby In Steel and Amethyst IDEs
3883
Posts in
799
Topics by
669
Members
Latest Member:
m
SapphireSteel Forum
General
Ruby In Steel
Debugging causes Ruby in Steel package to initialize
« previous
next »
Pages:
[
1
]
Author
Topic: Debugging causes Ruby in Steel package to initialize (Read 2837 times)
m4dc4p
Registered User
Newbie
Posts: 34
Debugging causes Ruby in Steel package to initialize
«
on:
February 23, 2007, 10:43:57 AM »
When I have a non-ruby project (and no ruby files) loaded in the editor, and I try to debug a program with Visual Studio, the Ruby in Steel splash screen appears and the package appears to initalize itself. Because the Ruby in Steel package takes about 15 - 20 seconds to do whatever it does, this is a bit annoying.
It's pretty easy to reproduce:
1) Create a new Windows Application project
2) Click "Start Debugging" to launch it.
This is with the Ruby in Steel trial edition, version 01.00.0181
Justin
Logged
Huw Collingbourne
Administrator
Hero Member
Posts: 933
Re: Debugging causes Ruby in Steel package to initialize
«
Reply #1 on:
February 23, 2007, 11:54:48 AM »
Thanks for the information. We haven't been able to reproduce this so may need some more details.
From your description, what seems to be happening is that Visual Studio is issuing a request to initialize the Ruby In Steel package. If you are running another language with no reference to Ruby In Steel, this shouldn't occur. I'd be grateful if you could clarify a few things:
1. When you start the new (non-Ruby) application, do you create a new solution or do you add the new project to an existing solution which also includes Ruby projects?
2. Does this behaviour occur even if you load Visual Studio 'fresh' (without working on Ruby) and create a project in some non-Ruby language?
3. Are there any messages relating to Ruby shown in the General pane of the Output window when this happens?
4. When you say the 'splash screen', do you mean the main screen that includes a count of days left? Or do you mean the small screen that nornally pops before debugging in the Trial edition?
4. Which Operating system are you using?
I notice that you are using the first release of the Trial (we have had two updates since then) but, we are not aware of anything in that edition that should trigger this behaviour so I'd appreciate any help you can give us in tracking this down.
best wishes
Huw
Logged
AlexK
Newbie
Posts: 12
Re: Debugging causes Ruby in Steel package to initialize
«
Reply #2 on:
February 23, 2007, 01:34:36 PM »
Hi Huw
Since I have the same problem, I thought I would reply. I think I can clarify it a bit - Ruby is only initialised when I start debugging. When I run a project without debugging, nothing happens. It looks like full initialisation - I get the Ruby menu, and the Synchronise button in Solution Explorer.
1. I've got a C++ only solution - no Ruby files, no Ruby projects.
2. I tried to create a new solution, the problem still occurs
3. There weren't any messages in the General pane of Output
4. I got a black rectangle the size of the main splash screen fading in and causing a delay in the existing solution, and the normal main splash screen for the new test solution.
5. I'm using Windows XP SP2, VS2005 SP1, and RiS 1.00.0202
Logged
Pages:
[
1
]
« previous
next »
Jump to:
Please select a destination:
-----------------------------
General
-----------------------------
=> News and Announcements
=> Amethyst
=> Ruby In Steel
=> Ruby Programming
=> The Snug Bar