thanks for you answer. The application cannot seem to start when using a
semicolon to separate values in initParams. I tried comma instead (the
application manages to start this way - not sure if the param is passed
properly though):
<param name="initParams"
value=“debug=true,reportErrors=errorLocation”
/>
either way, the breakpoints remain in the same state (inactivated).
I guess it’s a first step although something still must be missing. When
refreshing the browser windows, should a new debugger pop up ? Could it
be
some option at the internet explorer level ?
I may be mistaken, but I believe only the IronRuby bits on http://dynamicsilverlight.net can be debugged in Silverlight. I just did a
test and I cannot debug the ruby clock demo with the Silverlight SDK bits,
but it works with the Dynamic Silverlight bits. So, first make sure you’re
using the latest and greatest stuff from the web.
Hooray. It works now! FWIW: the simplest way to do this for me was to
copy the Dynamic SDK dlls from /bin to my application /app (it seems
that Chiron will pick them instead if they are here).
the simplest way to do this for me was to
copy the Dynamic SDK dlls from /bin to my application /app (it seems
that Chiron will pick them instead if they are here).
Sure. =) You can also put them in the /bin directory that Chiron points
to so all your apps can use them.
I may be mistaken, but I believe only the IronRuby bits on http://dynamicsilverlight.net can be debugged in Silverlight. I just did
a test and I cannot debug the ruby clock demo with the Silverlight SDK
bits, but it works with the Dynamic Silverlight bits. So, first make
sure you’re using the latest and greatest stuff from the web.
If you run the app, open the ruby file in VS, put a breakpoint in it,
attach to your browser running the app, and refresh the browser, you
should see the breakpoint flicker a bit and then break at the line.
This shouldn’t depend on any IE settings; you can debug Firefox as well.
thanks for you answer. The application cannot seem to start when using a
semicolon to separate values in initParams. I tried comma instead (the
application manages to start this way - not sure if the param is passed
properly though):
<param name="initParams"
value=“debug=true,reportErrors=errorLocation” />
either way, the breakpoints remain in the same state (inactivated).
I guess it’s a first step although something still must be missing. When
refreshing the browser windows, should a new debugger pop up ? Could it
be some option at the internet explorer level ?
It may be worth updating ProgramDlr.aspx with those additional tips ?
I have a related question: will it be (or is it currently ?) possible to
do
step-by-step debugging with any of the free products (Visual Studio C#
express 2008, VS 2008 shell version, any other ?).
It may be worth updating ProgramDlr.aspx with those additional tips ?
I have a related question: will it be (or is it currently ?) possible to
do step-by-step debugging with any of the free products (Visual Studio
C# express 2008, VS 2008 shell version, any other ?).