作者:mobiledu2502905213 | 来源:互联网 | 2023-06-11 18:46
iwanttohavesomesharedcode(codelibrary,controls,utilities,helperclasses,etc)inVisualS
i want to have some shared code (code library, controls, utilities, helper classes, etc) in Visual Studio. i do not mean shared assemblies, i mean shared code (i.e. i want to ship one assembly with my application, the executable assembly).
我想在Visual Studio中有一些共享代码(代码库,控件,实用程序,帮助程序类等)。我不是指共享程序集,我的意思是共享代码(即我想用我的应用程序,可执行程序集发送一个程序集)。
The technique in other development environments way is to have the common source code in a path on my machine, and the IDE is given a list of paths to search for code files.
其他开发环境方法中的技术是在我的机器上的路径中使用公共源代码,并为IDE提供搜索代码文件的路径列表。
Visual Studio does not support code search paths.
Visual Studio不支持代码搜索路径。
The back-up hack solution is to copy the source-code over and over into every project. But then in order to keep them all as one version, they are shared in source control. This works well when your source control provider is Microsoft Visual SourceSafe - which supports shared files.
备份黑客解决方案是将源代码一遍又一遍地复制到每个项目中。但是为了将它们全部保存为一个版本,它们在源代码控制中共享。当您的源代码管理提供程序是Microsoft Visual SourceSafe - 它支持共享文件时,这很有效。
But other source control products (CVS, Subversion, Microsoft Team Foundation Source Save Server, SVN) do not support shared files.
但其他源代码控制产品(CVS,Subversion,Microsoft Team Foundation Source Save Server,SVN)不支持共享文件。
So how does everyone else avoid shipping DLL's with their executable?
那么其他人如何避免使用可执行文件运送DLL?
Update 1
It is an issue of single file deployment. ClickOnce generates 18 files in 3 folders (i.e. more than one file)
这是单文件部署的问题。 ClickOnce在3个文件夹中生成18个文件(即多个文件)
4 个解决方案