Skip to content
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

Label F# PCL projects such that it's obvious which ones support Xamarin #2

Closed
KevinRansom opened this issue Jan 14, 2015 · 2 comments
Closed

Comments

@KevinRansom
Copy link
Member

Some of the F# PCL libraries support profiles 78 and 259 (support for consumption by Xamarin projects) but this isn't obvious when looking at the project descriptions when looking at them in visual studio. Someone developing a platform independent library intending to support Xamarin has no way of knowing these profiles will do what they want. I had to ask in a chat room in order to find out. Some sort of indication that these projects support profiles 78 and 259 would vastly improve discoverability.

comments

KevinRansom wrote Jan 2 at 10:49 AM [x]
I agree we should do something to make this clearer, after all Android and IOS programming are >very important use cases these days. Also the Visual Studio 2015 previews ship with a breadcrumb >to download the Xamarin VS add-in.

What do others think ?

Kevin

latkin wrote Jan 5 at 9:12 AM [x]
I agree it would be helpful to include the profile number in the project description. We could just >>add "(profile 259)" or similar at the end.

mydogisbox wrote Jan 5 at 9:43 AM [x]
Is there some way to make it more obvious than just the profile number? Unless someone is >>>familiar >with the meaning of profile numbers (I'm not), then they're just going to go off of the list >>>of supported >platforms which imply that it won't be consumable by Xamarin projects.

latkin wrote Jan 5 at 10:09 AM [x]
We have no control over how or if Xamarin chooses to use various portable profiles. They might >>>>add/drop/modify support for how these map to iOS or Android. And Xamarin is not, generally >>>>speaking, the only consumer of these libraries. So I think we should just stick to the facts.

mydogisbox wrote Jan 5 at 10:39 AM [x]
Ah, I didn't think of that. I guess that would be on Xamarin's end to publish which profiles they >>>>>support then.

@latkin
Copy link
Contributor

latkin commented Jan 19, 2015

@KevinRansom you have a string change prepped, correct?

@KevinRansom
Copy link
Member Author

it's fixed.with commit e3c08a19

enricosada pushed a commit to enricosada/visualfsharp that referenced this issue May 13, 2015
dsyme pushed a commit that referenced this issue May 26, 2016
Fix bug in error reporting
dsyme referenced this issue in dsyme/fsharp Jun 2, 2016
KevinRansom pushed a commit that referenced this issue Jun 9, 2016
KevinRansom pushed a commit that referenced this issue Jun 25, 2016
Merge branch 'master' into latkin-caller-info-attrs
dsyme added a commit that referenced this issue Jul 23, 2016
more fixes to protofx build
liboz pushed a commit to liboz/visualfsharp that referenced this issue Oct 5, 2016
@dsyme dsyme mentioned this issue Jun 15, 2017
2 tasks
0x53A added a commit to 0x53A/visualfsharp that referenced this issue Mar 18, 2018
KevinRansom pushed a commit that referenced this issue May 25, 2018
* Attempt add match! syntax to parser (as normal match) (does not work)

* Add name for MATCH_BANG token ("keyword 'match!')

* Make match! valid in (and only in) computational expressions

* match! works

* Add match! to xlf localization files

* Add two tests for match!

* Don't use left-pipe

* Give match! keyword a description

* Fix syntax error, and change match! description

* xlf updated

* Add match! keyword description to resx

* Update FSComp.fs

* Write quotation test for match!

* First crack at compile error tests

* Fix baselines

* Fix baseline one more time

* Add vs baseline

* Fix merge mistake

* Fix merge mistake (#2)

* Fix merge mistake in tests
cartermp added a commit to cartermp/fsharp that referenced this issue Jan 7, 2020
# This is the 1st commit message:

ref -> mutable in more places in the compiler

# The commit message dotnet#2 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20191229.1
#
# - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.19629.1

# The commit message dotnet#3 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20191230.1
#
# - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.19630.1

# The commit message dotnet#4 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20191231.1
#
# - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.19631.1

# The commit message dotnet#5 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20200101.1
#
# - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.20051.1

# The commit message dotnet#6 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20191216.5 (dotnet#8079)
#
# - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19616.5

# The commit message dotnet#7 will be skipped:

# dispose fsi at the end of a scripting session (dotnet#8084)
#

# The commit message dotnet#8 will be skipped:

# Added static link tests and extended CompilerAssert (dotnet#8101)
#
# * Changed CompilerAssert to static class. Added Compile/Execute methods that take a Compilation description. Added static link tests
# 
# * Hiding compilation description internals
# 
# * Added another test to check for sanity
# 
# * Making a few optional parameters
# 
# * Hiding internals of CompilationReference

# The commit message dotnet#9 will be skipped:

# Parameterize product version (dotnet#8031)
#
# * Parameterize Product details
# 
# * fcs
# 
# * Repack pkgdef
cartermp added a commit that referenced this issue Jan 7, 2020
…8063)

* # This is a combination of 9 commits.
# This is the 1st commit message:

ref -> mutable in more places in the compiler

# The commit message #2 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20191229.1
#
# - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.19629.1

# The commit message #3 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20191230.1
#
# - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.19630.1

# The commit message #4 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20191231.1
#
# - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.19631.1

# The commit message #5 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20200101.1
#
# - Microsoft.DotNet.Arcade.Sdk - 5.0.0-beta.20051.1

# The commit message #6 will be skipped:

# Update dependencies from https://github.com/dotnet/arcade build 20191216.5 (#8079)
#
# - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19616.5

# The commit message #7 will be skipped:

# dispose fsi at the end of a scripting session (#8084)
#

# The commit message #8 will be skipped:

# Added static link tests and extended CompilerAssert (#8101)
#
# * Changed CompilerAssert to static class. Added Compile/Execute methods that take a Compilation description. Added static link tests
# 
# * Hiding compilation description internals
# 
# * Added another test to check for sanity
# 
# * Making a few optional parameters
# 
# * Hiding internals of CompilationReference

# The commit message #9 will be skipped:

# Parameterize product version (#8031)
#
# * Parameterize Product details
# 
# * fcs
# 
# * Repack pkgdef

* no ilread
nojaf referenced this issue in nojaf/fsharp Jul 28, 2022
kant2002 pushed a commit to kant2002/fsharp that referenced this issue Dec 3, 2022
# Conflicts:
#	src/Compiler/TypedTree/tainted.fsi
#	src/fsharp/CompilerImports.fs
#	src/fsharp/ExtensionTyping.fs
#	src/fsharp/ExtensionTyping.fsi
psfinaki pushed a commit that referenced this issue Aug 22, 2024
* Update to .NET9p7 SDK

* Add dotnet9 feed

* Update trimming

* update trimming #2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants