代号产品和 Visual Studio
是否有关于在 Visual Studio 项目和解决方案中使用产品代号的做法？ 通常，一旦选择了产品名称，命名空间、程序集名称、二进制输出等就需要重命名：有什么方法可以处理这个问题吗？
Are there any practices regarding using codenames of products in Visual Studio projects and solutions? In that typically, namespaces, assembly names, binary outputs, et al need to be renamed once a product name is chosen: is there any way to deal with this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在我工作的一个地方，我们会为任何给定的项目选择一个不相关、无害的、典型的系统名称。Jupiter、Orca、Feynman 等等……并永远坚持使用该名称空间。
因为正如您所看到的，营销/客户/董事会选择如何称呼产品（见鬼，甚至他们选择的版本号）在开始时很少有人知道，更不用说到最后也一样，所以它就是这样每个人都可以更轻松地拥有固定的内部参考，而不必在以后进行重构。
我无法强调这个名字的重要性，因为它很简单，只有一个词，而且不具有冒犯性。
In one place I worked we'd choose an unrelated and inoffensive, and typically systematic name for any given project.. Jupiter, Orca, Feynman whatever... and stick with that namespace forevermore.
Because as you've seen what the marketing/client/board chooses to call a product (hell, even what version number they choose) is so rarely going to be known at the start let alone the same by the end, that it's just so much easier for everyone to be able to have a fixed internal reference they don't have to refactor later.
I can't stress how important it is that the name is simple, one word and inoffensive though.
这部分取决于产品的类型。 如果它是一个客户端库 - 或者任何需要用户查看名称的东西 - 那么显然名称很重要。 我认为其他情况并不重要。 请记住，产品的不同版本可能有新的代号（例如 Visual Studio 的 Everett、Whidbey、Orcas） - 您不希望每次启动新版本时都必须重命名代码！
This will partly depend on the type of product. If it's a client library - or anything that will require users to see the names - then clearly the names matter. I don't think it really matters otherwise. Bear in mind that different versions of the product may have new codenames (e.g. Everett, Whidbey, Orcas for Visual Studio) - you don't want to have to rename the code each time you start a new version!