-
Notifications
You must be signed in to change notification settings - Fork 585
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
Paket question for Fake.Deploy.Web #755
Comments
like #756? |
Did you update the lock file manually? I did try updating paket.dependencies and adding exactly that line, but further up the file. Kept bringing down 3.2.3. |
I added it to my paket backlog as an issue to invest. I used |
should I merge #756? |
Looks like it also needs microsoft.aspnet.webpages.2.0.30506 . Adding that in would make it bin-deployable (without any GAC support). |
Also...we can remove System.Web.Razor.Unofficial from all references...it was mainly a legal issue which no longer is an issue. |
better? 2015-04-14 17:30 GMT+02:00 Ashic Mahtab [email protected]:
|
Yup...looks nice. Need to up my paket-fu :) |
Bin deploy works :) |
regarding the paket issue: I think it's the same issue as fsprojects/Paket#777 and fixed in 0.41.3 any chance you could retry to confirm? |
Will try tomorrow and let you know. |
Currently Fake.Deploy.Web needs razor v2 binaries (either gac-ed or in bin). Paket brings down v3 of razor which nothing else is expecting. Is there a way to force the usage of v2? Basically, we need to ensure that http://www.nuget.org/packages/Microsoft.AspNet.Razor/2.0.30506 is used. Currently, the latest stable is put into packages: http://www.nuget.org/packages/Microsoft.AspNet.Razor/3.2.3/. The latter pretty much requires MVC5 and .NET 4.5, whereas the former doesn't. I've tried adding the following to paket.dependencies:
nuget Microsoft.AspNet.Razor 2.0.30506
but it doesn't seem to have any effect. Running ..paket\pakete.exe install simply brings down the latest stable version. I'm not overly familiar with paket. Would appreciate it if somebody could point me in the right direction.
The text was updated successfully, but these errors were encountered: