Hey there! I have a question. My project has an import in the .csproj that looks like this:
But when running "nukeeper repo", the underlying msbuild must not have the SolutionDir variable set since it resolves the above path to "C:\MyProject" which is not correct. Is there a way to pass parameters to the underlying msbuild that gets run during "nukeeper repo"? Setting the parameter in the Directory.Build.props is not an option as we don't want to hard code that value in our codebase.
repothe problem is
the correct version of msbuild gets selected
MSBuild auto-detection: using msbuild version '188.8.131.52601' from 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin'.
Actually: Microsoft states:
The nuget.exe CLI is for your .NET Framework project and non-SDK-style projects (for example, a non-SDK style project that targets .NET Standard libraries). If you are using a non-SDK-style project that has been migrated to PackageReference, use the dotnet CLI instead. The nuget.exe CLI requires a packages.config file for package references.
Manage packages using the nuget.exe CLI
So it is all about having a packages.config file or not.
i've got a nuget credentials provider error lately when trying to use nukeeper. how do get around this?
The plugin credential provider could not acquire credentials. Authentication may require manual action. Consider re-running the command with --interactive for
dotnet, /p:NuGetInteractive="true" for MSBuild or removing the -NonInteractive switch for
i'm simply not understanding how to resolve this from a nukeeper perspective