Добрый день, у нас есть чистая версия service 7.18.4 на Centos, которая работает через docker. При первой компиляции уже есть желтые предупреждения, весь лог предупреждений будет ниже. В поддержке ответили что это не влияет на систему, но мы выяснили что все таки влияет. Далее опишу БП в котором это не работает, у нас есть кубик с вопросом пользователю, если добавить только его в систему то все работает и сохраняется. Окей, дальше мы добавляем сценарий у которого есть только return true; и дальше такой процесс не публикуется и выходят те же предупреждения что и при первой компиляции.

Для всех предупреждения

Имя файла: Microsoft.Common.CurrentVersion.targets

Код MSB3277

Строка 2084

Вот описание предупреждений:

Found conflicts between different versions of "System.Resources.ResourceManager" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Collections" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Diagnostics.Debug" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Runtime.Serialization.Xml" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Runtime.Serialization.Primitives" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Linq" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Runtime.Serialization.Json" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Collections.Concurrent" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Threading.Tasks" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Data.Common" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Collections.NonGeneric" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Threading.ThreadPool" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Runtime.InteropServices" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.IO.Compression" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Runtime.Extensions" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Threading" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Text.RegularExpressions" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "netstandard" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Runtime" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.Xml.ReaderWriter" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.IO.FileSystem" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Found conflicts between different versions of "System.ComponentModel" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed.

Помню в сборке 7.17.4 мы отключали предупреждения, чтобы оно нормально компилировалось. После этого процессы публиковались. Вы можете попробовать сохранить процесс без публикации, а потом нажать Компилировать в конфигурации. Может, это поможет. Если нет - то добавление ошибки 2084 в исключения компиляции сборки должно помочь.

Ксензов Егор, добрый день, попробовал первый вариант, не сработало, не подскажете как добавить ошибку в исключения компиляции?

Добрый день, в отчёте ошибок компиляции присутствует скролл, скажите нет ли там ошибок, а не предупреждений?

Дима Вовченко,

проверил ещё раз, только предупреждения с кодом 

MSB3277

Евгений Шевченко,

В таком случае следует проверить логи, возможно там будет записана ошибка. Если даже там ничего нет, то оптимальней всего будет ещё раз обратиться в поддержку с детальным описанием проблемы.

Дима Вовченко,

да обращались,уже месяц общаемся пока толку нет

Насколько понимаю, в MobileKnowledgeBaseFileModelConfig именно так и сделано, два правила по двум константам меняют видимость одного поля:

Terrasoft.sdk.Model.addBusinessRule("KnowledgeBaseFile", {
	ruleType: Terrasoft.RuleTypes.Visibility,
	name: "KnowledgeBaseFileVisibleLinkRule",
	conditionalColumns: [
		{name: "Type", value: Terrasoft.Configuration.FileTypeGUID.Link}
	],
	events: [Terrasoft.BusinessRuleEvents.Load],
	dependentColumnNames: ["Name"]
});
Terrasoft.sdk.Model.addBusinessRule("KnowledgeBaseFile", {
	ruleType: Terrasoft.RuleTypes.Visibility,
	name: "KnowledgeBaseFileVisibleKnowledgeBaseLinkRule",
	conditionalColumns: [
		{name: "Type", value: Terrasoft.Configuration.FileTypeGUID.KnowledgeBaseLink}
	],
	events: [Terrasoft.BusinessRuleEvents.Load],
	dependentColumnNames: ["Name"]
});

Если не хватает возможности стандартных бизнес-правил, можно настроить пользовательское. См. статью, там настраивается валидность значения поля по тройному условию.