project level command line parameters compiled into another assembly?????

Question

We have an application that was developed using a plugin technology. You have the core engine. The engine has reference to all the plugins in the config file. We also use a test harness to build the two/three command line arguments required for processing. For clarity we have engine.exe (the  production app) and Testbed.exe (our app that calls the engine.exe project and invokes an instance. passing in the command line parameters.

Yesterday we had an interesting issue. The Engine.exe went to QA and failed because it just looped after copying a file to the work folder. I took the file and processed it locally and had no problem. Changed from Debug to Release and had the same issue as QA. TURNS out that the command line  arguments in the testbed project did not match between Debug and Release. I get how that was an issue and a simple fix.

Here is my dilemma and confusion. HOW did the command line arguments from the testbed.proj get imbedded into the Engine.exe. I deleted the debug symbol files, cleaned the solution, removed and reestablished the project references (so there were no assembly references), did a batch build of the solution

In the end I removed the command line arguments from the tesetbed project, did a release batch build, deleted the testbed.exe & config. Then and ONLY then did the release version of the engine.exe preform as the debug version did.

I would love to know how project line command line arguments are compiled into an exe. When the default project is not the production app how do the parameters get compiled into the other application?

---

Missionary Serving in my appointed field

Answer 1

Hi David,

As far as I know, a command line argument will not embed into exe using Visual Studio. I suggest you double check the code to see if there is any hard code for the arguments.

Regards,

Yi

---

Yi Feng Li [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Hello,

Would you mind letting me know the result of the suggestions? If you need further assistance, feel free to let me know. I will be more than happy to be of assistance.

Yi

---

Yi Feng Li [MSFT]
MSDN Community Support | Feedback to us

Answer 3

Unless you perform some debugging (probably via Visual Studio, http://blogs.msdn.com/b/visualstudio/archive/2010/07/06/debugging-msbuild-script-with-visual-studio.aspx) it is impossible to tell the cause, as you are using a custom script to compile it. Maybe you wrote something wrong.

---

Lex Li (http://lextm.com)