可换肤的 Windows 窗体应用程序：处理不同的图标集
开始时，我们将所有图标放在源代码管理中的一个文件夹中，所有 Windows 窗体项目都从其 .resx 文件引用该文件夹中的图标。
既然我们决定拥有不同外观的 GUI，我们又创建了两个图标集，它们都具有相同的名称，每个图标集都有自己的文件夹，这样当我们想要使用不同的图标时，我们只需复制并粘贴到“main”中即可文件夹。
这种方法的问题在于源代码控制：每当我们提交时，如果我们更改了图标，我们必须小心不要发送图标。这很麻烦。
如何避免这种情况，同时将所有图标置于源代码控制之下？有没有标准的方法来处理这个问题？
When we started, we put all icons inside a folder in source control, and all Windows Forms projects reference icons inside that folder from their .resx file.
Now that we decided to have different-looking GUIs, we created two more icon sets, all with same names, each into its own folder, so that when we want to use a different one, we just copy and paste into the "main" folder.
The problem with this approach is source control: whenever we commit, we must be careful not to send our icons, if we changed them. This is very bothersome.
How can this be avoided, while keeping all icons under source control? Is there a standard way to handle this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
有一个配置标志，指示要使用哪一组图标。然后，您只需将工作区配置为指向正确的图标集，而无需踩踏彼此的图标集。
为了防止配置文件在 VC 中相互干扰，请让 VC 存储具有合理默认值的配置文件模板，然后将实际配置文件设置为被 VC 系统忽略。
例如，我们将
web.config.template签入 VC 系统并在其中进行任何系统范围的配置更改。每个开发人员（以及任何其他类型的部署）都将拥有自己的模板文件副本，其中包含其特定的配置需求。为了帮助了解主配置文件何时发生更改，我们有一组钩子脚本，用于通知用户已发生更改并与本地文件进行自动比较，以及在更改主配置文件时需要设置显式标志主文件。
Have a configuration flag that indicates which set of icons to use. Then, instead of stomping on each other's icon sets, you only need to configure your workspace to point at the correct one.
To keep from having config files stomping on each other in VC, have the VC store a template of the config file with sensible default values, and then have the actual config file be ignored by the VC system.
For example, we will have
web.config.templatechecked in to the VC system and make any system-wide config changes in there. Each developer (and any other sort of deployment) will have their own copy of the template file with their specific config needs in it.To assist with knowing when the master config file has been changed, we have a set of hook scripts that notify the user that there have been changes and auto-diff against the local file, as well as requiring explicit flags to be set when changing the master file.