Skip to content

Commit

Permalink
We won't run ps1 file - more about the technical details - references #…
Browse files Browse the repository at this point in the history 
…100
  • Loading branch information
@forki
forki committed Sep 15, 2014
1 parent da9a30c commit adb2329
Showing 1 changed file with 15 additions and 2 deletions.
17 changes: 15 additions & 2 deletions docs/content/faq.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,22 @@ Paket tries to embrace [SemVer](http://semver.org/) while NuGet uses a pessimist

## Does Paket run install.ps1 scripts?

No we don't run any scripts from NuGet packages and we have no plans to do this in the future.
No, we don't run any script or program from NuGet packages and we have no plans to do this in the future.
We know that this might cause you some manual work for some of the currently available NuGet packages, but we think these install scripts cause more harm than good.
Instead we encourage everybody to use a declarative install process.
In fact our current model doesn't allow to run install.ps1 script like the following from `FontAwesome.4.1.0`:

[lang=batchfile]
param($installPath, $toolsPath, $package, $project)

foreach ($fontFile in $project.ProjectItems.Item("fonts").ProjectItems)
{
$fontFile.Properties.Item("BuildAction").Value = 2;
}

The reason is simply that even if we would support Powershell on Windows we can't access the Visual Studio project system. Paket is a command line tool and doesn't run inside of Visual Studio.
There is no way to make this work - and even NuGet.exe can't do it in command line mode.

Instead we encourage the .NET community to use a declarative install process and we will help to fix this in the affected packages.

## When I resolve the dependencies from NuGet.org it is really slow. Why is that?

Expand Down

1 comment on commit adb2329

@bartelink
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@forki

Paket is a command line tool and doesn't run inside of Visual Studio.

Doesn't wire into Visual Studio (pointless and all as it might be, don't want to trigger thoughts that it's impossible to run paket.exe from e.g. Package Manager Console)

and even NuGet.exe can't do it in command line mode.

And NuGet.exe install doesn't (and can't and won't) attempt to do so in command line mode.

Please sign in to comment.