1. .NET has better Performance
2. Node.js requires to mix & match languages to compensate for performance
3. C# is an amazing language
4. Best tooling available
5. Easier built-in development loop
6. Stable ecosystem
7. Compliance, privacy, and security
Building off the improvements to the managed sockets implementation in .NET Core we have changed the default transport in Kestrel from libuv to sockets.
LokiJS is an in-memory database which prioritises performance over everything. LokiJS supports field indexing for faster document access and performs really well (near 500,000 ops/s) on those. Its built-in DynamicView class also enables to utilize indexes on data subsets for even faster performance.
RyuJIT Just-in-Time Compiler Optimization Enhancements
using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc.Razor;
namespace Core1RtmEmptyTest.StartupCustomizations
{
public abstract class MyCustomBaseView<TModel> : RazorPage<TModel>
{
public bool IsAuthenticated()
{
return Context.User.Identity.IsAuthenticated;
}
#pragma warning disable 1998
public override async Task ExecuteAsync()
{
}
#pragma warning restore 1998
}
} @inherits Core1RtmEmptyTest.StartupCustomizations.MyCustomBaseView<TModel>
Is Current User Authenticated? @IsAuthenticated()
@functions
{
public string Test()
{
return message;
}
readonly string message = "test";
} @Test() <br /> @message
@inject Microsoft.AspNetCore.Hosting.IHostingEnvironment Host;
[Microsoft.AspNetCore.Mvc.Razor.Internal.RazorInjectAttribute]
public Microsoft.AspNetCore.Hosting.IHostingEnvironment Host { get; private set; } <div> Running in @Host.EnvironmentName </div>
@inject IOptions<SmtpConfig> Settings;
Full Stack ASP.NET Core 2.0 MVC Forum Build
Topics Covered:
- Setting up a new ASP .NET Core 2.0 MVC web application with Identity user authentication in Visual Studio
- Separating Web, Services, and Data Access Layers in our solution
- Setting up tests with NUnit and .NET Core virtual in-memory database
- Debugging / Fixing bugs
- Implementing the MVC (Model-View-Controller) pattern
- Dependency Injection of Services into our Controllers
- Using input forms to pass data from our Views to our Controllers
- Azure file storage for Profile Image uploads
- Azure SQL database hosting
- SQL Database seeding for starting the application with a super-user
- Code-first database migrations
- Writing SQL queries to inspect data in our database
- Deploying the application to Azure.
