- 
                Notifications
    
You must be signed in to change notification settings  - Fork 561
 
          [Xamarin.Android.Build.Tasks] don't set $(UseMonoRuntime) by default
          #10527
        
          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
base: main
Are you sure you want to change the base?
Conversation
ad0ed28    to
    c9bb3bb      
    Compare
  
    | 
           I assume this means that in .NET 11 CoreCLR will be the default runtime…  | 
    
dbf485e    to
    8000aef      
    Compare
  
    | <_AndroidRuntime Condition=" '$(PublishAot)' == 'true' and '$(UseMonoRuntime)' != 'true' ">NativeAOT</_AndroidRuntime> | ||
| <_AndroidRuntime Condition=" '$(PublishAot)' != 'true' and '$(UseMonoRuntime)' != 'true' ">CoreCLR</_AndroidRuntime> | ||
| <_AndroidRuntime Condition=" '$(_AndroidRuntime)' == '' ">MonoVM</_AndroidRuntime> | ||
| <_AndroidRuntime Condition=" '$(PublishAot)' == 'true' ">NativeAOT</_AndroidRuntime> | 
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.
What happens in Debug builds when you have <PublishAot>true</PublishAot> in the project file? Does it try to still run with NativeAOT? For "PublishAOT Debug builds", I believe we need to use CoreCLR 🤔 I suppose we can fix that later though.
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.
I think in this case it will try to use Mono AOT as it is now, at least the error messages I've seen suggest that. Yeah, we can't use NativeAOT for debug builds.
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.
Let's address this in another PR, I think Debug mode should mirror what a console app does. It would use CoreCLR there.
0ead24b    to
    3492e3f      
    Compare
  
    | 
           /azp run  | 
    
| 
          
Azure Pipelines successfully started running 1 pipeline(s). | 
    
a55d6f6    to
    dae743f      
    Compare
  
    | 
           /azp run  | 
    
| 
          
Azure Pipelines successfully started running 1 pipeline(s). | 
    
dae743f    to
    23a5d24      
    Compare
  
    | 
           /azd run  | 
    
a4ea6e9    to
    da832e4      
    Compare
  
    The removed classes contain tests which fail on CoreCLR (possibly due to not supporting the managed typemap, but it requires more research) and should be fixed in a separate PR.
da832e4    to
    0d9b143      
    Compare
  
    | 
           /azp run  | 
    
| 
          
Azure Pipelines successfully started running 1 pipeline(s). | 
    
Make CoreCLR the default runtime.
Fixes or (temporarily) disables a number of tests which were failing because of a variety
of reasons, such as:
Additionally, it parametrizes a number of tests with the runtime type,
so that they ran for both MonoVM and CoreCLR (and, eventually, NativeAOT)