Dotnet Quit Unexpectedly Visual Studio For Mac

-->

Visual Studio for Mac provides a full-featured Integrated Development Environment (IDE) for developing .NET Core applications. This article walks you through building a .NET Core solution that includes a reusable library and unit testing.

I have a site that was built using database first and I'm trying to continue development of it on a mac. Normally I would run the Scaffold-dbContext using the Console Package Manager in Visual Studio. The mac version doesn't have this I tried running it in Terminal, but that obviously didn't work. Steps to Reproduce open this rar open Basic/WG3000DemoBasic/WG3000DemoBasic.csproj release - run This is a 3rd party project. I tested it 6weeks ago on Sierra.

This tutorial shows you how to create an application that accepts a search word and a string of text from the user, counts the number of times the search word appears in the string using a method in a class library, and returns the result to the user. The solution also includes unit testing for the class library as an introduction to unit testing concepts. If you prefer to proceed through the tutorial with a complete sample, download the sample solution. For download instructions, see Samples and Tutorials.

Note

Your feedback is highly valued. There are two ways you can provide feedback to the development team on Visual Studio for Mac:

In Visual Studio for Mac, select Help > Report a Problem from the menu or Report a Problem from the Welcome screen, which opens a window for filing a bug report. You can track your feedback in the Developer Community portal.
To make a suggestion, select Help > Provide a Suggestion from the menu or Provide a Suggestion from the Welcome screen, which takes you to the Visual Studio for Mac Developer Community webpage.

Prerequisites

For more information on prerequisites, see the .NET Core dependencies and requirements. For the full system requirements of Visual Studio 2019 for Mac, see Visual Studio 2019 for Mac Product Family System Requirements.

Neoragex emulator. The Neo Geo emulator is also compatible on Mac and windows 7. Part 3.10 Popular Neo Geo Emulators This section consists of a list of emulators with their ranking from highest to lowest which allows you to play NeoGeo games on a variety of platforms including PC & mac and even consoles such as Dreamcast & Xbox. Start playing the game by installing many more games. How to install Neo Geo Games. First you download the game. Then you need to extract the game’s file, WinRar software. After extracting the game, double click on the file named NeoRAGEx 5.0.exe.

Building a library

On the start window, select New Project. In the New Project dialog under the .NET Core node, select the .NET Standard Library template. This command creates a .NET Standard library that targets .NET Core as well as any other .NET implementation that supports version 2.1 of the .NET Standard. If you have multiple versions of the .NET Core SDK installed, you can choose different versions of .NET Standard for your library. Choose '.NET Standard 2.1' and select Next.
Name the project 'TextUtils' (a short name for 'Text Utilities') and the solution 'WordCounter'. Leave Create a project directory within the solution directory checked. Select Create.
In the Solution pad, expand the TextUtils node to reveal the class file provided by the template, Class1.cs. Ctrl-click the file, select Rename from the context menu, and rename the file to WordCount.cs. Open the file and replace the contents with the following code:
Save the file by using any of three different methods: use the keyboard shortcut ⌘+s, select File > Save from the menu, or ctrl-click on the file's tab and select Save from the contextual menu. The following image shows the IDE window:
Select Errors in the margin at the bottom of the IDE window to open the Errors panel. Select the Build Output button.
Select Build > Build All from the menu.
The solution builds. The build output panel shows that the build is successful.

Creating a test project

Unit tests provide automated software testing during your development and publishing. The testing framework that you use in this tutorial is xUnit (version 2.4.0 or later), which is installed automatically when the xUnit test project is added to the solution in the following steps:

