Force evaluate floating version packages with lock file via MsBuild / csproj
up vote
0
down vote
favorite
I want to use the Locking dependencies of Nuget (>= 4.9), so I can have automatic package update during dev phase and fixed version during release build.
I enabled the lock file mode, so I now have a packages.lock.json file.
The problem is that when I have floating version of package references in the project file like:
<PackageReference Include="My.Nuget.Package" Version="1.0.*" />
The restore package via Visual Studio Build does not update to new packages version anymore. This behavior appeared after I activated the lock file.
The Microsoft documentation describes the --force-evaluate option with dotnet.exe, that works well but I want to do this directly with an MsBuild option in the csproj.
By checking the NuGet Client code, it seems that a RestoreForceEvaluate option exists in Msbuild NuGet.targets but I have no idea how to use it.
c# visual-studio msbuild nuget
asked Nov 21 at 8:37
maxence51
1791111
add a comment |
up vote
0
down vote
favorite
I want to use the Locking dependencies of Nuget (>= 4.9), so I can have automatic package update during dev phase and fixed version during release build.
I enabled the lock file mode, so I now have a packages.lock.json file.
The problem is that when I have floating version of package references in the project file like:
<PackageReference Include="My.Nuget.Package" Version="1.0.*" />
The restore package via Visual Studio Build does not update to new packages version anymore. This behavior appeared after I activated the lock file.
The Microsoft documentation describes the --force-evaluate option with dotnet.exe, that works well but I want to do this directly with an MsBuild option in the csproj.
By checking the NuGet Client code, it seems that a RestoreForceEvaluate option exists in Msbuild NuGet.targets but I have no idea how to use it.
c# visual-studio msbuild nuget
asked Nov 21 at 8:37
maxence51
1791111
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want to use the Locking dependencies of Nuget (>= 4.9), so I can have automatic package update during dev phase and fixed version during release build.
I enabled the lock file mode, so I now have a packages.lock.json file.
The problem is that when I have floating version of package references in the project file like:
<PackageReference Include="My.Nuget.Package" Version="1.0.*" />
The restore package via Visual Studio Build does not update to new packages version anymore. This behavior appeared after I activated the lock file.
The Microsoft documentation describes the --force-evaluate option with dotnet.exe, that works well but I want to do this directly with an MsBuild option in the csproj.
By checking the NuGet Client code, it seems that a RestoreForceEvaluate option exists in Msbuild NuGet.targets but I have no idea how to use it.
c# visual-studio msbuild nuget
asked Nov 21 at 8:37
maxence51
1791111
I want to use the Locking dependencies of Nuget (>= 4.9), so I can have automatic package update during dev phase and fixed version during release build.
I enabled the lock file mode, so I now have a packages.lock.json file.
The problem is that when I have floating version of package references in the project file like:
<PackageReference Include="My.Nuget.Package" Version="1.0.*" />
The restore package via Visual Studio Build does not update to new packages version anymore. This behavior appeared after I activated the lock file.
The Microsoft documentation describes the --force-evaluate option with dotnet.exe, that works well but I want to do this directly with an MsBuild option in the csproj.
By checking the NuGet Client code, it seems that a RestoreForceEvaluate option exists in Msbuild NuGet.targets but I have no idea how to use it.
c# visual-studio msbuild nuget
c# visual-studio msbuild nuget
asked Nov 21 at 8:37
maxence51
1791111
asked Nov 21 at 8:37
maxence51
1791111
asked Nov 21 at 8:37
maxence51
1791111
asked Nov 21 at 8:37
maxence51
1791111
asked Nov 21 at 8:37
maxence51
1791111
1791111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
By checking the NuGet Client code, it seems that a RestoreForceEvaluate option exists in Msbuild NuGet.targets but I have no idea how to use it.
I am afraid we could not do that at this moment. According to the nuget wiki,
Enable repeatable package restore using lock file:
There is no such MSBuild equivalent option for option --force-evaluate, so we could not use --force-evaluate directly with an MsBuild option in the csproj.
Hope this helps.
answered Nov 21 at 9:54
Leo Liu-MSFT
16.8k21731
1
Thanks, but where is Re-evaluate and Restore?
– maxence51
Nov 21 at 12:27
@maxence51, This is a preparing feature. It will appear on a later version. I am sorry that I mentioned it too early, I have updated the answer. I hope this does not bring you too much trouble.
– Leo Liu-MSFT
Nov 22 at 1:31
1
Ok thank you Leo, I will deal with the CLI until this will appears in Visual Studio.
– maxence51
Nov 22 at 7:38
@maxence51, You are always welcome! :)
– Leo Liu-MSFT
Nov 22 at 7:39
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
By checking the NuGet Client code, it seems that a RestoreForceEvaluate option exists in Msbuild NuGet.targets but I have no idea how to use it.
I am afraid we could not do that at this moment. According to the nuget wiki,
Enable repeatable package restore using lock file:
There is no such MSBuild equivalent option for option --force-evaluate, so we could not use --force-evaluate directly with an MsBuild option in the csproj.
Hope this helps.
answered Nov 21 at 9:54
Leo Liu-MSFT
16.8k21731
1
Thanks, but where is Re-evaluate and Restore?
– maxence51
Nov 21 at 12:27
@maxence51, This is a preparing feature. It will appear on a later version. I am sorry that I mentioned it too early, I have updated the answer. I hope this does not bring you too much trouble.
– Leo Liu-MSFT
Nov 22 at 1:31
1
Ok thank you Leo, I will deal with the CLI until this will appears in Visual Studio.
– maxence51
Nov 22 at 7:38
@maxence51, You are always welcome! :)
– Leo Liu-MSFT
Nov 22 at 7:39
add a comment |
up vote
1
down vote
accepted
By checking the NuGet Client code, it seems that a RestoreForceEvaluate option exists in Msbuild NuGet.targets but I have no idea how to use it.
I am afraid we could not do that at this moment. According to the nuget wiki,
Enable repeatable package restore using lock file:
There is no such MSBuild equivalent option for option --force-evaluate, so we could not use --force-evaluate directly with an MsBuild option in the csproj.
Hope this helps.
answered Nov 21 at 9:54
Leo Liu-MSFT
16.8k21731
1
Thanks, but where is Re-evaluate and Restore?
– maxence51
Nov 21 at 12:27
@maxence51, This is a preparing feature. It will appear on a later version. I am sorry that I mentioned it too early, I have updated the answer. I hope this does not bring you too much trouble.
– Leo Liu-MSFT
Nov 22 at 1:31
1
Ok thank you Leo, I will deal with the CLI until this will appears in Visual Studio.
– maxence51
Nov 22 at 7:38
@maxence51, You are always welcome! :)
– Leo Liu-MSFT
Nov 22 at 7:39
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
By checking the NuGet Client code, it seems that a RestoreForceEvaluate option exists in Msbuild NuGet.targets but I have no idea how to use it.
I am afraid we could not do that at this moment. According to the nuget wiki,
Enable repeatable package restore using lock file:
There is no such MSBuild equivalent option for option --force-evaluate, so we could not use --force-evaluate directly with an MsBuild option in the csproj.
Hope this helps.
answered Nov 21 at 9:54
Leo Liu-MSFT
16.8k21731
By checking the NuGet Client code, it seems that a RestoreForceEvaluate option exists in Msbuild NuGet.targets but I have no idea how to use it.
I am afraid we could not do that at this moment. According to the nuget wiki,
Enable repeatable package restore using lock file:
There is no such MSBuild equivalent option for option --force-evaluate, so we could not use --force-evaluate directly with an MsBuild option in the csproj.
Hope this helps.
answered Nov 21 at 9:54
Leo Liu-MSFT
16.8k21731
edited Nov 22 at 1:25
answered Nov 21 at 9:54
Leo Liu-MSFT
16.8k21731
answered Nov 21 at 9:54
Leo Liu-MSFT
16.8k21731
answered Nov 21 at 9:54
Leo Liu-MSFT
16.8k21731
16.8k21731
1
Thanks, but where is Re-evaluate and Restore?
– maxence51
Nov 21 at 12:27
@maxence51, This is a preparing feature. It will appear on a later version. I am sorry that I mentioned it too early, I have updated the answer. I hope this does not bring you too much trouble.
– Leo Liu-MSFT
Nov 22 at 1:31
1
Ok thank you Leo, I will deal with the CLI until this will appears in Visual Studio.
– maxence51
Nov 22 at 7:38
@maxence51, You are always welcome! :)
– Leo Liu-MSFT
Nov 22 at 7:39
add a comment |
1
Thanks, but where is Re-evaluate and Restore?
– maxence51
Nov 21 at 12:27
@maxence51, This is a preparing feature. It will appear on a later version. I am sorry that I mentioned it too early, I have updated the answer. I hope this does not bring you too much trouble.
– Leo Liu-MSFT
Nov 22 at 1:31
1
Ok thank you Leo, I will deal with the CLI until this will appears in Visual Studio.
– maxence51
Nov 22 at 7:38
@maxence51, You are always welcome! :)
– Leo Liu-MSFT
Nov 22 at 7:39
1
1
Thanks, but where is Re-evaluate and Restore?
– maxence51
Nov 21 at 12:27
Thanks, but where is Re-evaluate and Restore?
– maxence51
Nov 21 at 12:27
@maxence51, This is a preparing feature. It will appear on a later version. I am sorry that I mentioned it too early, I have updated the answer. I hope this does not bring you too much trouble.
– Leo Liu-MSFT
Nov 22 at 1:31
@maxence51, This is a preparing feature. It will appear on a later version. I am sorry that I mentioned it too early, I have updated the answer. I hope this does not bring you too much trouble.
– Leo Liu-MSFT
Nov 22 at 1:31
1
1
Ok thank you Leo, I will deal with the CLI until this will appears in Visual Studio.
– maxence51
Nov 22 at 7:38
Ok thank you Leo, I will deal with the CLI until this will appears in Visual Studio.
– maxence51
Nov 22 at 7:38
@maxence51, You are always welcome! :)
– Leo Liu-MSFT
Nov 22 at 7:39
@maxence51, You are always welcome! :)
– Leo Liu-MSFT
Nov 22 at 7:39
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53408075%2fforce-evaluate-floating-version-packages-with-lock-file-via-msbuild-csproj%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
