Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ExcludeVersion Setting for nuget.config #5487

Open
AlaricDelany opened this issue Jun 26, 2017 · 0 comments
Open

ExcludeVersion Setting for nuget.config #5487

AlaricDelany opened this issue Jun 26, 2017 · 0 comments
Labels
Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Status:Excluded from icebox cleanup Status:Inactive Icebox issues not updated for a specific long time Style:Packages.Config Type:Feature
Milestone

Comments

@AlaricDelany
Copy link

Hallo out there,
I have a Problem regarding to the way Pathes are Build by nuget.
In my current Project we use Fake Scripts for Building, Testing and Package.
My Problem is, the Version Number in the Path, because we need to Reference the (not working #1521) Solution Level Packages like Fake itself from the Fake (F#) Scripts, this looked like this:
#r @"packages\FAKE\tools\FakeLib.dll"

But with a Hard Coded Version Number at the Path we are be Forced to do something like this:
#r @"packages\FAKE\4.61.3\tools\FakeLib.dll"
And Every time someone updates one of these Packages we had to manually update every Script which uses one of these Solution Level Packages.

Offcause we could pass at every Place where we Restore a "-ExcludeVersion" Parameter but even than the Visual Studio would not do it, because (as far as i know) there is no way to pass Additional Parameters and if Possible it would be a Configuration which we had to do at every Developer PC and are again screwed up on the Build Server.

My Question/Request would be, why not adding it to the "nuget.config", there is allready a "packageRestore" Section and just adding it like this:
<add key="excludeVersion" value="True" />
And the Tooling arround (VS, CLI) should understand it, there would be no need to pass it all the Time, in my Mind it is a General/Global Setting and should be configureable like such one.

We Use Visual Studio 2017 and trying to use the build in Package Manager UI.

I hope my Point is clear and maybe there is allready such a Flag but at least i could not find it.

Best Regards
AlaricDelany

@mishra14 mishra14 added the Priority:2 Issues for the current backlog. label Dec 20, 2017
@mishra14 mishra14 added this to the Backlog milestone Dec 20, 2017
@ghost ghost added the Status:Inactive Icebox issues not updated for a specific long time label Sep 1, 2022
@nkolev92 nkolev92 added Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. and removed Priority:2 Issues for the current backlog. labels Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:3 Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog. Status:Excluded from icebox cleanup Status:Inactive Icebox issues not updated for a specific long time Style:Packages.Config Type:Feature
Projects
None yet
Development

No branches or pull requests

6 participants