There is an add-on module you can download to achieve this. It worked
well for my asp debugging. It's called PreExecuteTroubleshooter (or
something to that effect). There is a setting in the RD ini file that
you have to change while you use the add on, but it works very well.

On Mar 12, 1:52 am, markus giesen <[email protected]> wrote:
> Hi Barry,
>
> unfortunately RedDot renders the .net code in these separated files
> and then outputs the returned code as plain HTML to the preview.
> So the answer (as far as I know) is no :(
>
> Cheers,
> Markus
>
> On 12 Mrz., 15:01, BjP <[email protected]> wrote:
>
>
>
> > Hi Markus,
>
> > Yes Im aware of that method, but once more it assumes I have access to
> > the .aspx files generated in the temp files.  Is there any way I can
> > just get the .NET error appearing in the preview window by
> > modification of the RedDot settings?
>
> > Cheers,
> > Barry
>
> > On Mar 12, 1:10 pm, markus giesen <[email protected]> wrote:
>
> > > hi barry,
>
> > > did you try to have a look at the generated prexecutetemp files inside
> > > [yourRDfolder]\CMS\ASP
> > > ?
>
> > > When you load a page containing preexecutes that's the place where
> > > they should come up.
> > > just sort by "date modified" and enjoy the pressing F5 or right-click
> > > reload... :)
>
> > > Ceers,
> > > Markus
>
> > > On 11 Mrz., 09:51, BjP <[email protected]> wrote:
>
> > > > Hello,
>
> > > > We have recently decided to move our CMS project from running asp to
> > > > aspx in pre-execute block marks.
>
> > > > The issue we are having is that to get meaningful error messages
> > > > (instead of the RedDot 500 internal server error) I have had to set
> > > > the flags=256 on the RDServer.ini, use the pre-execute troubleshooter
> > > > plugin and make the calls directly from a remote desktop session on
> > > > the development server.
>
> > > > Ive tried changing the web.config in the cms/asp dir to;
>
> > > > <?xml version="1.0" encoding="utf-8"?>
> > > > <configuration>
> > > >     <system.web>
> > > >         <customErrors mode="Off" />
> > > >     </system.web>
> > > > </configuration>
>
> > > > but this doesnt seem to do anything.
>
> > > > Does anyone know a way that we can get meaningful errors from normally
> > > > working with the CMS through preview/smartedit mode to allow us to
> > > > work normally with the project?
>
> > > > Also with flags set to 256 all our render tags dont work either so its
> > > > all together not a great environment to try to debug!
>
> > > > Thanks,
> > > > BjP- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/RedDot-CMS-Users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to