Ivan,
When using IronRuby.Rack and debugging the ruby code running, keep a few things
in mind:
1. Enable debug mode for DLR code in your app’s web.config (in the
Microsoft.Scripting section).
2. Because VS breakpoints in blocks don’t work yet, using Debug.Assert
will do the job.
Ivan Porto Carrero wrote:
I am unable to debug the application though. If I put
System::Diagnostics::Debugger.break somewhere it will correctly break there
but eventually visual studio (2008 and 2010) will just get tired of it and
claim they have to quit. I've seen that the debug windows gives
...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Cory Foy
Sent: Sunday, March 14, 2010 11:25 PM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] IronRuby.Rack how to debug?
Ivan Porto Carrero wrote:
I am unable to debug the application though. If I put
System
-core@rubyforge.org
Subject: Re: [Ironruby-core] IronRuby.Rack how to debug?
Ivan Porto Carrero wrote:
I am unable to debug the application though. If I put
System::Diagnostics::Debugger.break somewhere it will correctly break
there
but eventually visual studio (2008 and 2010) will just
Sent: Monday, March 15, 2010 11:49 AM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] IronRuby.Rack how to debug?
I can attach and step through but just when the interesting bit occurs visual
studio takes a hike
but will try this again later
---
Met vriendelijke groeten - Best
Hi
IronRuby.Rack isn't passing the windows credentials through, but uses the
credentials from the app pool so using a user + password in database.yml did
change the error message.
development:
mode: ADONET
adapter: sqlserver
database: mocktwitter_dev
username: sa
password:
host:
