导出/导入Visual Studio配置属性设置 [英] Export / Import Visual Studio Configuration Properties Settings

问题描述

大家好，

我一直在Visual Studio 2008中不断使用C ++库，每次启动新项目时，该库都需要在项目的配置属性中更改大量字段.

我倾向于从现有的工作项目中手动复制设置，但是不可避免地，我会犯错并错过一些东西，因此开始一个新项目所花的时间比应该花的时间长得多.

我想知道是否可以导出正在运行的Visual Studio项目的配置属性，以便在启动新项目时可以快速导入这些设置.

我已经查看了导入和导出设置向导"(在Google搜索之后)，但这似乎是指整个环境的设置(不是特定于项目的).

谢谢，

Ad

Hey Guys,

I''m constantly using a C++ library with Visual Studio 2008 which requires a large number of fields to be changed in the project''s Configuration Properties every time I start a new project.

I tend to copy the settings manually from an exisiting working project, but inevitably, I make mistakes and miss out stuff, so starting a new project takes much longer than it should.

I''d like to know if there is a way of exporting the Configuration Properties of a working visual studio project so that I can quickly import these settings whenever I start a new project.

I''ve looked at the Import and Export Settings Wizard (after a Google Search), but this seems to refer to the settings for the environment as a whole (not project specific).

Thanks,

Ad

推荐答案

您是对的.您要保留的设置存储在项目文件*.* proj中，而不存储在任何Visual Studio设置中.你不觉得这对你很好吗?

当然，可以发明任何一种软件工具来收集，保存，分类和还原项目设置，在项目之间转移设置，克隆等等.是否可以以Visual Studio插件的形式完成.

我原则上不喜欢这种活动.它只会分散编程活动的本质.

Microsoft保证您的项目及其源代码的备份兼容性，但是谁能保证您的操作将保持有效，因为某些新设置会随项目文件架构的新版本一起添加，而某些版本已被弃用?您现在正在处理某些类型的项目，但是您如何知道将来要做什么?我认为这项活动不会浪费您宝贵的工作时间.

为什么不简单地组织工作?使用所有设置创建一些几乎为空的项目，这可以作为大多数项目的 起点 .将其用作创建实际工作项目的 模板 .当您确认此起点项目适合此目的时，请将其存储在版本控制系统中.当您由于需要不同而需要不同的模板时，请创建另一个模板.我会说，便宜又坚固.

(并且甚至不要怀着没有版本控制系统就做任何事情的想法.它可以是轻巧，便携式，可靠且免费的.请参阅以下讨论:

You are right. The settings you''re trying to preserve are stored in the project file *.*proj, not in any Visual Studio settings. Don''t you think this is very good for you?

Of course, it is possible to invent any kind of software tool to collect, preserve, classify and restore the project settings, transfer settings between projects, cloning, and so forth. It could be done in the form of Visual Studio plug-in or not.

I don''t like this kind of activity in principle. It only distracts from the essence of programming activity.

Microsoft guarantees backup compatibility of your projects with their source code, but who will guarantee that your manipulations will remain valid as some new settings are added with new versions of project file schema, some are deprecated? You''re working with certain types of project today, but how do you know what are you going to do in future? I don''t think this activity would make a good investment of your valuable working time.

Why not simply organizing your work? Create some nearly empty project with all settings which is good as a starting point for majority of your projects. Use it as a template for creating your real working projects. When you validate that this starting-point project is good for the purpose, store it in your revision control system. When you feel you need a different template because you come to different requirements — create another template. I would say, cheap and robust.

(And don''t even play with the idea of doing anything without Revision Control system. It can be light-weight, portable, reliable and free of charge. See this discussion: Revision control systems, which to choose from?[^].)


Don''t get me wrong. I tune and alter my system and working environment very meticulously, spending considerable amount of time to perfect it. Only I don''t contaminate or bloat it, trying to keep to bare minimum of tools, all thoroughly tuned. If work can be done reasonable well without some utility, that utility is to be exterminated.

—SA

您可以使用多种构建工具:
CMake [ ^ ]
NMake [ GNU Make [ ^ ]
MPC [ ^ ]

知道如何使用各种构建工具对于c/c ++开发人员无疑是有用的.

最好的问候
Espen Harlinn

You can use a fair number of build tools:
CMake[^]
NMake[^]
GNU Make[^]
MPC[^]

Knowing how to use various build tools is certainly useful for a c/c++ developer.

Best regards
Espen Harlinn

这篇关于导出/导入Visual Studio配置属性设置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！