>>I am not concerned about that - this is an in house app and not a vertical market one.

That's good re obfuscation, especially since declarative obfuscation means still you can use your own libraries for such a project, but also because an in-house app makes it more likely that you can avoid the dynamic code, which (without knowing all the circumstances) might be the wisest approach IMHO. Perhaps you could hammer out a quick VFP proc to parse the xml and create a VB.NET conditional proc commented with the old VFP code for conversion to equivalent VB.NET actions. The flexibility may be gone but if you make it a separate assembly it's easy enough to update as needed.