Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Our .net executable project is called “<CompanyName>.<ProductName>.Client“, and we’ve set the assembly name for the project “<ProductName>.exe” – Seems legit, right?
A co-worker asked me this:
Why won’t we call it simply “<CompanyName>.<ProductName>.Client.exe“?, and I couldn’t back any answer with any article or best-practices guide.
What are the best practices of naming an executable, and why?
Thanks!
c:\program files\company name\product name\executable_name.exeUpdate for @Oded:
As you can see, the usual placement path of executables contains both company and product names so there is no need to repeat yourself.
For internal products/tools I personally use full names.
Don’t use spaces in executable names, it’ll make you use quotes in command line.