Git Product home page Git Product logo

fixnugetpackagepaths's Introduction

FixNuGetPackagePath

Visual Studio extension (.vsix) to make sure that paths to NuGet packages are relative to the directory of the current solution.

When installing a NuGet package the paths to the package files (i.e. *.dll, *.targets, ...) are set relative to the solution that is open at the time the package is installed. This extension ensures that the paths are always relative to the solution that is currently open. That only really makes a difference if you have a project that is referenced from different solutions and those solutions live in different directories (e.g. when using git submodules).

For some discussion on this see NuGet/Home#738

Usage:

Fix NuGet paths in existing projects:

  • Open all solutions in Visual Studio
  • Select Tools -> Fix NuGet hint paths

When installing a new NuGet package the paths are fixed automatically.

fixnugetpackagepaths's People

Contributors

jkronberger avatar johannesegger avatar rowandish avatar

Stargazers

avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar

Forkers

johannesegger rowandish agnerbo frasten

fixnugetpackagepaths's Issues

Possible performance issue

When I update a single nuget package. ie: devDept.Eyeshot I see the following in the output window

[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCad.Plugin.GearCorrection ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCad.Plugin.GearCorrection.Spec ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCad.Plugin.FlankEvaluation ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCad.Plugin.MoineauPointList.Spec ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCad.Plugin.Peeling.Specs ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCad.Plugin.PointListValidation ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCad.Plugin.BasicFolders.Spec ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCad.Plugin.ExtruderMill ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCad.DataMigration.Spec ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project Weingartner.Wpf.Common ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project Weingartner.Wpf.Animation ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project Weingartner.DotLiquidExtensions.Spec ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project Weingartner.DotLiquidExtensions ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project QuickGraph ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project LaserHelpers ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project KeyenceCom ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project LaserHelpers.Spec ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCadOldImport ======
[Info] Fixed 0 paths.
[Info] ===== Fix paths for NuGet package devDept.Eyeshot in project WeinCadOldImport.Spec ======
[Info] Fixed 0 paths.

Which goes on for thousands of lines. This is a huge amout of output considering that it should really only be run once. Looks like it's responding immediately to every change nuget makes. I'm not sure if this is impacting the overall shitty amount of time that nuget takes to upgrade a package but making it even a bit worse certainly doesn't make it better.

ServiceFabric sfproj files

The Azure ServiceFabric project files (.sfproj) have the "......\packages" issue in at least 4 places and would benefit being fixed with the $(SolutionDir)packages.

Fix paths to analysers 

<ItemGroup>
    <Analyzer Include="..\packages\MyPackage.1.2.3\analyzers\dotnet\cs\MyAnalyser1.dll" />
    <Analyzer Include="..\packages\MyPackage.1.2.3\analyzers\dotnet\cs\MyAnalyser2.dll" />
</ItemGroup>

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.