We won't run ps1 file - document this in FAQ

[forki]

No description provided.

[sergey-tihon]

What is the reason for this? Some problems with Mono?
I believe that some packages really require this... I thing that will be better to have this feature optional and turned off by default. No?

[agross]

#65 (comment)

[forki]

these are the reasons:

1. we don't believe scripts should be used at all (so conceptually it's
   not the way we want to go in paket)
2. even for backwards compatibility it's very very hard to get that
   working and even nuget can't do it right.
3. it doesn't work on mono

2014-09-15 9:35 GMT+02:00 Sergey Tihon [email protected]:

What is the reason for this? Some problems with Mono?
I believe that some packages really require this... I thing that will be
better to have this feature optional and turned off by default. No?

—
Reply to this email directly or view it on GitHub
#100 (comment).

[forki]

It was a very very bad idea to introduce powershell into nuget and IIRC they did it in the beginning to support unrelated things like scaffolding for ASP.NET.

[ilkerde]

@forki Can we please extend this statement to we won't run any script/program?

[bartelink]

@forki @sergey-tihon See #101 generally one can re-express such stuff in a far more resilient manner using .props and .targets files. In my closed source production experience, .ps1 files get refactored into those to workaround the fundamental brittleness of the .ps1 concept.

Not a surprise as declarative is better than imperative and there's no testing story of consequence for the .ps1 madness