Microsoft Edge Mac Release Date
Right on schedule, Microsoft today launched its new Edge browser based on Google’s Chromium open source project. You can download Chromium Edge now for Windows 7, Windows 8, Windows 10, and macOS directly from microsoft.com/edge in more than 90 languages. This is Edge 79 stable, for those who like tracking version numbers. Edge 80 is slated to arrive in early February, and afterwards Microsoft will stick to a six-week cadence for stable releases, just like with Chrome.
Microsoft has yet to lay out which features will ship in Edge 80, Edge 81, and so on. When asked what to expect from the next few Edge releases, a spokesperson said developers and users should use the beta releases as an indication. If you want to peek at the pipeline, download one of the Edge Insider Channels: Beta (updated every six weeks), Dev (updated weekly), or Canary (updated daily). Insider builds can be installed side by side with Edge stable. Update: Microsoft has published a support article that lists features in the works and requests that are not currently on the roadmap.
Office for homeIf you have an product and it came with a product key., before installing for the first time (or it if you have Office 365 Home), you need to redeem your product key first. Go to and sign in with an existing or new. Instalar microsoft office en mac. and then enter your product key to redeem it. Redeeming your key is what adds your Microsoft account to Office and you only have to do this once.
It’s worth noting that the new Microsoft Edge, as Microsoft is calling it, has a fresh logo. For the first time in decades, Microsoft’s browser is not denoted with a blue “e” — the logo is a wave, presumably for “surfing” the web.
Microsoft Edge Mac Release Date 2017
Nov 13, 2018 The new Microsoft Edge is based on Chromium and will be released January 15, 2020. It's compatible with all supported versions of Windows, and with macOS (version 10.12 Sierra or higher). When you download this browser, it replaces the legacy version of Microsoft Edge on Windows 10 PCs. Nov 05, 2019 At the Ignite developer conference, Microsoft noted that Edge browser’s final version release date is slated for January 15. Edge development is decoupled from Windows, so you would be able to.
Aug 02, 2018 When using OneNote for Mac version, MacBook Pro crashed. After rebooting MacBookPro, it reported Microsoft OneNote had caused the crash. Then every time when i open OneNote, app crashed immediately. Reinstalling OneNote Mac app via Appstore or clearing caches, does not fix the issue. OneNote keeps crashing on start. Mar 19, 2020 OneNote for Mac crashes on start Meanwhile, from the log, the version of OneNote on your Mac is 15.37.0.17080500 while the lasted version number is 15.37.0.17081500 from this page. If OneNote still crash, please download and install from the page mentioned above to check the result. 
Today’s debut has been a long time coming. Back in December 2018, Microsoft embraced Chromium for Edge development on the desktop. In April 2019, Microsoft released the first Chromium Edge builds (daily Canary and weekly Dev channels), and the Chromium Edge Beta channel followed in August 2019. In November 2019, Microsoft launched the Chromium Edge release candidate and positioned Edge and Bing as “the browser and search engine for business.” Microsoft today shared that the Insider builds have gotten “millions” of downloads. Now we’ll see if the stable release can get traction.
Features and performance
Microsoft plans to ship more consumer Edge features later this year, but this launch is largely targeted at businesses. That means AAD support, Internet Explorer mode, and Microsoft Search in Bing integration. Business and education IT administrators can download offline packages and policies for Chromium Edge. Many businesses already use Chrome and at least one Microsoft browser (Internet Explorer and/or Edge) — Microsoft is hoping these features will get them to switch to using just Chromium Edge.
Business features aside, there’s also support for Chrome-based extensions, 4K streaming, Dolby audio, inking in PDF, and privacy tools. For the last one, it’s worth noting that tracking prevention is on by default and offers three levels of control, like Firefox’s tracking protection.
Chrome extension support is probably the most important feature for most users. By default, extensions that have been ported over to Edge can be downloaded from the Microsoft Store. Chromium Edge also has an option to “Allow extensions from other stores” to get Chrome extensions from the Chrome Web Store.
There are still a few features missing from Chromium Edge, most notably history sync and extension sync. Microsoft is working on these and some other inking functionality that it still wants to port from legacy Edge, as Microsoft is calling it.
Microsoft also claims that Chromium Edge is twice as fast as legacy Edge. Curiously, the team isn’t making any claims against other browsers — at least not yet. In fact, our own testing shows Chromium Edge has solid performance.
The bigger picture here is that by leaning on Chromium, Microsoft no longer has to worry about “fixing” its underlying browser engine EdgeHTML. The company can instead improve Chromium itself, which helps all browsers that use the codebase, not just Chromium Edge. Microsoft says over the past year it has made more than 1,900 contributions to Chromium across areas like accessibility, touch, speech, and digital inking.
On the flip side, Edge is now just another Chromium-based browser. That makes it all the harder to offer a differentiated experience. Having failed with EdgeHTML, Microsoft figures Chromium is worth a shot.
Installing the new Edge: Manual or Automatic
If you’re running Windows 10 and don’t install Edge manually, you’ll eventually get it in a future update. Microsoft plans to start rolling out the new Edge “in the coming weeks,” starting with a subset of Windows Insiders in the Release Preview ring. The process will ramp up to more users “over the next several months.” It will be made gradually available on Windows Update and offered to additional devices “as data and feedback indicate that users are having a good experience.” Microsoft currently has no plans to automatically upgrade Managed, Enterprise, Education, or Workstation Pro Edition devices (documentation). If you want to block automatic delivery of the new Edge to Home and Pro devices, you can do so either via policies or the Blocker Toolkit.
When you install the new Edge on Windows 10, it will replace legacy Edge. Any shortcuts you have on the desktop, taskbar, or Start Menu will be updated to new Edge. The executable for legacy Edge is technically hidden, but it will be removed eventually. Your favorites, passwords, form fill information, and basic settings will carry over from legacy Edge to new Edge automatically. If you have Chrome or Firefox installed, new Edge will ask if you want to import those settings from there. Web apps built on EdgeHTML and Edge preview channels will continue to work without interruption. Depending on how up-to-date your Windows 10 installation is, you may be asked to install additional updates. A future version of Windows 10 will skip all this and include new Edge by default.
When you install new Edge on Windows 7, Windows 8, and macOS, it will work just like installing any other browser. New Edge will not replace whatever you have as the default (whether that’s Internet Explorer, Safari, or a third-party browser). Yesterday, Microsoft ended support for Windows 7, so it’s notable the company is still releasing new Edge for the decade-old operating system. It shows just how big Windows 7 still is — about one in four computers run it.
On Android and iOS, new Edge will replace old Edge automatically. That said, not much is new on mobile — Edge already uses Blink/Chromium on Android and WebKit/WKWebView on iOS. But you can expect the new logo, similar user interface to the desktop versions, and tracking prevention on iOS (coming soon to Android). More desktop features will make their way to Android and iOS over time.
Lastly, Microsoft’s FastTrack and App Assure programs cover Chromium Edge. The former means Microsoft will help you deploy Edge to your organization at no extra charge with an eligible subscription to Microsoft 365, Azure, or Dynamics 365. The latter means if your sites work in Internet Explorer 8 and above, Chrome, or legacy Edge, then they’ll work on the new Edge. If not, Microsoft will help you fix them at no additional cost.
-->Developer Community System Requirements Compatibility Distributable Code Documentation Blogs Servicing
Click the button to download the latest version of Visual Studio 2019 for Mac. For information on the system requirements see the see Mac System Requirementsand Mac Platform Targeting and Compatibility guides.
For instructions on installing and updating Visual Studio 2019 for Mac, see theInstall Visual Studio for Mac guide.
To learn more about other related downloads, see the Downloads page.
What's New in Visual Studio 2019 for Mac
Visual Studio 2019 for Mac Releases
- April 7, 2020 - Visual Studio 2019 for Mac version 8.5.2
- April 1, 2020 - Visual Studio 2019 for Mac version 8.5.1
- March 16, 2020 - Visual Studio 2019 for Mac version 8.5
Visual Studio 2019 for Mac Blog Posts
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
In this release of Visual Studio 2019 for Mac we replaced our old Git implementation, refreshed our color palette and icons, and we addressed a number of issues with the debugger, test tools, and project system.
Known Issues
Refer to the Known Issues section.
Visual Studio 2019 for Mac version 8.5.2 (8.5.2.13)
released April 7, 2020
Visual Studio for Mac 8.5 Service Release 2 addresses the following:
- A user navigating with the keyboard can not navigate to the 'Reset' button in the Xamarin Designer Property Panel.
- We fixed an issue where commits do not work in projects using Git worktree.
- We fixed an issue where Visual Studio for Mac may become unresponsive when popping a stash in a project under Git.
- We fixed an issue where projects pushed to GitHub fail to show new files or directories.
Visual Studio 2019 for Mac version 8.5.1 (8.5.1.42)
released April 1, 2020
This release includes the following updates:
- Support for Xcode 11.4.
- We fixed an issue with increased UI delays when working with Xamarin.iOS projects.
- We fixed an issue where Visual Studio for Mac shows in current window on Mac when selected.
- We fixed an issue where Visual Studio for Mac goes to background when switching virtual desktops.
- We fixed an issue where Version Control does not recognize newly added files in a folder.
- We fixed an issue where Visual Studio for Mac tells me to install Command Line Tools but it's already installed.
Visual Studio 2019 for Mac version 8.5 (8.5.0.3183)
released March 23, 2020
New Features
Accessibility
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 staus.
- After creating a project using the New Project Dialog, the IDE now accurately announces “project created” status message to VoiceOver users.
- 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 'New version' dropdown.
- VoiceOver now announces more information when using version control, the publish to Azure feature, and in a number of additional areas.
Edge For Mac Release Date
Version Control
We replaced our old Git implementation with a wrapper around the official Git command line client, which is already used by Visual Studio on Windows, in order to improve the overall performace and reliability of Git support in the IDE. The new Git support depends on the official git client. The recommended way to install Git is to install it as part of the Xcode Command Line Tools by running xcode-select --install in the Terminal app (Xcode does not need to be installed).
Debugger
- Function breakpoints can now be edited.
- We have improved stepping performance in .NET Core projects.
Editor
- We updated Light & Dark themes to match Visual Studio.
Installer
- We added a new item to the carousel to allow users to sign up for ASP.NET Core tips.
- We added support to implement CLI tools required by version control.
- We integrated error reporting to aid in improving future quality.
Web and Azure
- We bumped to the latest .NET Core release.
- We added authentication support in the New Project Dialog for ASP.NET Core projects.
- We added support for v2/v3 of Azure Functions runtime.
NuGet
- We bumped NuGet to 5.4.
Xamarin
- You can now see a hierarchy of your Xamarin.Forms controls in the Document Outline pane. On Windows, it can be opened with Ctrl+Alt+T (View > Other Windows > Document Outline). On Mac, you can open it via Views > Pads > Document Outline.
- When debugging multiple projects at the same time, you can now use XAML Hot Reload simultaneously on both targets. For example, you can use XAML Hot Reload to see how your XAML change looks on both an iOS and Android phone at the same time. Learn more about debugging multiple process in the Visual Studio 2019 documentation.
- You can now set the default iOS Designer in Visual Studio for Mac. Any changes made in the Xcode storyboard designer will be synchronized back to Visual Studio for Mac automatically.
- You can now apply Android resource changes at runtime using Android Apply Changes. This feature allows you to quickly see changes made to your Android resource files (XML layouts, drawables, etc) on an Android device or emulator without requiring the application to be restarted.
- You can now generate your own custom profiles when using startup tracing in your Android application. This provides you an even more performant startup experience with a minimal increase to APK size.
- You can now generate Xamarin.Android bindings against Kotlin libraries.
- You can now use the Google Manifest Merger when merging AndroidManifest.xml files in your Android projects. This allows you to customize how each manifest and its contents will be merged. For more details on rules that can be applied, please see Merge multiple manifest files.
- The option to use shared project has been removed when creating a new Xamarin.Forms app. New Xamarin.Forms apps will now use .NET Standard to ensure the best development experience.
Bug Fixes
Shell
- We fixed an issue where the start window shows when launching from Unity and cant be closed.
- We fixed an issue where right clicking a tab causes Visual Studio for Mac to crash
Editor
- We fixed an issue where Code Analysis ruleset is ignore and a bunch of conflicting warnings are presented by Visual Studio for Mac.
- We fixed an issue where method documentation is gone.
- We fixed an issue where there is no syntax highlighting and autocompletion in T4 templates.
- We fixed an issue where copy and paste did not work between certain types of files 123.
- We fixed an issue with color contrast during field renaming with the new theme.
- We improved VoiceOver accessibility for the Quick Fixes and Refactorings menu.
- We fixed a crash viewing certain file types on macOS 10.13.
Debugger
- We fixed an issue where value visualizer is always blank.
- We fixed an issue that caused inspecting nested variables in hierarchy to take longer than expected.
- We fixed an issue where viewing variables with async methods shows nothing.
- We fixed an issue where the debugger would not show variable inspection icons correctly.
- We fixed an issue that prevented watched expressions from being removed with the backspace key.
- We fixed an issue where Visual Studio for Mac does not break on the line of an unhandled exception in .NET Core projects.
- We fixed an issue where the DataTip (variable inspect) font size looks small.
- We fixed an issue where the pin variable icon during debugging is initially missing.
- We fixed an issue where the UI buttons for stepping are slow to respond and make stepping feel very slow.
- We fixed an issue where values might not be able to be copied from the locals and watch pads.
- We fixed an issue where the .NET Core debugger would not show System.Drawing.Color values.
- We fixed an issue where the Attach to Process dialog shows no processes.
- We fixed an issue where the Debugger stops on lines without a breakpoint set (in multiple startup projects).
- We fixed an issue where watched expressions are removed after trying to rename them in the Watch Pad.
- We fixed an issue where saving edits from the Text visualizer during debugging does not save changes.
- We fixed an issue where the Locals pad is not updating after editing variable value in the visualizer.
- We fixed an issue that could cause spurious scrolling when stepping through code.
Project
- We fixed an issue where StyleCop rules are ignored.
- We fixed an issue where Visual Studio for Mac automatically closes my solution claiming that a file is gone - but it is not.
- We fixed an issue where an occasional dialogue about mono-sgen32 not optimised for my Mac appears.
- We fixed an issue where creating a project with a name that already exists in one folder disables the dialog.
- We fixed an issue where “mono-sgen32” is not optimized for your Mac and needs to be updated.
- 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.
- We fixed an issue where the Solution Explorer is showing duplicate files.
- We fixed an issue where deleting file from SDK style project adds unnecessary data into .csproj file.
- We fixed an issue where the wrong version of a multi-target project is referenced in a .NET Framework project.
- We fixed an issue where there is no IntelliSense for NUnit types when adding a new NUnit project to an existing solution.
- We fixed an issue that prevented a file from being removed from the project when the file was missing.
- We fixed an issue that would cause some MSBuild properties to not be fully evaluated.
- We fixed an issue where linked files could not be removed from the project.
- We fixed an issue where duplicate files are shown in the Solution window.
Version Control
- We fixed an issue where the version control file drop down is (partially) broken.
- We fixed an issue where libhostfxr.dylib is not signed.
- We fixed an issue where the status of modified files was not updated after saving or reverting changes.
- We fixed an issue with the overall performance when working with solutions inside a git repository.
- We fixed an issue with macOS continously prompting to install Xcode command line tools.
- We fixed an issue where Git 'Authors' incorrectly shows the 1st line as modified.
- We fixed an issue where renaming a file can cause a UI hang.
- We fixed an issue where Switch to Branch menu is missing.
- We fixed an issue where a new file was not shown in the Status View if it was not added/staged manually.
- We fixed an issue where there are issues with BOM in the Status View diff.
Web Tools
- We fixed an issue where custom parameters do not persist.
- We fixed an issue where .NET Core web application MVC template creates multiple launchSettings.json and appsettings.json files.
- We fixed an issue where Visual Studio for Mac 2019 has no controller scaffolding with views.
- We fixed an issue where launchSettings.json are changed on save.
NuGet
- We fixed an issue where unable to get repository signature information for source.
- We fixed an issue where NuGets are not refreshing.
Test Tools
- We fixed an issue where the test heirarchy is jumbled and breaks namespace names.
- We fixed an issue with weird nesting in the 'Unit Tests' pad.
- We fixed an issue that can cause test discovery to fail.
- We fixed some additional nested issues related to weird nesting in 'Unit Tests' explorer/window.
Known Issues
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.