Clever Geek Handbook

Codenamed and Visual Studio products

Are there any methods for using product codenames in Visual Studio projects and solutions? Typically namespaces, assembly names, binary outputs, etc. Need to rename after choosing a product name: is there a way to handle this?

+1


source to share


2 answers


This depends in part on the type of product. If it's a client-side library - or anything that requires users to see the names, then it's clear that the names matter. I don't think it really matters. Be aware that different versions of a product may have new codenames (e.g. Everett, Whidbey, Orcas for Visual Studio) - you don't want to rename the code every time you launch a new version!



+1


source


In one place I worked, we would choose an unrelated and harmless, and usually systematic name for any given project. Jupiter, Orca, Feynman ... and stick with this namespace forever.

Because as you've seen what the marketing / customer / board chooses to call the product (heck, not even the version number they pick), it is so rarely known at the beginning, let alone at the end, that it is it's just a lot easier for everyone to be able to have a fixed internal reference that they don't need to refactor later.



I cannot stress how important it is for the name to be simple, one word, and harmless.

+2


source






More articles:


All Articles