Think dilettante will chime. I somewhat remember a project where he did something similar but can't remember where I saw it...

Completely in uncharted waters here. I've never compiled a VB application via a command line and am looking for some pointers. To make this a bit easier to offer advice, it is a very specific scenario. Here's a reference from msdn, but not exactly sure what to use or which are mandatory, optional or preferred? Are those the only switches I need to be concerned with? This is where the gurus' experiences can help me.

I want to create a DLL project through code, drop it in a subfolder and compile it and then immediately unregister the DLL. This is nothing nefarious. I'm looking at an option to automate creation of resource-only DLLs. Ideally this would have no user interaction other than specifying the DLL's name and which resources to include. Assuming the coder has admin rights, no other interaction should be needed I think. I'm assuming (bad idea, huh?) that since VB will be used to kick off the command-line compilation, if the coder has admin rights to begin with, shouldn't be any hassles there. Correct?

This is something else I'd like some advice on: automating the unregistering, especially with regards to 32 and 64 bit systems if a Shell command is recommended. If an API will do this -- great!