I believe VS uses this to get multiple completions and then you can cycle through different completions via the Edit.NextSuggestion/PreviousSuggestion keyboard shortcuts.

Looks like this bug - github.com/dotnet/sdk/issues…

Thanks for confirming. The problem you are seeing is a bug in the installer. It causes the 'Install Visual Studio for Mac' icon to not be centered, and in the case when you have opted in to show hidden files it can result in the icon being scrolled out of view. Sorry about that.

Hi, would you be able to post a screenshot of what you are seeing? Can you try right clicking inside the opened .dmg and selecting View - as List?

Would you be able to report this on developercommunity.visualstu… ? To diagnose we would need the Package Console output, also information about whether the solution contains a mix of classic and SDK style projects. Thanks.

With a .NET 7 iOS app, both dotnet and VS Mac end up building with the .NET Standard 2.0 Xamarin.Essentials.dll which does not have the Platform type. It does not use the xamarinios10/Xamarin.Essentials.dll which a classic Xamarin iOS project would use.

Yes, .NET 8 support is planned for Visual Studio for Mac 17.6 Preview 2. It did not make it into Preview 1.

It looks like something changed in Visual Studio for Mac 17.x. Visual Studio for Mac 8.10 allows pasting. Initially I thought this was due to a security change, but it seems not since it works with the older version. I have opened a bug for this. Thanks for reporting.

There are also several other extensions for VS Mac under my github account, which do not use addin maker, but show in more depth what can be extended. github.com/mrward

I have a couple of sample extensions for VS Mac, one hello world, one that shows a custom UI for the new project dialog, both of these use addin maker. github.com/mrward/vsmac-exte…

Installing the macOS workload for .NET 7 seems to have fixed the problem for me.

You can see it is not working in VS Mac since the main toolbar shows 'Default' instead of 'My Mac (macOS)'. Not sure what your setup is.

Just had this happen to me on another machine. I have macOS workloads installed for .NET 6 but not .NET 7. Added a global.json to pin to .NET 6, but VS Mac seems to not consider the project a macOS project, same error trying to run the .dll instead of the native executable.

I believe the mac addin should be trying to run the native executable from the project's app bundle not the .dll. I was going to suggest, as a workaround, changing the run config to directly run the native executable, but you cannot configure that for macOS projects :(

I would try unchecking 'Build with MSBuild on mono' in solution properties - Build - General.

It looks like .NET is being downgraded. I am guessing your solution has a classic project (non-sdk style) which causes the entire solution to be built with MSBuild on mono, which does not support the latest .NET SDKs

The first macOS option will install the macOS workload for .NET 7 only. The Xamarin category is for classic Xamarin that requires Mono to build.

Xcode 13.x when you run it without Rosetta installed it prompts for you to install Rosetta - although you can cancel the dialog. Not sure exactly what inside Xcode requires Rosetta and causes that dialog to be displayed. Possibly this has changed in Xcode 14?