Best Practices for Naming Executable (EXE)
.net, executable
Solution
`c:\program files\company name\product name\executable_name.exe`
Update 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.
Problem
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!