Announcement: Planned removal of the included Mono & MSBuild tools #5120

JoeRobich · 2022-03-19T02:06:16Z

Background:

The included Mono and MSBuild tools were added to support easy development of C# using .NET Core. We have frequently updated these build tools to match the current shipping SDK tooling.

On Windows we did not need to ship a copy of Mono because we could rely on the .NET Framework being installed. For MacOS and Linux we shipped a minimal Mono that would support running MSBuild and OmniSharp. With these tools, the .NET SDK installed, and the dotnet CLI discoverable from the environment PATH, developers would have good support when developing against the newer SDK-style projects.

There was some support for Full Framework projects with this configuration, but that was considered a bonus. Our most common Full Framework projects (Unity) were unsupported with this configuration because the .NET 4.7.1 targeting pack was not included.

In the future .NET Framework OmniSharp builds will not ship with Mono or the MSBuild tooling (See announcement omnisharp-roslyn#2339, See PR omnisharp-roslyn#2360).

Proposal:

To ensure that the C# extension remains usable out of the box for .NET SDK projects, we will be changing the default value of omnisharp.useModernNet to true. This means by default OmniSharp will run on the .NET SDK and .NET Framework projects will likely not load properly. It will require the .NET 6 SDK be installed and the dotnet CLI to be discoverable from the environment PATH.

Users who need .NET Framework support will have to set omnisharp.useModernNet to false to download the .NET Framework build of OmniSharp. Linux and MacOS users will need to have a complete system install of Mono including MSBuild (Download). Windows users will need to have the Visual Studio MSBuild Tools or a full Visual Studio installed (Download).

The omnisharp.useGlobalMono setting will be removed as there is no longer an included Mono and we will always use the system installation of Mono.

The text was updated successfully, but these errors were encountered:

HaraldKorneliussen · 2022-03-30T09:17:01Z

I guess the removal of bundled msbuild is the reason omnisharp suddenly fails on my projects with

The MSBuild option 'UseBundledOnly' is no longer supported. Please update your OmniSharp configuration files.

Having a bundled version seems like a good idea to me, especially if the alternative is chasing version dependencies manually.

filipw · 2022-03-30T13:43:39Z

We never shipped .NET Framework reference assemblies, so the bundled MSBuild was only suitable for .NET Core (and .NET 5+) development, and it was a poor man's replacement for discovering the MSBuild from the .NET SDK installation.

Since for .NET Core (and .NET 5+) development you anyway need to have the relevant .NET SDK installed, and since .NET SDK has the appropriate MSBuild already, this will be the MSBuild discovered and used by OmniSharp.

NoTuxNoBux · 2022-04-07T15:23:20Z

Does this mean that using Unity projects with this package will essentially become impossible for the time being without changing the flag back (or after the flag is dropped)?

It just so happens that I already created an issue on the Unity VSCode package issue tracker around Unity generating legacy .NET Framework 4.7 csproj files instead of the newer format, even if the project is set to API compatibility .NET Standard 2.0. If I understand correctly, this is a change that Unity must make to keep its package compatible with OmniSharp on the long term?

JoeRobich · 2022-04-07T17:18:12Z

Does this mean that using Unity projects with this package will essentially become impossible for the time being without changing the flag back (or after the flag is dropped)?

Yes, for your unity projects you can set omnisharp.useModernNet to false in the Workspace settings instead of User settings. This should allow you to use the modern build of O# by default, but have it do the right thing in configured Unity workspaces.

If I understand correctly, this is a change that Unity must make to keep its package compatible with OmniSharp on the long term?

Yes, Unity could possibly continue to target net471, but they would definitely need to update to SDK-style projects.

tngmrk77 · 2022-04-24T11:47:33Z

Hi @JoeRobich, I set "omnisharp.useModernNet": false for User and Workspace but intellisense's omnisharp dont'works
Can you help me please? :(
I have version VSCode 1.66.2 and extension C# version 1.24.4

JoeRobich · 2022-04-24T16:37:56Z

@tngmrk77 Can you please open a new issue and provide the requested OmniSharp Log and C# Log from the VS Code output pane?

JoeRobich · 2022-05-21T00:16:23Z

These changes will be complete when v1.25.0 ships.

JoeRobich · 2022-05-24T19:11:56Z

v1.25.0 has shipped with this change. A .NET 6 SDK is required when running with "omnisharp.useModernNet" set to "true", which is the default configuration.

esklarski · 2022-05-25T20:16:23Z

This seems to have completely broken Unity projects.

If I set useModernNet to false as suggested I just get a different error:
[info]: OmniSharp.Services.DotNetCliService DotNetPath set to /usr/lib64/dotnet/dotnet [info]: OmniSharp.MSBuild.Discovery.MSBuildLocator Located 0 MSBuild instance(s) Could not locate MSBuild instance to register with OmniSharp.

Or with useModernNet set true I get:
/usr/lib64/dotnet/sdk/6.0.105/Microsoft.Common.CurrentVersion.targets(1217,5): Error: This project targets .NET version that requires reference assemblies that are not installed (e.g. .NET Framework). The most common solution is to make sure Mono is fully updated on your machine (https://mono-project.com/download/) and that you are running the .NET Framework build of OmniSharp (e.g. 'omnisharp.useModernNet': false in C# Extension for VS Code).

I'm on Fedora 36 and everything seems installed when I go through setup set again (and again).

wanieru · 2022-05-25T20:52:45Z

Having the exact same issue as @esklarski, I'm on Fedora 35.

JoeRobich · 2022-05-25T21:01:15Z

@esklarski From the error Could not locate MSBuild instance to register with OmniSharp., It does not appear that your system install of Mono includes MSBuild. Which mono packages do you have installed? Perhaps this page is helpful in getting a working dev environment -https://developer.fedoraproject.org/tech/languages/dotnet/mono.html

mrchantey · 2022-05-26T01:30:17Z

fyi I wrote a stackoverflow answer for how I got it working again on Windows.

liujinlong123 · 2022-05-26T01:53:35Z

Can you provide a solution on ubuntu ?

esklarski · 2022-05-26T02:09:24Z

@esklarski From the error Could not locate MSBuild instance to register with OmniSharp., It does not appear that your system install of Mono includes MSBuild. Which mono packages do you have installed? Perhaps this page is helpful in getting a working dev environment -https://developer.fedoraproject.org/tech/languages/dotnet/mono.html

I've done exactly as those instructions say.

dnf install mono-develop

I forget the exact version just now, 6 something.

The problem could be the Fedora packaging, any suggestion how to check?

[xxxx@fedora ~]$ dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.105
 Commit:    1c35735293

Runtime Environment:
 OS Name:     fedora
 OS Version:  36
 OS Platform: Linux
 RID:         fedora.36-x64
 Base Path:   /usr/lib64/dotnet/sdk/6.0.105/

Host (useful for support):
  Version: 6.0.5
  Commit:  70ae3df4a6

.NET SDKs installed:
  6.0.105 [/usr/lib64/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.5 [/usr/lib64/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.5 [/usr/lib64/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET runtimes or SDKs:
  https://aka.ms/dotnet-download
[xxxx@fedora ~]$ mono --version
Mono JIT compiler version 6.12.0.122 (tarball Thu Jan 20 20:34:53 UTC 2022)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	Interpreter:   yes
	LLVM:          supported, not enabled.
	Suspend:       hybrid
	GC:            sgen (concurrent by default)

liujinlong123 · 2022-05-26T02:20:11Z

This is my steps:

mono: sudo apt install mono-complete

mk@mk:~$ mono --version
Mono JIT compiler version 6.12.0.179 (tarball Tue May 17 21:33:45 UTC 2022)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	Interpreter:   yes
	LLVM:          yes(610)
	Suspend:       hybrid
	GC:            sgen (concurrent by default)
mk@mk:~$

.net sdk: ./dotnet-install.sh -c Current

mk@mk:~$ dotnet --info
.NET SDK (反映任何 global.json):
 Version:   6.0.300
 Commit:    8473146e7d

运行时环境:
 OS Name:     ubuntu
 OS Version:  20.04
 OS Platform: Linux
 RID:         ubuntu.20.04-x64
 Base Path:   /home/mk/.dotnet/sdk/6.0.300/

Host (useful for support):
  Version: 6.0.5
  Commit:  70ae3df4a6

.NET SDKs installed:
  6.0.104 [/home/mk/.dotnet/sdk]
  6.0.202 [/home/mk/.dotnet/sdk]
  6.0.300 [/home/mk/.dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.4 [/home/mk/.dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.5 [/home/mk/.dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.4 [/home/mk/.dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.5 [/home/mk/.dotnet/shared/Microsoft.NETCore.App]

To install additional .NET runtimes or SDKs:
  https://aka.ms/dotnet-download
mk@mk:~$

Omnisharp version is 1.25.0; vscode version is 1.67, settings.json

"omnisharp.useModernNet": true,

but it still doesn't work

Starting OmniSharp server at 2022/5/26 10:19:05
    Target: /home/mk/workLiu/simulation/unity/L_Learn

OmniSharp server started with .NET 6.0.300
.
    Path: /home/mk/.vscode/extensions/ms-dotnettools.csharp-1.25.0-linux-x64/.omnisharp/1.39.0-net6.0/OmniSharp.dll
    PID: 46793

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on Unknown 0.0 (Unknown)
[info]: OmniSharp.Services.DotNetCliService
        Checking the 'DOTNET_ROOT' environment variable to find a .NET SDK
[info]: OmniSharp.Services.DotNetCliService
        Using the 'dotnet' on the PATH.
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 3 MSBuild instance(s)
            1: .NET Core SDK 6.0.300 17.2.0 - "/home/mk/.dotnet/sdk/6.0.300/"
            2: .NET Core SDK 6.0.202 17.1.1 - "/home/mk/.dotnet/sdk/6.0.202/"
            3: .NET Core SDK 6.0.104 17.0.0 - "/home/mk/.dotnet/sdk/6.0.104/"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: .NET Core SDK 6.0.300 17.2.0 - "/home/mk/.dotnet/sdk/6.0.300/"
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0
[info]: OmniSharp.MSBuild.ProjectSystem
        Detecting projects in '/home/mk/workLiu/simulation/unity/L_Learn/L_Learn.sln'.
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp-Editor.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/home/mk/workLiu/simulation/unity/L_Learn'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Did not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/home/mk/workLiu/simulation/unity/L_Learn' on host 46614.
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp.csproj
[fail]: OmniSharp.MSBuild.ProjectLoader
        This project targets .NET version that requires reference assemblies that are not installed (e.g. .NET Framework). The most common solution is to make sure Mono is fully updated on your machine (https://mono-project.com/download/) and that you are running the .NET Framework build of OmniSharp (e.g. 'omnisharp.useModernNet': false in C# Extension for VS Code).
[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file '/home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp.csproj'.
/home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp.csproj
/home/mk/.dotnet/sdk/6.0.300/Microsoft.Common.CurrentVersion.targets(1221,5): Error: This project targets .NET version that requires reference assemblies that are not installed (e.g. .NET Framework). The most common solution is to make sure Mono is fully updated on your machine (https://mono-project.com/download/) and that you are running the .NET Framework build of OmniSharp (e.g. 'omnisharp.useModernNet': false in C# Extension for VS Code).

[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp-Editor.csproj
[fail]: OmniSharp.MSBuild.ProjectLoader
        This project targets .NET version that requires reference assemblies that are not installed (e.g. .NET Framework). The most common solution is to make sure Mono is fully updated on your machine (https://mono-project.com/download/) and that you are running the .NET Framework build of OmniSharp (e.g. 'omnisharp.useModernNet': false in C# Extension for VS Code).
[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file '/home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp-Editor.csproj'.
/home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp-Editor.csproj
/home/mk/.dotnet/sdk/6.0.300/Microsoft.Common.CurrentVersion.targets(1221,5): Error: This project targets .NET version that requires reference assemblies that are not installed (e.g. .NET Framework). The most common solution is to make sure Mono is fully updated on your machine (https://mono-project.com/download/) and that you are running the .NET Framework build of OmniSharp (e.g. 'omnisharp.useModernNet': false in C# Extension for VS Code).

[fail]: OmniSharp.MSBuild.ProjectManager
        Attempted to update project that is not loaded: /home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp.csproj
[fail]: OmniSharp.MSBuild.ProjectManager
        Attempted to update project that is not loaded: /home/mk/workLiu/simulation/unity/L_Learn/Assembly-CSharp-Editor.csproj

esklarski · 2022-05-26T19:45:53Z

@esklarski Can you try the mono-complete package?

I did some checking and as far as I can tell msbuild is installed properly on my system.

Mono does not use the dotnet SDK version of MSBuild.

I have the mono-complete package installed, and v1.25.0 still breaks things.

JoeRobich · 2022-05-26T20:44:49Z

@esklarski Lets continue this investigation on #5232. Hopefully we can come up with a workable solution.

liujinlong123 · 2022-05-26T23:44:25Z

@liujinlong123 If you are trying to do Unity development, then you need to set useModernNet to false

From the output you shared:

The most common solution is to make sure Mono is fully updated on your machine (https://mono-project.com/download/) and that you are running the .NET Framework build of OmniSharp (e.g. 'omnisharp.useModernNet': false in C# Extension for VS Code).

Thanks!!

DavidJVitale · 2022-05-27T04:36:49Z

I understand the need for breaking software changes like this, but please consider communicating this change in a more clear way to end-users. I have the latest mono installed, but OmniSharp server would completely silently fail and give no indication of what was wrong. Not every user of VS code would think to check this github page when that happens. Maybe a popup in vs-code linking to this announcement would be helpful?

For more details -- I am on Ubuntu, latest version of mono installed, using vs-code with mono. My OmniSharp server would fail to even start, show no output at all in VS code. No icon in the bottom tray. Ctrl + Shift + P -> Restart OmniSharp Server is the top google result, and that would silently fail. Running OmniSharp: Analyze Current Project would throw a OmniSharp server is not running error, but top google results send you in a wrong direction. Finally, I found this page, and going to Settings and setting UseModernNet to false fixed my error.

Thank you for all the work your team does!

kmcfate · 2022-05-30T01:49:15Z

To fix Intellisense/Omnisharp on Ubuntu 22.04 use https://launchpad.net/~eofla/+archive/ubuntu/msbuild and install the msbuild and msbuild-roslyn packages. Also make sure omnisharp.useModernNet is false and the mono-complete package is installed.

abreu9999 · 2022-06-30T06:35:44Z

To fix Intellisense/Omnisharp on Ubuntu 22.04 use https://launchpad.net/~eofla/+archive/ubuntu/msbuild and install the msbuild and msbuild-roslyn packages. Also make sure omnisharp.useModernNet is false and the mono-complete package is installed.

Thanks, this fixed the error "Could not locate MSBuild instance to register with OmniSharp" for me.
Regards

1w1f · 2022-07-02T15:20:35Z

We never shipped .NET Framework reference assemblies, so the bundled MSBuild was only suitable for .NET Core (and .NET 5+) development, and it was a poor man's replacement for discovering the MSBuild from the .NET SDK installation.

Since for .NET Core (and .NET 5+) development you anyway need to have the relevant .NET SDK installed, and since .NET SDK has the appropriate MSBuild already, this will be the MSBuild discovered and used by OmniSharp.

if find many dotnet sdk ,how to select the sdk to find msbuild to Registered MSBuild instance?

JoeRobich · 2022-07-06T20:05:30Z

@1w1f You can set the omnisharp.sdkVersion to the version string you would like to load. You can also configure your omnisharp.json like so (see SDKOptions.cs).

{
  "SDK": {
    "Version": "{enter version string}"
  }
}

Hakazaba · 2022-09-30T23:09:38Z

To fix Intellisense/Omnisharp on Ubuntu 22.04 use https://launchpad.net/~eofla/+archive/ubuntu/msbuild and install the msbuild and msbuild-roslyn packages. Also make sure omnisharp.useModernNet is false and the mono-complete package is installed.

I'm getting a Broken pipe error when installing Msbuild-roslyn after Msbuild:
Unpacking msbuild-roslyn (1:17.1-0ppa3) ... dpkg: error processing archive /var/cache/apt/archives/msbuild-roslyn_1%3a17.1-0ppa3_all.deb (--unpack): trying to overwrite '/usr/bin/csc', which is also in package mono-roslyn 6.12.0.182-0xamarin1+ubuntu1804b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/msbuild-roslyn_1%3a17.1-0ppa3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

myocytebd · 2022-11-02T07:18:16Z

There is a minor bug that, after set useModernNet=false, omnisharp restarts and immediately fails due to lack of OmniSharp.exe.
It seems that .NET framework build don't download until restart vscode.
It is minor but confusing: omnisharp should instructs user to restart vscode.

ATikadze · 2022-11-09T12:27:43Z

Hello,
I'm working in VS Code + Unity on macOS and until today everything was working fine. Today I opened vs code, disabled Use Modern Net (because sometimes I work on .Net 6) and it displays the following error (I'll attach the screenshot too):
OmniSharp requires a complete install of Mono (including MSBuild) to provide language services when omnisharp.useModernNet is disabled in Settings. Please install the latest Mono and restart.

I downloaded Mono, even though I had a very recent version, and restarted vs code. It still shows this error.
Keep in mind that yesterday it was working fine.

Software versions:

macOS Monterey 12.6
Unity 2021.3.11f1
VS Code 1.73.0
Mono 6.12.0

filipw · 2022-11-09T12:44:38Z

@ATikadze see #5443 (comment)

ATikadze · 2022-11-09T13:46:41Z

@filipw Reverted C# extension to 1.25.0 and works again. Thanks 👍

alexandr-osprey · 2022-12-18T07:24:26Z

@filipw @ATikadze still have the same issue in 1.25.2
using dev container with mcr.microsoft.com/dotnet/sdk:5.0 mono installed like this

RUN  apt install -y gnupg ca-certificates && \
    apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF && \
    "deb https://download.mono-project.com/repo/ubuntu stable-focal main" | tee /etc/apt/sources.list.d/mono-official-stable.list && \
    apt update && \
    apt install mono-devel -y

I can provide full repository with dockerfile if needed

crawlchange · 2023-03-07T05:10:59Z

"Go To Definition" is STILL not working on windows, vscode. What is this plugin good for? NOTHING in the documentation works. All the commands do NOTHING.

JoeRobich pinned this issue Mar 19, 2022

halilkocaoz mentioned this issue Mar 25, 2022

mono: command not found #5127

Closed

filipw mentioned this issue Mar 30, 2022

System.Reflection.ReflectionTypeLoadException when getting code actions #5105

Open

JoeRobich mentioned this issue Mar 31, 2022

Omnisharp won't start or generate assets in vs code mac m1 #5132

Closed

NoTuxNoBux mentioned this issue Apr 8, 2022

omnisharp-vscode version 1.24.3 does not load on debian (possibly other OS'es) #5147

Closed

This was referenced Apr 12, 2022

Omnisharp fails to load #3545

Closed

Make SDK build of OmniSharp the default #5176

Merged

JoeRobich mentioned this issue Apr 21, 2022

How to use .NET 5 SDK without upgrade Visual Studio to 16.8 #4358

Closed

JoeRobich mentioned this issue Apr 25, 2022

Low-hanging nullable fruit #5186

Merged

filipw mentioned this issue May 11, 2022

Omnisharp server crashes on start #5181

Closed

luke-atp mentioned this issue May 24, 2022

[ERROR] Error: Found dotnet version 5.0.403. Minimum required version is 6.0.100. #5222

Closed

JoeRobich mentioned this issue May 24, 2022

C# formatter broken in ms-dotnettools.csharp-1.25.0-linux-x64 #5223

Closed

dfibuch mentioned this issue May 25, 2022

Omnisharp server not running #5229

Closed

JoeRobich mentioned this issue May 25, 2022

version 1.25.0 "omnisharp.useGlobalMono" Disappeared #5228

Closed

jkeech mentioned this issue May 25, 2022

How to fix OmniSharp broken in dotnet 3.1 image microsoft/vscode-dev-containers#1474

Open

JoeRobich mentioned this issue May 26, 2022

OmniSharp not working with legacy .NET projects on Fedora 36 #5232

Closed

JoeRobich mentioned this issue May 27, 2022

On Mac Intel, with SDK:3.1.420 x64 and latest C# extension:1.25.0 installed, debugging 3.1 project doesn't work in VSCode. #5237

Closed

This was referenced May 30, 2022

Syntax Correction/Highlighting has Vanished in VSC #5244

Closed

C# 1.25.0 causing code editing issues #5245

Closed

v1.25.0 C# extension not working - Unity 2021 & 2020 #5252

Closed

JoeRobich mentioned this issue Jun 7, 2022

1.25 is messing with intellisense, no completion/intellisense, no methods recognized... reverting to 1.24.4 makes everything ok #5257

Closed

333fred mentioned this issue Aug 19, 2022

Incomplete/missing system API methods OmniSharp/omnisharp-roslyn#2432

Closed

Alexey-T mentioned this issue Oct 10, 2022

More language servers Alexey-T/CudaText#4423

Closed

RbBtSn0w mentioned this issue Dec 9, 2022

Omnisharp not working on Mac OS M1 and VS Code #5262

Closed

timsu92 mentioned this issue Feb 27, 2023

Can't use out-of-box because of MSBuild OmniSharp/omnisharp-vim#834

Open

dibarbet added the OmniSharp label Jun 6, 2023

microhobby mentioned this issue Aug 17, 2023

Mono Template intellisense does not work witht the new C# dev tools extension torizon/vscode-torizon-templates#89

Closed

dibarbet mentioned this issue Oct 6, 2023

Add support for using Mono to load .NET Framework projects dotnet/roslyn#70263

Merged

JoeRobich unpinned this issue May 2, 2024

mikadumont closed this as completed Sep 4, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Announcement: Planned removal of the included Mono & MSBuild tools #5120

Announcement: Planned removal of the included Mono & MSBuild tools #5120

JoeRobich commented Mar 19, 2022 •

edited

Loading

HaraldKorneliussen commented Mar 30, 2022

filipw commented Mar 30, 2022

NoTuxNoBux commented Apr 7, 2022

JoeRobich commented Apr 7, 2022 •

edited

Loading

tngmrk77 commented Apr 24, 2022

JoeRobich commented Apr 24, 2022

JoeRobich commented May 21, 2022

JoeRobich commented May 24, 2022

esklarski commented May 25, 2022 •

edited

Loading

wanieru commented May 25, 2022

JoeRobich commented May 25, 2022 •

edited

Loading

mrchantey commented May 26, 2022

liujinlong123 commented May 26, 2022

esklarski commented May 26, 2022 •

edited

Loading

liujinlong123 commented May 26, 2022

esklarski commented May 26, 2022

JoeRobich commented May 26, 2022

liujinlong123 commented May 26, 2022

DavidJVitale commented May 27, 2022

kmcfate commented May 30, 2022 •

edited

Loading

abreu9999 commented Jun 30, 2022

1w1f commented Jul 2, 2022

JoeRobich commented Jul 6, 2022

Hakazaba commented Sep 30, 2022

myocytebd commented Nov 2, 2022

ATikadze commented Nov 9, 2022 •

edited

Loading

filipw commented Nov 9, 2022

ATikadze commented Nov 9, 2022

alexandr-osprey commented Dec 18, 2022 •

edited

Loading

crawlchange commented Mar 7, 2023

Announcement: Planned removal of the included Mono & MSBuild tools #5120

Announcement: Planned removal of the included Mono & MSBuild tools #5120

Comments

JoeRobich commented Mar 19, 2022 • edited Loading

HaraldKorneliussen commented Mar 30, 2022

filipw commented Mar 30, 2022

NoTuxNoBux commented Apr 7, 2022

JoeRobich commented Apr 7, 2022 • edited Loading

tngmrk77 commented Apr 24, 2022

JoeRobich commented Apr 24, 2022

JoeRobich commented May 21, 2022

JoeRobich commented May 24, 2022

esklarski commented May 25, 2022 • edited Loading

wanieru commented May 25, 2022

JoeRobich commented May 25, 2022 • edited Loading

mrchantey commented May 26, 2022

liujinlong123 commented May 26, 2022

esklarski commented May 26, 2022 • edited Loading

liujinlong123 commented May 26, 2022

This is my steps:

esklarski commented May 26, 2022

JoeRobich commented May 26, 2022

liujinlong123 commented May 26, 2022

DavidJVitale commented May 27, 2022

kmcfate commented May 30, 2022 • edited Loading

abreu9999 commented Jun 30, 2022

1w1f commented Jul 2, 2022

JoeRobich commented Jul 6, 2022

Hakazaba commented Sep 30, 2022

myocytebd commented Nov 2, 2022

ATikadze commented Nov 9, 2022 • edited Loading

filipw commented Nov 9, 2022

ATikadze commented Nov 9, 2022

alexandr-osprey commented Dec 18, 2022 • edited Loading

crawlchange commented Mar 7, 2023

JoeRobich commented Mar 19, 2022 •

edited

Loading

JoeRobich commented Apr 7, 2022 •

edited

Loading

esklarski commented May 25, 2022 •

edited

Loading

JoeRobich commented May 25, 2022 •

edited

Loading

esklarski commented May 26, 2022 •

edited

Loading

kmcfate commented May 30, 2022 •

edited

Loading

ATikadze commented Nov 9, 2022 •

edited

Loading

alexandr-osprey commented Dec 18, 2022 •

edited

Loading