I actually disagree very much with your statement of its a waste of everyone's time putting out more linux distro's. Firstly, dotnet or rather at the very least .net core or whatever the latest crossplatform offering is is advertised with installation instructions for at LEAST 7 linux distro's.
All products that are then compilable by the advertised version of dotnet (e..g .net5) SHOULD then by extension be compilable on the OS's it runs on.... without fail and especially without broken builds checked in.(btw.. when did that become the fashion?)
Also regarding the issue of checking out code from github and compiling. I always thought that the one branch of code that SHOULD always work (i.e. compile for release etc) was the main/tip/head branch. So imagine me.. using Fedora, goes and checks out msuild. I run "build.sh" ... then I get enough errors to last a lifetime. Now .. perhaps MS handles their projects differently etc etc.. but to me to check out the main branch, hit compile and be faced with errors is a major sin.
If the code exists for a build to only work on ubuntu, then it should go in the ubuntu branch.
Why do I made these assumptions? Well.. because its advertised. Cross platform, I see my linux distro is in there .. so why should I not expect something to work? Another point is that there actually arent that many truly unique linux distro's. All more or less conform to a standard. All other distro's are based on the major ones.. so should in theory work.
Note that my comments aren't said with malicious or hidden intent. Its all something that I'm surprised no one has mentioned.
I believe a huge part of the success of C# and .Net as a framework is due to the IDE. If you ever used the IDE that came with for example VB6 (Visual Interdev) then you will understand what Im talking about. The part that I think ESPECIALLY stands out with the IDE is the WINFORMS DESIGNER which made RAD actually rather ejoyable.
Albeit one can claim that it was more or less duplicated from the delphi ide (which was a wonderful ide for RAD in my personal opinion)
I think MS is missing an opportunity to play a role in somewhat bringing unity to as claimed divided linux community albeit with regards to a small area of programming. They should do the ide on linux.. but do it THEIR way and not try satisfy squabbles between communities. (pref the ide will contain a winforms designer - and not whatever js decides) . If they do it well enough.. people WILL follow. They do have the resources.
It would have maybe been a bit better to have announced intentions on the main website and not have to dig into various forums around the web to discover that projects are abandoned as I would prefer the news from the horses mouth.
Lastly.As mentioned , none of my statements are meant in any devious or malicious way. It just seemed a waste to invest 15+ years in mono/monodevelop for someone to abandon it .. doesn't it? ;)
Microsoft/VisualStudio/v16.0? i have NEVER seen any folders like that installed alongside any dotnet core install.
We are having an issue with a Visual Studio for Mac Extension build. Currently we have dependancies to MonoDevelop.Ide and MonoDevelop.Core and we have hardcoded version(17.0) the problem is that for example if Visual Studio for Mac 2022 Preview release new version17.2 our extensions stops working bacause it cannot find the dependancy with the correct version. So is there a way to build an Extension that would work in more than one Visual Studio for Mac 2022 release or we have to release new version of the Extension each time Visual Studio for MAC 2022 releases a new version?
Excuse me if this question is not for this group, just did not find specific group for VS for Mac.