-
-
Notifications
You must be signed in to change notification settings - Fork 478
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
Profile 259 Compatibility? #78
Comments
Hi @adamhill , Thank you for bringing the issue to attention. 😎 You're right. Bogus is not compatible with Xamarin at the moment. I think I tried Xamarin some time ago and ran into the same issue with as you've described above. I've just been too lazy to fix the problem because it's not an immediate need of mine in my current projects. I suspect the crux of the issue is we're missing an explicit build target for There are a few ways we can proceed to get this resolved:
Some helpful guidelines on modifying Bogus' source:
Please let me know how you'd like to proceed. Also, just as a heads-up (no offense) I'll be closing this issue if we don't have a path forward because I'm OCD w.r.t unresolved-open issues in GitHub that might linger on for years. IMHO, GitHub issues are like trying to get to Inbox 📭 zero! Hehe. Thanks, |
Hey @adamhill , FYI. Latest release v17 (compiled against .NET Standard 2.0) appears to run on Xamarin Mobile now: Here's how I got it working:
Here's a screenshot and XAML samples that I used to get it working:
|
Is there any version of Bogus that is compatible with PCL Profile 259 in Xamarin? I tried all the way up to 7.1.2, which is the one just before .NET Core support was official. I always get:
Could not install package 'Bogus 7.1.3'. You are trying to install this package into a project that targets '.NETPortable,Version=v4.5,Profile=Profile259'
when I try to add the the Nuget package.
Even though the Dependency is .NET 4.0 and 259 is Version=4.5 shouldn't I be able to add it? I thought dependencies were always >= <X.X>
Thanks.
The text was updated successfully, but these errors were encountered: