Closed luisrudge closed 10 years ago
Interesting.. I've had a similar behavior with the packages.config existing before but not the packages.
That stack trace indicates its using the built-in ScriptCs.AssemblyResolver instead of ScriptCs.PvcAssemblyResolver.. what version is your PVC CLI (I really need to add a pvc version cmd)?
Check in:
C:\Chocolatey\bin\pvc.bat
I have a repro for this. Thanks for the report!
Just to confirm:
C:\Chocolatey\bin\pvc.bat
@echo off
SET DIR=%~dp0%
cmd /c "%DIR%..\lib\pvc.0.0.2.2\tools\pvc.exe %*"
exit /b %ERRORLEVEL%
The base ScriptCs resolvers were still being used during initialization so it was loading stuff that PVC just doesn't care about. Fixed! :+1:
When i try to install a plugin inside a solution folder that has a packages folder, it crashes (but still creates the pvc-packages folder).
First, on an empty folder:
Now, on a solution folder
Finally, if i remove the 'packages' folder, it runs ok again: