Closed kzhui125 closed 1 year ago
Hello! Thank you for your question. If you have Mac with Apple chip you don't need to specify the RuntimeIdentifier property in the csproj file. .NET Meteor automatically adds the desired RuntimeIdentifier depending on the architecture of your Mac. You can see this in the vscode terminal
If you want to build the application for Intel architecture on Mac with Apple chip, you can customize the build task. See predefined task customization.
You can create the tasks.json
file with the following content:
{
"version": "2.0.0",
"tasks": [
{
"type": "dotnet-meteor.task",
"target": "Build",
"args": [
"-p:RuntimeIdentifier=maccatalyst-x64"
],
"problemMatcher": [],
"label": "Build MAUI for Mac (Intel)",
}
]
}
and run it
But in this case, you will not be able to launch the application, since .NET Meteor will search for it in the maccatalyst-arm64 folder. Maybe I should add the ability to run Intel applications for Mac with Apple chip.
thanks @JaneySprings for your help I can debug now.
But it seems I can only debug cs file, I can't debug razor file. and why is there two startDate in watch...
Thanks for your help.
I think the Mono Debugger can't resolve breakpoints inside .razor files. I will try to research this issue.
Wow. I added '.razor' files to the Mono 'whitelist' and the breakpoints was resolved
I will release an update soon and add support for Blazor
Great! Thanks a lot.
if I add maccatalyst-arm64 RuntimeIdentifier, the app can't start(seems maui problem).
So how can I debug net7.0-maccatalyst(intel) app?
thanks.