使用 devenv 构建具有指定配置的智能智能设备 CAB 项目
我有一个包含智能设备 CAB 项目的 Visual Studio 2008 解决方案。我正在致力于自动化发布过程。我正在使用 devenv 构建用于构建 CAB 的 inf 文件，如下所示：
C:\programming\acs_reader2>"C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv" ACSreader2\ACSreader2Setup\ACSreader2Setup.vddproj /Rebuild Release /SafeMode
它确实构建了 inf 文件，但它对某些依赖项使用了错误的配置（测试而不是发布）。当我从 VS 内部构建时，这种情况不会发生。我做错了什么还是这是一个错误？如果这是一个错误，有没有办法解决这个问题？我拼命寻求避免手动维护 inf 文件。
我还尝试了这种其他格式，它与 devenv 重建 文档，您可以在其中指定解决方案名称和配置以及项目名称和配置。也会出现同样的问题。
I have a Visual Studio 2008 solution with a Smart Device CAB project. I am working on automating the release process. I am using devenv to build the inf file that I use to build the CAB like this:
C:\programming\acs_reader2>"C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv" ACSreader2\ACSreader2Setup\ACSreader2Setup.vddproj /Rebuild Release /SafeMode
It does build the inf file, but it uses the wrong configuration (Test instead of Release) for some of the dependencies. When I build from within VS, this does not happen. Am I doing something wrong or is this a bug? If it is a bug is there a way to work around this? I am desperately seeking to avoid having to manually maintain the inf file.
I have also tried this other format which matches up more closely with the example from the devenv rebuild documentation where you specify both the solution name and configuration and the project name and configuration. The same problem occurs.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我试图想出一个更有创意的解决方案来解决这个问题，我找到了！我是从二维角度看待这个问题的。 CAB 文件多年来一直给我带来问题。解决方案是什么？不要使用 CAB 文件！我们的安装过程已经从在设备上运行并下载文件的可执行文件开始，因此我将让它完成所有工作。无论如何，所有依赖项最终都会在构建后出现在输出文件夹中。
I was trying to come up with a more creative solution to this problem, and I figured it out! I was looking at this so 2 dimensionally. CAB files have been giving me problems for years now. The solution? Don't use CAB files! Our installation process already starts with an executable that runs on the device and downloads files, so I will just have it do all the work. All the dependencies end up in the output folder after a build anyway.