You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 12, 2024. It is now read-only.
Fail the build if the right nugetizer nuget package cannot be deployed/packaged
This makes far easier to detect cases where the nugetizer package doesn't exist,
and later on template unfolding will fail. It won't happen for CI builds, since
the right builds happen in the right order, but it's quite easy to make this
mistake for developer builds while iterating on the extension.
<DeleteFiles="$(TargetPath)"Condition="'$(_NuGetizerPackageExists)' != 'true' Or '$(_CurrentNuGetizerPackageExists)' != 'true'" />
56
+
57
+
<ErrorCondition="'$(_NuGetizerPackageExists)' != 'true'"Text="NuGetizer nuget package was not found under '$(Out)'.
58
+
Run 'build.cmd' at least once, or run 'msbuild' from the 'src\Build' folder to build the nuget package." />
59
+
60
+
<ErrorCondition="'$(_CurrentNuGetizerPackageExists)' != 'true'"Text="Required NuGetizer nuget package version '$(Version)' was not found under '$(Out)'.
61
+
Run 'build.cmd' at least once, or run 'msbuild' from the 'src\Build' folder to build the nuget package.
62
+
Packages found were: %0a@(_NuGetizerPackage -> ' %(Filename)%(Extension)', '%0a')" />
0 commit comments