Rick Strahl's FoxPro and Web Connection Web Log
White Papers | Products | Message Board | News |

Last 2 Posts


Syntax Errors in the FoxPro Editor caused by Extended Characters


The FoxPro editor is prone to allow extended cahracters into the editor - some of which may be invisible and can cause some really nasty compiler bugs that are 'invisible'. Here's an example how that happened to me and how it caused me to think I'm going nuts.

Route Web Connection Scripts, Templates and Pages to a single Process Class


Web Connection supports automatic extension mapping to a single route handler by default. This typically means you can route a single extension to a single type of processing mechanism like the Script or Template engines or the Web Control Framework. However, the default behavior is easily overridable by explicitly overriding the script mode in OnProcessInit(). Here's how.


© Rick Strahl, West Wind Technologies, 2003 - 2017