In the Solution sidebar, ctrl-click the WordCounter solution and select Add > Add New Project.
In the New Project dialog, select Tests from the .NET Core node. Select the xUnit Test Project followed by Next.
If you have multiple versions of the .NET Core SDK, you'll need to select the version for this project. Select .NET Core 3.1. Name the new project 'TestLibrary' and select Create.
In order for the test library to work with the WordCount class, add a reference to the TextUtils project. In the Solution sidebar, ctrl-click Dependencies under TestLibrary. Select Edit References from the context menu.
In the Edit References dialog, select the TextUtils project on the Projects tab. Select OK.
In the TestLibrary project, rename the UnitTest1.cs file to TextUtilsTests.cs.
Open the file and replace the code with the following code:
The following image shows the IDE with the unit test code in place. Pay attention to the Assert.NotEqual statement.
It's important to make a new test fail once to confirm its testing logic is correct. The method passes in the name 'Jack' (uppercase) and a string with 'Jack' and 'jack' (uppercase and lowercase). If the GetWordCount method is working properly, it returns a count of two instances of the search word. In order to fail this test on purpose, you first implement the test asserting that two instances of the search word 'Jack' aren't returned by the GetWordCount method. Continue to the next step to fail the test on purpose.
Open the Unit Tests panel on the right side of the screen. Select View > Tests from the menu.
Click the Dock icon to keep the panel open. (Highlighted in the following image.)
Click the Run All button.
The test fails, which is the correct result. The test method asserts that two instances of the inputString, 'Jack,' aren't returned from the string 'Jack jack' provided to the GetWordCount method. Since word casing was factored out in the GetWordCount method, two instances are returned. The assertion that 2 is not equal to 2 fails. This result is the correct outcome, and the logic of our test is good.
Modify the IgnoreCasing test method by changing Assert.NotEqual to Assert.Equal. Save the file by using the keyboard shortcut Ctrl+s, File > Save from the menu, or ctrl-clicking on the file's tab and selecting Save from the context menu.
You expect that the searchWord 'Jack' returns two instances with inputString 'Jack jack' passed into GetWordCount. Run the test again by clicking the Run Tests button in the Unit Tests panel or the Rerun Tests button in the Test Results panel at the bottom of the screen. The test passes. There are two instances of 'Jack' in the string 'Jack jack' (ignoring casing), and the test assertion is true.
Testing individual return values with a Fact is only the beginning of what you can do with unit testing. Another powerful technique allows you to test several values at once using a Theory. Add the following method to your TextUtils_GetWordCountShould class. You have two methods in the class after you add this method:
The CountInstancesCorrectly checks that the GetWordCount method counts correctly. The InlineData provides a count, a search word, and an input string to check. The test method runs once for each line of data. Note once again that you're asserting a failure first by using Assert.NotEqual, even when you know that the counts in the data are correct and that the values match the counts returned by the GetWordCount method. Performing the step of failing the test on purpose might seem like a waste of time at first, but checking the logic of the test by failing it first is an important check on the logic of your tests. When you come across a test method that passes when you expect it to fail, you've found a bug in the logic of the test. It's worth the effort to take this step every time you create a test method.
Save the file and run the tests again. The casing test passes but the three count tests fail. This outcome is exactly what you expect to happen.
Modify the CountInstancesCorrectly test method by changing Assert.NotEqual to Assert.Equal. Save the file. Run the tests again. All tests pass.

Adding a console app

In the Solution sidebar, ctrl-click the WordCounter solution. Add a new Console Application project by selecting the template from the .NET Core > App templates. Select Next. Name the project WordCounterApp. Select Create to create the project in the solution.
In the Solutions sidebar, ctrl-click the Dependencies node of the new WordCounterApp project. In the Edit References dialog, check TextUtils and select OK.
Open the Program.cs file. Replace the code with the following code:
Ctrl-click on the WordCounterApp project and select Run project from the context menu. When you run the app, provide values for the search word and input string at the prompts in the console window. The app indicates the number of times the search word appears in the string.
The last feature to explore is debugging with Visual Studio for Mac. Set a breakpoint on the Console.WriteLine statement: Select in the left margin of line 23, and you see a red circle appear next to the line of code. Alternatively, select anywhere on the line of code and select Run > Toggle Breakpoint from the menu.
ctrl-click the WordCounterApp project. Select Start Debugging Project from the context menu. When the app runs, enter the search word 'cat' and 'The dog chased the cat, but the cat escaped.' for the string to search. When the Console.WriteLine statement is reached, program execution halts before the statement is executed. In the Locals tab, you can see the searchWord, inputString, wordCount, and pluralChar values.
In the Immediate pane, type 'wordCount = 999;' and press Enter. This command assigns a nonsense value of 999 to the wordCount variable showing that you can replace variable values while debugging.
In the toolbar, click the continue arrow. Look at the output in the console window. It reports the incorrect value of 999 that you set when you were debugging the app.

You can use the same process to debug code using your unit test project. Instead of starting the WordCount app project, ctrl-click the Test Library project, and select Start Debugging Project from the context menu. Visual Studio for Mac starts your test project with the debugger attached. Execution will stop at any breakpoint you've added to the test project, or the underlying library code.

