One of the things that really makes reflector a fantastic tool for me is the add-ins. The code model and the analysis that this makes possible is fantastic.
As part of our automated build (using CC.NET) I use the Code Metrics add-in to perform some static analysis and report the output in the build report. I run this from the command line.
I note that when the application starts up from the command line it still attempts to access the desktop and use message boxes to solicit input from the user (e.g. when an update to reflected is required/available for download).
This behaviour causes a timeout and exception in our automated build.
Do any plans exist to improve the usability of the tool from the command line? A switch would be one option, or a reflector-console.exe (a-la nunit).
As the code model and analysis functionality in reflector is so good I would expect more add-in functionality to be developed around performing static analysis and these tools would be useful to run from the command line as part of automated builds.
As part of our automated build (using CC.NET) I use the Code Metrics add-in to perform some static analysis and report the output in the build report. I run this from the command line.
I note that when the application starts up from the command line it still attempts to access the desktop and use message boxes to solicit input from the user (e.g. when an update to reflected is required/available for download).
This behaviour causes a timeout and exception in our automated build.
Do any plans exist to improve the usability of the tool from the command line? A switch would be one option, or a reflector-console.exe (a-la nunit).
As the code model and analysis functionality in reflector is so good I would expect more add-in functionality to be developed around performing static analysis and these tools would be useful to run from the command line as part of automated builds.