Closed JaneySprings closed 1 year ago
Now you can use following as a workaround:
Create a tasks.json
file inside the .vscode
folder:
{
"version": "2.0.0",
"tasks": [
{
"type": "dotnet-meteor.task",
"target": "Build",
"problemMatcher": [
"$dotnet-meteor.problemMatcher"
],
"label": "Build iOSSimulator-x64",
"args": [
"-p:RuntimeIdentifier=iossimulator-x64"
]
}
]
}
Add a new configuration in the launch.json
file:
{
"version": "0.2.0",
"configurations": [
{
"name": ".NET Meteor Debugger",
"type": "dotnet-meteor.debugger",
"request": "launch",
"preLaunchTask": "dotnet-meteor: Build"
},
// Launch on iossimulator-x64
{
"name": ".NET Meteor: iOSSimulator-x64",
"type": "dotnet-meteor.debugger",
"request": "launch",
"runtime": "iossimulator-x64",
"preLaunchTask": "Build iOSSimulator-x64"
}
]
}
And now you can select a new configuration and run it:
I had implemented this feature in the 2.61.0
version.
Thanks for the workaround! Very much appreciated!
JFYI While I really appreciate this change it broke our project. We have dependencies like SkiaSharp and SQLitePCL.raw that are missing the native library builds for iossimulator-arm64. I'll try to work with the maintainers to rectify it but since there's no switch I am forced to downgrade the extension now.