What's New in Visual Studio 2019 for Mac

Visual Studio 2019 for Mac Releases

March 3, 2020 - Visual Studio 2019 for Mac version 8.4.8
February 25, 2020 - Visual Studio 2019 for Mac version 8.4.7
February 19, 2020 - Visual Studio 2019 for Mac version 8.4.6
February 10, 2020 - Visual Studio 2019 for Mac version 8.4.5
February 4, 2020 - Visual Studio 2019 for Mac version 8.4.4
January 28, 2020 - Visual Studio 2019 for Mac version 8.4.3
January 21, 2020 - Visual Studio 2019 for Mac version 8.4.2
January 14, 2020 - Visual Studio 2019 for Mac version 8.4.1
January 8, 2020 — Visual Studio 2019 for Mac version 8.4

Visual Studio 2019 for Mac Blog Posts

Broadcom sdio wifi driver for mac. The Visual Studio Blog is the official source of product insight from the Visual Studio Engineering Team. You can find in-depth information about the Visual Studio 2019 for Mac releases in the following posts:

Release Highlights

This release adds support for .NET Core 3.1.100.
This release focuses on improving the overall experience using assistive technologies in Visual Studio for Mac.
This release brings additional features for .NET Core developers including:
- Scaffolding support for ASP.NET Core projects.
- The ability to develop and publish ASP.NET Core Blazor Server applications.
- Editor refinement, including support for .razor files.
- Pack support for creating NuGet packages from .NET Core library projects.

Known Issues

Refer to the Known Issues section.

Visual Studio 2019 for Mac version 8.4.8 (8.4.8.2)

released March 3, 2020

This service release fixes the following issues:

Templates are missing after updating Azure Functions templates and restarting Visual Studio for Mac.

Visual Studio 2019 for Mac version 8.4.7 (8.4.7.17)

released February 25, 2020

This service release addresses a number of additional accessibility issues and also fixes the following issues:

Report a problem dialog hidden when attaching a new file.
Cmd + . file search now has to be pressed twice.
Navigate to shortcut won't focus search text box.
Copy in a .resx file clears clipboard instead of copying.
Unable to copy/paste from Specflow .feature file.
Copy and paste from the old editor to the Xaml editor doesn't work.
launchSettings.json are changed on save.

Visual Studio 2019 for Mac version 8.4.6 (8.4.6.36)

released February 19, 2020

This service release addresses a number of additional accessibility issues and also fixes the following issues:

Can't expand a list item in the Review Solution and Commit page after doing a Update Solution command.

Visual Studio 2019 for Mac version 8.4.5 (8.4.5.19)

released February 10, 2020

This service release fixes the following issues:

MVC scaffolding doesn't include 'MVC Controller with views, using Entity Framework' scaffolder.
Scaffolding in a ASP.NET Core project uses LocalDB instead of Sqlite leading to PlatformNotFoundException.

Visual Studio 2019 for Mac version 8.4.4 (8.4.4.91)

released February 4, 2020

This release of Visual Studio 2019 for Mac brings a refreshed color palette, new icons, and updated warning and error status messages. Color contrast ratios for text and icons have been increased to improve clarity. Visual Studio for Mac also now fully suports macOS High Contrast Mode.

In addition to the visual changes, this release of Visual Studio 2019 for Mac has made a number changes to increase overall accessibility of the IDE. These include:

Improvements to focus order and visibility when using VoiceOver in the debugger, NuGet Package Manager and project options dialog.
Areas previously inaccessible by keyboard navigation, such as the pin and eye icon, are now navigable by keyboard.
Enhanced feedback from VoiceOver for debugger status.
'Project created' was not previously announced and now is.
Fixes to the NuGet Package Manager that allow keyboard access to the Browse, Installed, Update and Consolidate tabs.
VoiceOver now announces the selected version in the NuGet 'New version' dropdown.
VoiceOver now announces more information when using version control, the publish to Azure feature, and in a number of additional areas.
New PList editor source view implementation with improved keyboard navigation and VoiceOver support.

This service release also fixes the following issues:

We fixed an issue where .aspx files have no IntelliSense.

Visual Studio 2019 for Mac version 8.4.3 (8.4.3.12)

released January 28, 2020

This service release fixes the following issues:

