简体繁体 English

发布构建包问题

[英]Release build package issue

原文 2018-03-22 09:19:36 6 1 c#/ package/ nuget/ nuget-package

There's a function that is called from a NuGet package when the program starts up, and if I start the program in debug or release build in VS 2017 it works just fine, no issues - this has been tried on multiple machines. 程序启动时有一个从NuGet包中调用的函数，如果我以VS 2017的调试版本或发布版本启动该程序，它就可以正常工作，没有问题-已在多台计算机上进行了尝试。

If we queue it for a release build on our build server and launch the program it builds on one of the PCs where it worked (or any other PC) we get the following error: 如果我们将其排队等待在构建服务器上进行发布，并在可以运行的其中一台PC（或任何其他PC）上启动其构建的程序，则会出现以下错误：

It's possible that the NuGet on the build server is pulling the wrong version of the package that's causing the error, but I've cleared the NuGet cache and I still get the same issue (Although there is an extra NuGet install on the PC which I can't clear or update). 生成服务器上的NuGet可能拉出了导致错误的软件包的错误版本，但是我已经清除了NuGet缓存，但仍然遇到相同的问题（尽管我在PC上额外安装了NuGet无法清除或更新）。

This build server has been creating release builds for years, it has only started to happen recently, and with this specific branch of code. 这个构建服务器已经创建发布构建已有多年了，它直到最近才开始使用此特定的代码分支。

Any thoughts on what could/might cause a package issue on a release build on a build server would be appreciated. 对于在构建服务器上的发行版本上可能/可能导致软件包问题的任何想法，我们将不胜感激。

1 个解决方案

Turned out to be an issue with some DLL's in the source which were out of date and only got copied over in the build server itself. 原来是源中某些DLL已过期且仅在构建服务器本身中被复制的DLL的问题。 Nothing to do with NuGet or C#. 与NuGet或C＃无关。

The fault was with the build scripts we created and how the build server builds release builds differently. 问题在于我们创建的构建脚本，以及构建服务器构建发行版的方式不同。