The one area I wanted to specifically test though is the decompilation of an assembly to file, and it would appear to be disabled in the evaluation version.
I can see why this is so, but it is causing me some concern about going ahead with a purchase - Can you give me some insight into what kind of output the 'Decompile to file' will produce? Will it generate a complete project that can simply be loaded in Visual Studio (2003) and then compiled?
Decompile To File redirects decompilation output to the file. If you'll try to decompile some class, Spices.Decompiler tries to decompile managed resources connected to this class. If you'll try to decompile whole assembly, Spices.Decompiler will separate decompiled classes into namespaces files or class files (you can specify class separation options in the Spices.Decompiler plugin settings), decompile all managed and unmanaged resources, create AssemblyInfo file and create Visual studio project (usually - VS2003 project, but if decompiled assembly is .Net 2.0 related - VS2005 project).
Yes, this project you can be loaded into Visual Studio 2003 or 2005 and ready to work.
Also, When I looked at the license options I notice that there is a version with "Visual Studio Integration Pack". Could you provide details on what this additionally provides?
Spices.Net has a special package that completely integrates Spices.Net functionality into Visual Studio 2003 (we're prepared Spices.Net for VS2005 integration but not released). With Spices.VSIP you can integrate obfuscation into VS build process, can build-obfuscate-and debug assemblies and use Spices.Net plugins inside Visual Studio.
Spices.VSIP includes Spices.Net GUI, and you can use Spices.Net inside VS and as standalone application.
If you will have question or problem - feel free to contact us, we'll make every possible effort to assist you.