-
Notifications
You must be signed in to change notification settings - Fork 525
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 update breaks VFPT solution #316
Comments
ok will check |
found it. We now create the framework assembly references directly with Paket. Since you still have "custom" framework references Paket refuses to override these. You need to try really really So please do the following:
|
What do custom framework references mean? In any case, I would appreciate some error messages from Paket that points me to a right direction. |
It's not really an error. Paket just assumes you have manually installed that package and skips the install. It already traced that information in verbose mode. I changed this and now you get a warning when paket skips the install. |
It doesn't seem to work using these exact steps you mentioned. Could you take a look? |
sure. will send PR |
seems the install --hard work, but something changed after update. Investigating... |
looks like FsXaml.Wpf update to 0.9.9 is breaking |
/cc @ ReedCopsey |
forki/FSharpVSPowerTools@d20d966 worked locally - why is it failing on appveyor? |
I ran
on VFPT solution and the solution no longer compiles.
Particularly,
FsXaml.Wpf
references have been removed fromFSharpVSPowerTools.Logic
project https://github.com/fsprojects/VisualFSharpPowerTools/blob/master/src/FSharpVSPowerTools.Logic/FSharpVSPowerTools.Logic.fsproj. It doesn't change anything if I do selective update (not changingFsXaml.Wpf
version).I start seeing this issue from version 0.9.x.
The text was updated successfully, but these errors were encountered: