如何在Visual Studio 2017中为超过24 GB文件的项目生成msi/exe安装程序文件? [英] How to generate msi/exe installer file in visual studio 2017 for a project of over 24 GB files?
问题描述
我有一个WPF项目，该项目的资源(视频)超过24 GB，我在Visual Studio 2017中将配置设置为如果较新则复制".我想生成将包含我所有资源(视频)的安装程序文件在debug/bin文件夹中. 我已经尝试过Microsoft Visual Studio安装程序扩展程序，但是它只能生成700Kb的exe文件.
I have a WPF project which has a resource (videos) with over 24 GB, I have set the configuration to Copy if newer in Visual Studio 2017. I want to generate installer files that will include all my resources (videos) that are inside the debug/bin folder. I have tried Microsoft Visual Studio installer extension but that generates only 700Kb of exe file.
请提出建议.
推荐答案
在线? :说实话，我会检查是否可以放这样的视频在线(甚至是Youtube?)，而不是将它们捆绑在设置中-尤其是如果您可能想更新它们时.这将需要服务器和带宽(除非您使用Youtube)，但也将允许使用更小的设置大小，这是非常理想的(构建周转时间和处理过程中的整体混乱情况)较大的文件)，并且随着时间的推移，内容的可维护性也更好(您可以立即为所有用户更新视频-甚至可以删除突然不再分发的视频，也可以将视频替换为较低或较低的视频)您认为合适的高分辨率版本).此外，您可以跟踪人们实际观看的视频，并且可以(如果提供)从用户收集反馈.我不确定所涉及的版权和法律问题，但是如果这些是您的视频，则应该可以.如何将 YouTube 用于低分辨率版本?然后为高分辨率版本设置单独的千兆字节大小的设置?如果在线版本有消失的风险，并且您不希望在本地进行全尺寸安装，则可以在安装程序中包含一些分辨率很低的视频版本.
Online?: In all honestly, I would check if it is possible to put videos like that online (even Youtube?) instead of bundling them inside a setup - especially if you might ever want to update them. This will require a server and bandwidth (unless you Youtube it), but it will also allow smaller setup size which is very desirable (build turnaround time and overall messiness of dealing with large files) and also much better maintainability over time for the content (you can update the videos for all users instantly - and you can even take videos down that you suddenly don't want distributed anymore, or you can replace the videos with lower or higher resolution versions as you see fit). Further you can track what videos people actually view, and you can gather feedback from the users if you provide a means to do so. I am not sure of the copyright and legal issues involved, but if these are your videos you should be fine. How about using YouTube for low-res versions? And then a separate gigabyte-size setup for high-res versions? You could include some very low-res versions of the videos in your setup if the online versions are at risk of disappearing and you want no local full-size installation.
大文件问题 :同样重要的是要指出您不能在 FAT32 分区和其他分区上存储大文件文件系统也可能有问题.大文件很痛苦.现在我还没有使用过部署工具中的某些缓存功能-我很确定WiX拥有此功能，而且我认为其他工具也可以.也许 Bogdan 或 Urman 可以发表评论?
Large Files Concerns: It is also important to point out that you can't store a file that big on FAT32 partitions and other file systems might have problems as well. Large files are painful. There may be caching features in deployment tools now that I have not used - I am pretty sure WiX has this, and I think the other tools do as well. Maybe Bogdan or Urman can comment?
Deployment Tools: I have an ad-hoc summary of different deployment tools here. WiX is free and open source, most of the other tools are commercial and very good for most deployment tasks.
- 这是一个WiX快速入门篇
- 这是高级安装程序门户网站& ; 用户指南
- Installshield 2018联机文档
- PACE套件PDF (大量下载)
- Here is a WiX quick start piece
- Here is an Advanced Installer Portal & User Guide
- Installshield 2018 online documentation
- PACE Suite PDF (large download)
VS安装程序项目限制 :Visual Studio安装程序项目有很多限制，这是 外部源文件 :MSI支持外部源文件.所有部署工具-包括免费的WiX-都应该能够支持此功能，但是我不确定Visual Studio Installer项目是否支持它.使用这种方法，您可以快速重建测试和QA设置，而无需为每个构建都压缩整个视频文件夹-消除了大型构建的烦恼.哇！这大大缩短了周转时间.对于最终版本，您可以压缩所有内容-如果需要的话.
External Source Files: MSI supports external source files. All deployment tools - including the free WiX - should be able to support this, but I am not sure that Visual Studio Installer Projects supports it. Using this approach you can rebuild test and QA setups quickly without compressing the whole video folder for every build - vanquishing the lunacy of large builds. Woho! This drastically improves turnaround time. For the final release you can compress everything - if need be.
我从没用过那么多，但是在WiX中会是这样的:
I have never used this much, but in WiX it would be something like:
<Media Id="1" />
<..>
<Component Feature="MainApplication">
<File Source="TestLicenseAgreement.rtf" Compressed="no" />
</Component>
我不确定是否可以将文件保留在原处，或者是否始终将其复制到生成输出文件夹中.
I am not sure if you can have the file remain where it is, or if it is copied to the build output folder at all times.
Need-For-Speed: Some further options here (availability differs between tools): Speed up Build-Process of WiX-Installer (shimming files, light compression, release flags, compiler options, splitting large setups into prerequisite setups, etc...).
这篇关于如何在Visual Studio 2017中为超过24 GB文件的项目生成msi/exe安装程序文件?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
