Matt Ward

SharpDevelop, MonoDevelop, Xamarin Studio, NuGet, Visual Studio for Mac.

[Matt Ward @lastexitcode]

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

[Matt Ward @lastexitcode]

@sforkmann Looks like this bug - https://t.co/vGHZ6oOIF9

[Jordan Matthiesen @JMatthiesen]

Hey VSMac friends/users! Based on my feed, I think most have seen the news, but sharing in case you haven't. I've not been working on VSMac for a year now, but it was absolutely one of my favorite teams/projects.

https://t.co/EkSMNkcKzI

[Matt Ward @lastexitcode]

@bernd_salewski @VisualStudioMac 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.

[Matt Ward @lastexitcode]

@bernd_salewski @VisualStudioMac 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?

[Matt Ward @lastexitcode]

@manojdeshmukh78 @VisualStudioMac Would you be able to report this on https://t.co/Lc82qCKE7y ? 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.

[Matt Ward @lastexitcode]

@MikeCodesDotNET @JamesMontemagno @kwlothrop 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.

[Matt Ward @lastexitcode]

@jongalloway @DamselflyPhotos @jeremylikness @runfaster2000 @VisualStudioMac Yes, .NET 8 support is planned for Visual Studio for Mac 17.6 Preview 2. It did not make it into Preview 1.

[Matt Ward @lastexitcode]

@staffanenberg @VisualStudioMac 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.

[Matt Ward @lastexitcode]

@dotMorten @philhenning @sayedihashimi This should be fixed in Visual Studio for Mac 17.5 in a later release. This is currently tracked by this developer community issue - https://t.co/x1Wadw8CaI

[Matt Ward @lastexitcode]

@poderosacoding There is a single installer, and a single Visual Studio for Mac application, that supports all editions. The installer from this page is what you need - https://t.co/DqRrWtEQcc The edition is based on your account when you activate Visual Studio for Mac - https://t.co/jvwVELQjVe

[Matt Ward @lastexitcode]

@JMatthiesen @mkristensen @i_ssuresh @mjhutchinson 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. https://t.co/GaHObOZr58

[Matt Ward @lastexitcode]

@JMatthiesen @mkristensen @i_ssuresh @mjhutchinson 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. https://t.co/TNPTwe8k1m

[Matt Ward @lastexitcode]

@jfversluis @praeclarum @rodrigo_moya @JasonImison Installing the macOS workload for .NET 7 seems to have fixed the problem for me.

[Matt Ward @lastexitcode]

@jfversluis @praeclarum @rodrigo_moya @JasonImison 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.

[Matt Ward @lastexitcode]

@sshary19 @jfversluis @dotnet @VisualStudioMac I would try unchecking 'Build with MSBuild on mono' in solution properties - Build - General.

[Matt Ward @lastexitcode]

@sshary19 @jfversluis @dotnet @VisualStudioMac 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