In general, to be honest, R# feels smarter. But another aspect here is that with R#, I rarely have to leave my current context, pretty much everything is available immediately from where I am. 

• A bug is fixed in loop unroller which might lead to wrong condition codes being generated in the unrolled loop.
• Fixed a bug that caused ServiceHub.Host.CLR.x64 to stop working.
• Fixes issue in Chinese version of compiler errors C4533 and C2362 which resulted in incorrect order of string substitution for those languages.
• Improved stability of the Diagnostic Tools and Performance Profiler.
• Code generation problem causing crash with pure virtual destructor in const object
• Fixed a constant evaluation regression from 16.5 Preview 2
• Fixed an issue where MacOS couldn't be paired.
• Fixed an issue where the Diagnostic Tools while debugging and Performance Profiler fail to launch on XBox devices. 

Parse those pesty unreadable long stack traces. Stack Trace Explorer provides syntax highlighting and easy navigation to elements in the stack trace. 

- if...else syntax in component HTML templates
- Stand alone animation module
- TypeScript's StrictNullChecks compliancy
- Angular Universal adoption by team to live in core
- Performance boost with FESM

 The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.
Requested URL: /Service/1/ewr/

public static void RegisterRoutes(RouteCollection routes)
{
   routes.MapPageRoute( "Service" ,  "Service/{ID}/{ProductTitle}" ,  "~/Service.aspx" );
}

void Application_Start( object sender, EventArgs e)
{
   RegisterRoutes(RouteTable.Routes); 
}

protected void LinqDataSource1_Selecting( object sender, LinqDataSourceSelectEventArgs e)
{
   int ID =  int .Parse(Page.RouteData.Values[ "ID" ].ToString());
   e.Result = db.Product.Where(p => p.ProductID == ID).FirstOrDefault(); 
}

update-package T4MVC -Reinstall -ProjectName Decision.Web
update-package Microsoft.AspNet.Mvc -ProjectName Decision.Web
update-package Microsoft.Web.Infrastructure -ProjectName Decision.Web
Install-Package RazorGenerator.Mvc
Enable-RazorGenerator
Redo-RazorGenerator

First it is important to recognize that the .NET Framework is not the same as .NET Core. The .NET Framework is effectively now in maintenance mode , and all innovation is occurring in the open source .NET Core now and into the future. So step one to remaining relevant is to understand .NET Core (and the closely related .NET Standard). 

Note that FASTER is not directly comparable to Redis, as FASTER is not just a cache. FASTER can index and access data larger than memory, as well as take consistent checkpoints for recovery, more like a persistent hash key-value store + cache combination. FASTER is multi-threaded and latch-free as well, which gives it very high performance on a single machine.

Some recently completed and ongoing/future work items on our roadmap can be found at https://microsoft.github.io/FASTER/roadmap. For instance, in FASTER C#, we recently added log compaction, support for deletes, inline variable-sized allocations, and a read cache.