Short of actually encouraging the deployment of script based solutions when performance/robustness is required - I largely agree with the writer.
For all new Groove projects that will not be written in managed code, I plan to use a high level language to prototype and then port to another language for deployment. An example would be writing some code in JavaScript, getting the concepts to work, then porting to C++ to gain performance/robustness. This strategy works well for me in Groove world because tool template files can have JavaScript embedded within it, and when used in conjunction with the "My Templates" functionality, allows changes to the tool template file/script code to be immediately tested without having to shutdown Groove.
10:24:04 AM 
|
|
