Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add support package with version containing a wildcard (i.e. 3.*)
See original GitHub issueFor the moment, the tool fails with the error:
Analysing project MyProject...
Building MyProject (net471)...
Error: Version '3.*' is not valid. (Parameter 'version')
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Nuget install package with wildcard version
Unfortunately install-package command does not support a wild card version. But if you have a .NET Core based project then you can use...
Read more >Nuget pack handles nuspec files containing wildcards wrong
In the nuspec file there is a dependency to another nuget-package whith a specified version as 1.0.* (included below).
Read more >JQL - Add wildcard functionality to versions
Excellent idea. I'd like to use version wildcards in JQL. Otherwise it makes it difficult to maintain a single filter to display on...
Read more >NuGet Package Version Reference
Exact details on specifying version numbers and ranges for other packages upon which a NuGet package depends, and how dependencies are ...
Read more >Supporting Wildcard Characters in Cmdlet Parameters
The following command shows how a wildcard character is used to return all the cmdlets in the current session whose name contains the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This one is hitting me at the moment, do you want me to have a look at doing a PR for you @patriksvensson
Hello I’m still getting the error from the last version or source code ‘Could not find color or style ‘2.4.1,3.0.0)[/’.’ reason contains [grey]Might be updated from[/] [silver][2.4.1,3.0.0)[/] [grey]in[/] [aqua]Aston.Testing[/]
i’m using : <XunitVersion>[2.4.1,3.0.0)</XunitVersion> in a props file and the project contains
<PackageReference Include="xunit" Version="$(XunitVersion)" />