VS2010删除重建解决方案上的非解决方案中间文件 [英] VS2010 Deletes non-solution intermediate files on a Rebuild Solution

查看:168
本文介绍了VS2010删除重建解决方案上的非解决方案中间文件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们从VS2008升级到VS2010( VS2012).我们有使用公共输出目录的多种解决方案. VS2008和更早版本具有仅删除的智能 定义的特定解决方案文件.重建解决方案将删除其.OBJ,.LIB,.EXP等(例如),但不保留其他解决方案文件(例如,它不会删除未引用的解决方案.OBJ,.LIB,.PDB文件).似乎VS2010(VS2012?)已经失去了这个 智能,现在删除所有文件,即使它们与该特定解决方案无关(例如,该文件所引用的.LIB也不相关).这是一个旧产品,实际上有数百个解决方案文件[各个DLLS,各种子产品EXE, 等].  我知道一个简单的答案是为每个解决方案创建单独的控制器,但是,由于该产品中包含许多单独的解决方案,因此执行升级是一项非常艰巨的任务.   我们希望丢失一些Rebuild开关,这将导致VS2010不接触该解决方案未引用的其他中间文件,并像VS2008一样执行智能清理.

We upgraded from VS2008 to VS2010 (on our way to VS2012). We have multiple solutions using a common output directory. Vs2008 and prior versions had intelligence to delete only the specific solution files defined. A Rebuild solution would delete its .OBJ, .LIB, .EXP, (etc.) but leave the other solution files alone (e.g., it would not delete non-referenced solution .OBJ, .LIB, .PDB files). It seems like VS2010 (VS2012?) has lost this intelligence and now deletes all files even if they are not related to that specific solution (nor are, for example, the .LIB referenced by it). This is an old product that literally has hundreds of solution files [individual DLLS, various sub-product EXEs, etc.].  I know a simple answer is to create separate directors for each solution, however, with the number of separate solutions within this product it becomes a very daunting task to perform the upgrade.  We were hoping for some Rebuild switch we have missed that will result in VS2010 not touching other intermediate files not referenced by the solution and perform an intelligent Clean like VS2008 did.

推荐答案

我正在调查此查询.会尽快更新您的信息.

I'm looking into this query now. Will update you soon.

谢谢.


这篇关于VS2010删除重建解决方案上的非解决方案中间文件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