-
Notifications
You must be signed in to change notification settings - Fork 520
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
[4.8.6] Too many props are imported #2387
Comments
fixed by fixed by #2388 |
So should we re-enable the net4.6.1 -> netstandard16 compat once we figured this one out? |
|
One I thing I just thought of: Referencing a ns16 lib from full-fx requires that the user also adds a reference to that NETStandard.Library.NETFramework. If he doesn't, it will fail at runtime. Also, that whole stuff is still in preview by microsoft. Aaand paket 5 can't even resolve these preview packages ... So I don't think we should enable it by default. Either disable, or a toggle somewhere. |
Yeah it needs to work is the minimum bar ;) We can warn or fail if we detect that, but let's first fix the current bugs... |
I guess fixed in 4.8.7. Thanks for taking care of this. |
Afaik only props with the exact name packageName.props should be imported. All others should be ignored. Same for targets
The csproj contains the following block:
There are two issues:
The text was updated successfully, but these errors were encountered: