Closed gerritmulder closed 5 years ago
eXpand.lab release 19.1.502.4 includes commit that relate to this task:
Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
Thanks a lot for your contribution.
eXpand.lab release 19.1.502.7 includes commit that relate to this task:
Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
Thanks a lot for your contribution.
eXpand.lab release 19.1.502.8 includes commit that relate to this task:
Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
Thanks a lot for your contribution.
Description We have a Utils project which only references eXpandLib and doesn't reference any DevExpress references, because we only use Xpand.Utils for this project. This fails since 19.1.501, because the ModelMapper is added to eXpandLib, which added the VersionConverter too. The VersionConverter doesn't recognize the DevExpress version for projects that do not have DevExpress references and throws the exception
Exception calling "Match" with "3" argument(s): "Value can not be null"
Solution The solution would be to change the script or release the Utils project as a NuGet package.
Work-around Add the
<DevExpressVersion>
element to the PropertyGroup in your .csprojAdditional information Problem where this occurs, the $include variable is null because the
$packageReference
and the$dxReferences
variables are both null. https://github.com/eXpandFramework/DevExpress.XAF/blob/319d672212f8f8f8c2524bc4046ef1a72bf08f40/tools/Xpand.VersionConverter/Functions.ps1#L220-L221.csproj