-
Notifications
You must be signed in to change notification settings - Fork 674
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
Frameworks within the portable profile are not allowed to have profiles themselves #165
Conversation
@@ -497,5 +497,20 @@ public void PackageReader_SupportedFrameworks() | |||
} | |||
} | |||
} | |||
|
|||
[Fact] | |||
public void PackageReader_SupportedFrameworksForInvalidPortableFrameworkThrows() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In theory this test is not required, but since NuGet/Home#1869 mentions a broken package this test was added to test front to back.
looks good to me. @emgarten what do you think? |
Looks good |
So I can just merge? |
Is this change in? |
No, was waiting for a "yes please merge" :-) |
It looks good to me. //cc @yishaigalatzer |
Let's get this merged in |
Fixes NuGet/Home#1869
Note that current 3.3 does not throw when such invalid framework is encountered. Instead, it parses the framework into:
.NETPortable,Version=v0.0,Profile=net+win+wpa+wp+sl+net-cf+netmf+MonoAndroid+MonoTouch+Xamarin.iOS
This PR changes the behaviour and will throw
FrameworkException
in these cases.