Friday, May 14, 2004
Interesting tool + script task
Another interesting .net dev tool discovered today. SnippetCompiler is a mini IDE for editing and running those throw-away apps you're always building to test some small thing out of the context of your current application. Its kinda like the immediate mode that python programmers know and love:
- ie a lightweight sandbox for trying out ideas in code without the hassle of calling compilers and or build tools. I found it interesting because I've recently been working on nants script task which in some ways does the same thing - ie allows you to work on nant extensions in a lightweight manner without having to build a full project.
Tracking down a bug in afore mentioned script task I realized that the code that compiles the inline script adds all the currently loaded assemblies as references. This works fine but kinda breaks the nice framework targetting support in nant. ie you might have specified version 1.0 of the framework on the commandline but the script task will grab assemblies from the currently executing runtime. I should think about adding the common system assemblies ( perhaps using csc.exe's response file ) from the current framework directory instead.
- ie a lightweight sandbox for trying out ideas in code without the hassle of calling compilers and or build tools. I found it interesting because I've recently been working on nants script task which in some ways does the same thing - ie allows you to work on nant extensions in a lightweight manner without having to build a full project.
Tracking down a bug in afore mentioned script task I realized that the code that compiles the inline script adds all the currently loaded assemblies as references. This works fine but kinda breaks the nice framework targetting support in nant. ie you might have specified version 1.0 of the framework on the commandline but the script task will grab assemblies from the currently executing runtime. I should think about adding the common system assemblies ( perhaps using csc.exe's response file ) from the current framework directory instead.
