{"action":"created","issue":{"url":"https://api.github.com/repos/themotleyfool/Klondike/issues/73","labels_url":"https://api.github.com/repos/themotleyfool/Klondike/issues/73/labels{/name}","comments_url":"https://api.github.com/repos/themotleyfool/Klondike/issues/73/comments","events_url":"https://api.github.com/repos/themotleyfool/Klondike/issues/73/events","html_url":"https://github.com/themotleyfool/Klondike/issues/73","id":58740727,"number":73,"title":"Packages which contain the work Crypto are unable to be found via VS Package Manager","user":{"login":"smadam813","id":4027686,"avatar_url":"https://avatars.githubusercontent.com/u/4027686?v=3","gravatar_id":"","url":"https://api.github.com/users/smadam813","html_url":"https://github.com/smadam813","followers_url":"https://api.github.com/users/smadam813/followers","following_url":"https://api.github.com/users/smadam813/following{/other_user}","gists_url":"https://api.github.com/users/smadam813/gists{/gist_id}","starred_url":"https://api.github.com/users/smadam813/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smadam813/subscriptions","organizations_url":"https://api.github.com/users/smadam813/orgs","repos_url":"https://api.github.com/users/smadam813/repos","events_url":"https://api.github.com/users/smadam813/events{/privacy}","received_events_url":"https://api.github.com/users/smadam813/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-02-24T13:52:40Z","updated_at":"2015-02-28T15:32:46Z","closed_at":null,"body":"We have two packages in our repository that are unable to be searched for using the VS Package Manager after upgrading to Build 82.  Their names are \"Company.Libraries.Crypto\" and \"Company.Libraries.Crypto.Api\".  I have not been able to identify any other naming schemes that create this issue so I am wondering if Crypto is a reserved word.  The package search within Klondike's web interface works 100% even with the packages listed above."},"comment":{"url":"https://api.github.com/repos/themotleyfool/Klondike/issues/comments/76530546","html_url":"https://github.com/themotleyfool/Klondike/issues/73#issuecomment-76530546","issue_url":"https://api.github.com/repos/themotleyfool/Klondike/issues/73","id":76530546,"user":{"login":"chriseldredge","id":826092,"avatar_url":"https://avatars.githubusercontent.com/u/826092?v=3","gravatar_id":"","url":"https://api.github.com/users/chriseldredge","html_url":"https://github.com/chriseldredge","followers_url":"https://api.github.com/users/chriseldredge/followers","following_url":"https://api.github.com/users/chriseldredge/following{/other_user}","gists_url":"https://api.github.com/users/chriseldredge/gists{/gist_id}","starred_url":"https://api.github.com/users/chriseldredge/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chriseldredge/subscriptions","organizations_url":"https://api.github.com/users/chriseldredge/orgs","repos_url":"https://api.github.com/users/chriseldredge/repos","events_url":"https://api.github.com/users/chriseldredge/events{/privacy}","received_events_url":"https://api.github.com/users/chriseldredge/received_events","type":"User","site_admin":false},"created_at":"2015-02-28T15:32:46Z","updated_at":"2015-02-28T15:32:46Z","body":"Sounds like it. So the package targets .NET 4.0 Client Profile and it isn't showing up for a project that targets .NET 4.0 (Standard).\r\n\r\nI'll make a test case for this and verify.\r\n\r\nIncidentally, the logic for which framework versions are compatible with other framework versions is not something built into NuGet.Core.dll, or anywhere else I've found that Klondike could reuse. I've had to reimplement this logic to the best of my ability. The logic is brittle and prone to need touching up every time a new framework is introduced."}}