Debugging Preexecute in OpenText WSM 10.1

[NP]

I've implemented Gavin Cope's great debugging log method (http://
www.reddotcmsblog.com/debugging-pre-executed-classic-asp) in a few
projects now in RedDot 9. I'm now working on a project in version 10.1
on Server 2008 with IIS7 and finding that it's not writing the error
logs, though it isn't breaking preexecution either and even wrote a
web.config file into the asp folder. Has anyone else gotten this
working? I have a feeling I missed something in IIS, but the setup is
different enough in version 7 that it's tough to say.

[Tony Gayter]

you can always set the flags in the rdserver.ini to 1280. this tells the CMS to leave the generated preexecute files etc in the prexecute directory. You can then open them in IE and see the error message.

Just never leave this in a production environment as its a fairly big performance hit (we usually have it on all the time in dev and have a nightly job to clean up the generated files over night.

[markus giesen]

Also: PreExecute is the devil..

Out of curiosity: what do you mainly use it for Tony?

[Tony Gayter]

We use if sparingly but as all our solutions are .net we often need to set variables from reddot content or just have .net run to get the output we need. In our best practice I have said not to use it unless there is no other way. A lot of devs come out of training thinking they will just write everything in .net and preexecute it rather than using the render tags approach. Which is understandable due to Rendertags making templates really verbose and difficult to maintain (why they cant improve the backend template editor is beyond me, a little bit of intellisense and tag matching woudl go a long way)