File tree Expand file tree Collapse file tree 5 files changed +50
-13
lines changed Expand file tree Collapse file tree 5 files changed +50
-13
lines changed Original file line number Diff line number Diff line change @@ -207,8 +207,16 @@ Accept wildcard characters: False
207
207
` ` `
208
208
209
209
### -Version
210
- Specifies the version of the resource to be returned.
211
- Expected version/version range format is documented here: https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#version-ranges
210
+ Specifies the version of the resource to be returned. The value can be an exact version or a version
211
+ range using the NuGet versioning syntax.
212
+
213
+ For more information about NuGet version ranges, see [Package versioning](/nuget/concepts/package-versioning#version-ranges)
214
+
215
+ PowerShellGet supports all but the _minimum inclusive version_ listed in the NuGet version range
216
+ documentation. So inputting "1.0.0.0" as the version doesn't yield versions 1.0.0.0 and higher
217
+ (minimum inclusive range). Instead, the values is considered as the required version and yields
218
+ version 1.0.0.0 only (required version). To use the minimum inclusive range, provide ` [1.0.0.0, ]` as
219
+ the version range.
212
220
213
221
` ` ` yaml
214
222
Type: System.String
Original file line number Diff line number Diff line change @@ -89,9 +89,16 @@ Accept wildcard characters: False
89
89
` ` `
90
90
91
91
### -Version
92
- Specifies the version of the resource to be returned.
93
- Can be an exact version or a version range, using the NuGet versioning syntax.
94
- Expected version/version range format is documented here: https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#version-ranges
92
+ Specifies the version of the resource to be returned. The value can be an exact version or a version
93
+ range using the NuGet versioning syntax.
94
+
95
+ For more information about NuGet version ranges, see [Package versioning](/nuget/concepts/package-versioning#version-ranges)
96
+
97
+ PowerShellGet supports all but the _minimum inclusive version_ listed in the NuGet version range
98
+ documentation. So inputting "1.0.0.0" as the version doesn't yield versions 1.0.0.0 and higher
99
+ (minimum inclusive range). Instead, the values is considered as the required version and yields
100
+ version 1.0.0.0 only (required version). To use the minimum inclusive range, provide ` [1.0.0.0, ]` as
101
+ the version range.
95
102
96
103
` ` ` yaml
97
104
Type: System.String
Original file line number Diff line number Diff line change @@ -72,9 +72,16 @@ Accept wildcard characters: False
72
72
` ` `
73
73
74
74
### -Version
75
- Specifies the version of the resource to be installed.
76
- Can be an exact version or a version range, using the NuGet versioning syntax.
77
- Expected version/version range format is documented here: https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#version-ranges
75
+ Specifies the version of the resource to be installed. The value can be an exact version or a version
76
+ range using the NuGet versioning syntax.
77
+
78
+ For more information about NuGet version ranges, see [Package versioning](/nuget/concepts/package-versioning#version-ranges)
79
+
80
+ PowerShellGet supports all but the _minimum inclusive version_ listed in the NuGet version range
81
+ documentation. So inputting "1.0.0.0" as the version doesn't yield versions 1.0.0.0 and higher
82
+ (minimum inclusive range). Instead, the values is considered as the required version and yields
83
+ version 1.0.0.0 only (required version). To use the minimum inclusive range, provide ` [1.0.0.0, ]` as
84
+ the version range.
78
85
79
86
` ` ` yaml
80
87
Type: System.String
Original file line number Diff line number Diff line change @@ -66,9 +66,16 @@ Accept wildcard characters: False
66
66
` ` `
67
67
68
68
### -Version
69
- Specifies the version of the resource to be saved.
70
- Can be an exact version or a version range, using the NuGet versioning syntax.
71
- Expected version/version range format is documented here: https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#version-ranges
69
+ Specifies the version of the resource to be saved. The value can be an exact version or a version
70
+ range using the NuGet versioning syntax.
71
+
72
+ For more information about NuGet version ranges, see [Package versioning](/nuget/concepts/package-versioning#version-ranges)
73
+
74
+ PowerShellGet supports all but the _minimum inclusive version_ listed in the NuGet version range
75
+ documentation. So inputting "1.0.0.0" as the version doesn't yield versions 1.0.0.0 and higher
76
+ (minimum inclusive range). Instead, the values is considered as the required version and yields
77
+ version 1.0.0.0 only (required version). To use the minimum inclusive range, provide ` [1.0.0.0, ]` as
78
+ the version range.
72
79
73
80
` ` ` yaml
74
81
Type: System.String
Original file line number Diff line number Diff line change @@ -169,8 +169,16 @@ Accept wildcard characters: False
169
169
` ` `
170
170
171
171
### -Version
172
- Specifies the version the resource is to be updated to.
173
- Expected version/version range format is documented here: https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#version-ranges
172
+ Specifies the version of the resource to be updated to. The value can be an exact version or a version
173
+ range using the NuGet versioning syntax.
174
+
175
+ For more information about NuGet version ranges, see [Package versioning](/nuget/concepts/package-versioning#version-ranges)
176
+
177
+ PowerShellGet supports all but the _minimum inclusive version_ listed in the NuGet version range
178
+ documentation. So inputting "1.0.0.0" as the version doesn't yield versions 1.0.0.0 and higher
179
+ (minimum inclusive range). Instead, the values is considered as the required version and yields
180
+ version 1.0.0.0 only (required version). To use the minimum inclusive range, provide ` [1.0.0.0, ]` as
181
+ the version range.
174
182
175
183
` ` ` yaml
176
184
Type: System.String
You can’t perform that action at this time.
0 commit comments