|
From: <MRo...@th...> - 2003-06-06 09:21:09
|
The J-out-of-T debugging issue is still relevant on machines without VS as
I hit this very thing this week on a build box without it. I haven't got
around to finding the switch to turn it off yet, but at a quick glance, I
don't think its anything you can put in an application's .config file.
Another problem I had with this situation is that my ccnet.state file was
left in corrupt condition, and CCNet would not start without me manually
editting the file (deleting the contents of the <output> tag worked for
me) - this is bug and needs to be fixed (its on my list, but if anyone
else fancies looking at it, go ahead! :) )
Mike
mc...@th...
Sent by: ccn...@li...
06/05/2003 09:49 AM
To: ccn...@li...
cc:
Subject: RE: [Ccnet-devel] Re: shipping nant with ccnet
CCnet has a build timeout feature already. I think it defaults to 30
seconds. There is a possibility that it isn't working right or that it has
trouble with the modal dialog. If this modal dialog is the typical,
"You're stupid app through an exception! Do you want to debug? yada yada"
(Paraphrasing, in case you couldn't tell.) then there is a way to turn
that off. When it is off the exception just gets thrown and things proceed
as usual. This only happens on machines with vs.net installed (I think,
not 100% positive on that). It is called Just In Time debugging. Although,
"Just one line of code too late" might be more apt.
To turn off just in time debugging on a machine with vs.net installed go
into vs.net, tools menu, select options, expand the debugging folder and
select the just in time debugging option. Uncheck everything.
I think that should be a standard setup on a build machine.
If only the .NET runtime is installed I don't know if the same thing
happens.
Mike Two; Putting the tWo in Thoughrks
|