We fixed an issue where it is not possible to install Android material on macOS Catalina.
We added support for launchSettings.json to Worker projects.
We fixed an issue where the debug mode is browser when creating a Worker Service project instead of default.

Visual Studio 2019 for Mac version 8.4.2 (8.4.2.59)

released January 21, 2020

This service release fixes the following issues:

We shipped the .NET Core January update (2.1.15 runtime and 3.1.101 SDK).
We fixed some additional accessibility issues with VoiceOver and keyboard navigation.
We fixed an issue where the Value Visualizer is always blank in 8.3.3 (Build 8).
We fixed an issue where inspecting nested variables in the hierarchy takes a long time.
We fixed an issue where Blazor debugging tool tips do not show any icons.
We fixed an issue where the Start Window shows when launching from Unity and can't be closed.
We fixed an issue where the 'Create' button doesn't work and .NET crashes.
We fixed an issue where Visual Studio for Mac cannot create .NET Core 3.1 projects after installing .NET Core 3.1.

Visual Studio 2019 for Mac version 8.4.1 (8.4.1.2)

released January 14, 2020

This service release fixes the following issues:

We fixed an issue where the bottom toolbar in the Xamarin Designer is being cut off.
We addressed a high volume crash.

Visual Studio 2019 for Mac version 8.4 (8.4.0.2657)

released January 8, 2020

New Features

Accessibility

We made a number of changes to improve the accessibility of Visual Studio for Mac in this release including:

Increasing contrast for text and icons throughout the IDE.
Improving keyboard navigation and shortcuts.
Refining focus order when navigating using assistive technologies.
Reducing the number of steps needed to move between certain elements on the Start Page while using VoiceOver.
The 'Pin button' on the Start Page can now be accessed with VoiceOver.
Improving VoiceOver dictation and navigation throughout the IDE in the following areas and more:
- Recently used templates page
- Font picker
- Document view tabs
- Global Search Results
- Code editor
- Code snippets
- Updater
- Version control
- Project options
Mitigating keyboard traps in Xamarin designer property panels and made previously inaccessible areas in those property panels accessible.
Completely rewriting previously inaccessible IDE components to make them accessible.

Web and Azure

We added support for ASP.NET Core Scaffolding.
We added support for editing .razor files.
We added support for provisioning Azure SignalR Service for Blazor Server projects during publish to Azure App Service.
We added support to Pack .NET Standard library projects.

Editor

All files should now open in the new editor unless legacy editor is explicitly needed.
We fixed some performance leaks in the editor.
We updated to use the latest FSharp.CompilerService.
We improved support for .csx files.
We have added support for TypeScript 3.7, with new features like Optional Chaining and Nullish Coalescing.
Blazor support has improved IntelliSense and debugger integration.

Shell

We have added a native and fully accessible (keyboard and VoiceOver) property pad control from the Android designer to the shelland enabled it by default for all solution items.

Debugger

We have implemented native controls for the debugger tooltips, locals pad and watch pads, and the exception caught dialog which allowed for us to re-enable pinned watches in the editor.

Xamarin

XAML Hot Reload for Xamarin.Forms is now on by default and built-in to the IDE. To learn more about XAML Hot Reload, see the XAML Hot Reload documentation.
You can now create Android App Bundles when publishing your Android applications in Visual Studio. App Bundles provide users with with optimized APKs per their device specifications when downloading an app from the Google Play Store or various Android App Stores.
You can now use an AndroidX migration wizard to convert your existing Android application to AndroidX from the Android Support Library.
You are now provided a set of common issues when editing your layouts inside the Android designer.

Installer

The installer now supports dark theme.
The installer will now clean up older minor versions of .NET Core that were previously installed using the installer.
HAXM and AVD creation support have been removed from the installer. Creation of AVDs should be done using Visual Studio for Mac's device manager.
The installer, and Visual Studio for Mac, no longer supports macOS Sierra.

Bug Fixes

Shell and Tools

We fixed the following issues with the IDE:

We added notarization support for macOS Catalina.
Dialog locations are inconsistent.
The accounts Window is always on top, even when leaving Visual Studio for Mac.
The IDE opens in the wrong Desktop if the Start Window is dragged to a new desktop.
'New' is cut off at the bottom in the Start Window in some languages.
If you choose not to sign in on first run, you'll continually get prompted through the first run experience.
Hitting return in a search field doesn't search.
Tab key to change between views seems to be broken.
Visual Studio Community lacks UTF-8 (no signature) format.
Preferences menu item does not open.
We fixed an issue where extension manager cannot be closed once opened.

