You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dotnet --info output:
VS Code version:
C# Extension version:all
Steps to reproduce:
Take on what turns out to be the very difficult challenge of teaching MVC6 and ASP.NET Core to my PolyTech programming class. Spend many hours setting up a virtual machine running Windows 10 32-bit with Visual Studio Code and resources for many good reasons coming from the special challenges of this teaching and learning environment including many many installation failures on student laptops. Get many errors. Click an obscure blue OmniSharp error message in the bottom right hand corner of VS Code. Display happens to mention X64 in an installation error message. Be like a Sherlock Holmes detective and follow the trail to this github site and discover - well scrolled down and therefore obscure - the sad sad information that support for Windows is 64-bit only.
Expected behavior:
Preferably support 32-bit. Because everything else in this ASP.NET Core ecosystem supports 32-bit. Wide support of OSs is a stated Core aim so this exception comes as a less than obvious surprise.
ALTERNATIVE expected behaviour: Warn us about 64-bit only - UPFRONT - as in visible when this item appears in the Extensions panel of VS Code. Further suggestion is better indication of error when installing into 32-bit Windows.
Actual behavior:
dotnet run of the "Blogging" example app aka "EFGetStarted.AspNetCore.ExistingDB" results in bright red text giving 608 errors "error NU1001: The dependency ... could not be resolved". See attached screen shots.
The text was updated successfully, but these errors were encountered:
I just wanted to let you know that the latest release of the C# extension (1.5.2) supports 32-bit Windows for IntelliSense, go to definition, find all references, and other editor features. The debugger still does not support 32-bit Windows, and that is being tracked with #844.
Environment data
dotnet --info
output:VS Code version:
C# Extension version:all
Steps to reproduce:
Take on what turns out to be the very difficult challenge of teaching MVC6 and ASP.NET Core to my PolyTech programming class. Spend many hours setting up a virtual machine running Windows 10 32-bit with Visual Studio Code and resources for many good reasons coming from the special challenges of this teaching and learning environment including many many installation failures on student laptops. Get many errors. Click an obscure blue OmniSharp error message in the bottom right hand corner of VS Code. Display happens to mention X64 in an installation error message. Be like a Sherlock Holmes detective and follow the trail to this github site and discover - well scrolled down and therefore obscure - the sad sad information that support for Windows is 64-bit only.
Expected behavior:
Preferably support 32-bit. Because everything else in this ASP.NET Core ecosystem supports 32-bit. Wide support of OSs is a stated Core aim so this exception comes as a less than obvious surprise.
ALTERNATIVE expected behaviour: Warn us about 64-bit only - UPFRONT - as in visible when this item appears in the Extensions panel of VS Code. Further suggestion is better indication of error when installing into 32-bit Windows.
Actual behavior:
dotnet run of the "Blogging" example app aka "EFGetStarted.AspNetCore.ExistingDB" results in bright red text giving 608 errors "error NU1001: The dependency ... could not be resolved". See attached screen shots.
The text was updated successfully, but these errors were encountered: