Just when I thought I had got the hang of deploying .NET plugins they seem to stop working. I wanted to compile a list of steps and useful information that needs to be done in order to get a .NET plugin to work in RE. Does it make any difference to RE if you use a release or a debug configuration when building the dll? Firstly I know that you have to register the plugin with regasm and not with regsvr32. Also this only works for me when I use the /codebase switch - Anyone have any explanation as to why? However you should be able to use VS2005 setup project in order to have it register the plugin for you. It doesn't seem to do this. There are a few options when registering the primary output in the setup project either vsdrpCOM, vsdrpCOMSelfReg or vsdrpCOMRelativePath. Does anyone know the difference between these and which ones work? Even when I do use the setup project the files end up in the plugins directory (I am using a custom folder to do this in the setup project), the entry does not appear in under plugins. Instead I copy over all the output file including the pdb and xml files (pdb is a debug database) and when I register it using regasm it works (some of the time). Does anyone have a definitive explanation of which file are required and how to always ensure they appear in RE? Thanks David Zeidman Development http://www.zeidman.info  Check out my RE API blog http://re-decoded.com