Editor

We fixed the following issues with editing source code:

The IDE would re-default to 'case sensitive' search.
When creating a breakpoint, selected lines would not be auto-filled.
When copy/pasting a word-wrapped line, only the first line would be copied.
The emoji selector would not display.
Commenting commands does not work in .js/.ts files.
We fixed an issue where code formatting in .js/.ts files could delete user code unexpectedly.
The insert line command (shift+enter) would not work.
The 'Show quick info' and 'Focus Document' commands would not work.
We removed some obsolete refactorings.
We fixed an issue where font weight was being ignored.
More msbuild files (such as .props) are now syntax-highlighted.
We fixed an issue where editor commands sometimes stopped working when tabs were moved into separate windows.
We fixed an issue where files sometimes opened scrolled to the right.
We fixed an issue where some tooltips were missing from Find.
We fixed an issue where quick info tooltips were not displayed for some properties.
Blazor support received several fixes to productivity features such as Go To Defintion and debugger tooltips.
The IntelliSense completion list now responds properly to text zoom commands.

Web and Azure

We fixed the following issues with .NET Core support:

The Blazor template has been added to the New Project dialog.
Razor component and Worker Service templates added to New Item dialog.
Launch settings were previously generated with https but project doesn't support https.
When creating a new ASP.NET Core project the port number was not unique.
We improved ASP.NET Core project loading times, especially in projects with extensive File Nesting.
We fixed an issue where updating to 3.0 Azure Functions Templates in the Project Creation Wizard causes Azure Functions to disappear as an option.

We fixed the following issues with Azure Functions support:

Azure Functions was missing templates for AzureFunctionsVersion, v2.

Version Control

We fixed the following issues with Version Control:

Cancelling an SVN checkout can accidentally delete user files.

Project System

We fixed the following issues with Projects:

Manually adding DefaultTargets to csproj gets overridden when VS modifies the project.
Inconsistent naming for removal on files and projects.
Project context menu is missing 'Add Reference'.
Renaming a file in the solution pad does not re-apply nesting rules.
Change title of window from 'Edit References' to 'References'.
Project model reports wrong references for certain projects.
We fixed an issue where Define Constants would not be defined correctly when defined in imported projects.
We fixed an issue where Visual Studio for Mac could get stuck in a loop saving a project that was under source control.

Debugging

We fixed the following issues with Debugging:

We added a missing 'Debug All Tests' command.
Hovering over an expression may change the value of variables in the .NET Core debugger.
Opening the Exception Caught dialog makes the IDE hang.
We fixed an issue where pinning properties in debug doesn't work.

Xamarin

We fixed the following issues with the Xamarin support:

Visual Studio for Mac reporting iOS specific classes, methods and enums unavailable in iOS.
We improved an unhelpful error message when signing an archive for distribution.
We fixed an issue where document outlines in storyboards are empty.
We fixed an error where the Xamarin.Forms multiplatform templates would add files to disk, but not add them to the solution itself.
We fixed an issue where Visual Studio for Mac was failing to upload Android archives to the Google Playstore with the message: 'API has been deprecated'.

Testing

We fixed the following issues with Testing:

'Show Test Source Code' does nothing if you right click a test class name.
'Run Test' does not run the test if a compile is required.
We fixed an issue where the debugger doesn't open a file on failure during test debugging.

Installer

We squashed a handful of behind-the-scenes bugs in the installer.

Updater

We fixed the following issues with the updater:

Progress indicator was empty after an unsuccessful download.
Updater does not wait for IDE to exit before installing updates.

Known Issues

After adding a new file using the Razor Component file template, the project may fail to build. The issue is caused by some unneeded elements in the project file (.csproj file), remove elements referencing the new file from the project file, and the project should build successfully.
When developing ASP.NET Core projects, if .NET Core SDK 3.1 Preview is installed, https connections may be refused. The browser may not launch, or when using docker, certificate errors are shown. To workaround this, run the following commands in the terminal; dotnet dev-certs https —clean and then dotnet dev-certs https —trust.
Pressing backspace does not delete a watch from the Watches pad.

Feedback

We would love to hear from you! You can report a problem through the Report a Problem option in Visual Studio for Mac IDE.You can track your feedback, including suggestions, in the Developer Community portal.

Top of Page