Today, we are releasing updates to the .NET Core SDK, included in Visual Studio 2017 RC. You can also install the .NET Core SDK for use with Visual Studio Code or at the command line, on Windows, Mac and Linux. Check out the Visual Studio blog to learn more about this Visual Studio 2017 update. 

Entity Framework Migrations are handled from the package manager console in Visual Studio. The usage is shown in various tutorials, but I haven’t found a complete list of the commands available and their usage, so I created my own. There are four available main commands 

SQL Generation Improvements in Entity Framework 7

 Select * from sys.dm_os_buffer_descriptors

 select * from sys.dm_os_buffer_pool_extension_configuration

 ALTER SERVER CONFIGURATION
SET BUFFER POOL EXTENSION ON
 (FILENAME = 'd:\BufferPoolExt.BPE', SIZE = 1GB);

 ALTER SERVER CONFIGURATION
SET BUFFER POOL EXTENSION ON
 (FILENAME = 'd:\BufferPoolExt.BPE', SIZE = 10GB);

 Could not change the value of the 'BPoolExtensionPath' property

 ALTER SERVER CONFIGURATION
SET BUFFER POOL EXTENSION OFF

Query cache parameters can be configured from the app/web.configuration file  

Rider 2018.1 adds support for Roslyn analyzers and Entity Framework, introduces XAML preview, takes Unity integration to a whole new level, improves debugger with Memory view and other updates, evolves F# and NuGet support. 

BenchmarkDotNet v0.10.13 has been released! This release includes:

• Mono Support for DisassemblyDiagnoser: Now you can easily get an assembly listing not only on .NET Framework/.NET Core, but also on Mono. It works on Linux, macOS, and Windows (Windows requires installed cygwin with obj and as). (See #541)
• Support ANY CoreFX and CoreCLR builds: BenchmarkDotNet allows the users to run their benchmarks against ANY CoreCLR and CoreFX builds. You can compare your local build vs MyGet feed or Debug vs Release or one version vs another. (See #651)
• C# 7.2 support (See #643)
• .NET 4.7.1 support (See 28aa94)
• Support Visual Basic project files (.vbroj) targeting .NET Core (See #626)
• DisassemblyDiagnoser now supports generic types (See #640)
• Now it's possible to benchmark both Mono and .NET Core from the same app (See #653)
• Many bug fixes (See details below) 

These are the customer-reported issues addressed in 15.7.2:

• With 15.7, users installing an extension on the command line with a nested extension may see an error installing. This has been addressed in the 15.7.2 servicing release.
• Anaconda fails to uninstall during upgrade and issues warning (Error 87).
• The SSDT 15.6.0 Installer configuration registry key could not be opened..
• Editor performance Issues when editing JavaScript.
• The Code Coverage functionality in Visual Studio 2017 ignores async methods.
• Missing atls.lib in arm/arm64 after update.
• Test Explorer no longer greys out the previously run unit tests.
• Version 15.7.1 debugs .aspx App in a new Chrome instance even if JavaScript debugging is disabled.
• 15.7 compiler fails with Folly.
• ASP project keeps running after closing the web page.
• Chrome Debugger not working and shows an error message, however, the debugger buttons stay active. .
• Rename Python from Rename on the Refactor menu no longer works.
• Visual Studio Installer doesn't work correctly in low disk space conditions.
• Debugger links to browser when previously not set.
• Problems with template argument deduction for class templates.
• C++ constexpr string_view == fails to compile.
• A regression in Type Providers which use native resources (e.g., FSharp.Data.TypeProviders) has been fixed.
• You can now add files to F# ASP.NET Core projects from the UI.
• Listening to Microsoft-Extensions-Logging causes VS diagnostic events window to disconnect with an error message has been fixed in Service Fabric Tools. 

VSTest is a very extensible unit test execution framework.  The base engine, discovers tests and runs them.  It can parallelize across cores, provides process isolation and can integrate with Visual Studio.  It has extensibility for different test frameworks, code coverage, test impact analysis, data collection, test result reporting and much more.