Different generation behaviour on same Codesmith Project file (csp)

When I generate wihtin CodeSmith Studio, I have no problems.

 All my CodeSmith Projects files generate fine.

When I generate from within Visual Studio, or within Windows Explorer,  some of them raise an error during generation :

Any advice is wellcome.

 Thx

I am experiencing similar behavior.

Using Codesmith Studio template generate and respond to changes in the configuration as expected.

Using the Codesmith Explorer changes to the configuration are seemingly ignored. I have tried refreshing, closing and opening but the configuration still seems to be cached.
The configuration pane of the Explorer correctly shows the changes but they are not used during the generation phase.

In frustration I recompiled our extension library with some Response.Write 'debugging' and magically and suddenly the explorer behaved the same as the Studio.
I then made a change to a text file used as input to the template (field exludes) and again Explorer ignored the change while Studio executed properly.

This is a huge issue seeing as most our developers are using the standard version and only have access to the Explorer.
The caching that is going on may have been intended as a feature but it most certainly is not.

 What version of CodeSmith are you using?  We released a maintenance version in August that included a way to refresh cache when altering configuration values.

The error messages displayed when error occur during execution of csps do not provide enough useful information.  We have recreated this issue and are currently working on a fix for this.

Hi

Using version 4.1.2 rev 2729, which according to the application itself is the latest version.

But then I am not actually changing the configuration itself, I am changing a text file that a configuration setting points to and that the template uses to evaluate columns to skip for various tables.

For some reason the Explorer does not read the file on every run, in fact the caching mechanism is very long lived so not even a restart of the explorer solvs the issue. A computer restart does, but that seems a bit harsh to do that every time you need to change a config value... ;)