WebSocket is real-time communication protocol we can use to make UI in browser to send and receive messages from server over real-time communication channel. WebSocket is also supported by ASP.NET Core. This blog post demonstrates how to build simple browser based chat room on ASP.NET Core and WebSocket.
Want to hear how Stack Overflow uses ASP.NET Core in production? Come watch Nick Craver (Architecture Lead, Developer, Site Reliability Engineer & DBA) explain and take your live questions and answers!
Learn how to build enterprise applications using ASP.NET Core 3 and following the principles of Clean Architecture. This talk provides practical guidance and will cover architecture, technologies, tools, and frameworks.
The following article describes how to developing APIs using Actor model in ASP.NET Core. It will show some benefits of build APIs using actor model pattern and some good reasons about adopting Orleans.NET as actor model framework
In this post, I'll describe how controllers are created in ASP.NET Core MVC using the IControllerActivator, the options available out of the box, and their differences when it comes to dependency injection.
Last year, Mike Rousos posted a great post about token authentication on the .NET blog and demonstrated how you could leverage ASP.NET Core Identity and OpenIddict to create your own tokens in a completely standard way.
namespace Core1RtmEmptyTest.Services
{
public interface IMessagesService
{
string GetSiteName();
}
public class MessagesService : IMessagesService
{
public string GetSiteName()
{
return "DNT";
}
}
} 
{
"dependencies": {
// same as before
"Core1RtmEmptyTest.Services": "1.0.0-*"
}, public void Configure( IApplicationBuilder app, IHostingEnvironment env, IMessagesService messagesService)
public void Configure(
IApplicationBuilder app,
IHostingEnvironment env,
IMessagesService messagesService)
{
app.Run(async context =>
{
var siteName = messagesService.GetSiteName();
await context.Response.WriteAsync($"Hello {siteName}");
});
} System.InvalidOperationException No service for type 'Core1RtmEmptyTest.Services.IMessagesService' has been registered. at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType) at Microsoft.AspNetCore.Hosting.Internal.ConfigureBuilder.Invoke(object instance, IApplicationBuilder builder) System.Exception Could not resolve a service of type 'Core1RtmEmptyTest.Services.IMessagesService' for the parameter 'messagesService' of method 'Configure' on type 'Core1RtmEmptyTest.Startup'. at Microsoft.AspNetCore.Hosting.Internal.ConfigureBuilder.Invoke(object instance, IApplicationBuilder builder) at Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication()
public class Startup
{
public void ConfigureServices(IServiceCollection services)
{
services.AddTransient<IMessagesService, MessagesService>();
} 
{
"dependencies": {
// same as before
"StructureMap.Dnx": "0.5.1-rc2-final"
}, public class Startup
{
public IServiceProvider ConfigureServices(IServiceCollection services)
{
services.AddDirectoryBrowser();
var container = new Container();
container.Configure(config =>
{
config.Scan(_ =>
{
_.AssemblyContainingType<IMessagesService>();
_.WithDefaultConventions();
});
//config.For<IMessagesService>().Use<MessagesService>();
config.Populate(services);
});
container.Populate(services);
return container.GetInstance<IServiceProvider>();
} 
<configuration>
<runtime>
<gcServer enabled="true"/>
</runtime>
</configuration> <PropertyGroup> <ServerGarbageCollection>true</ServerGarbageCollection> </PropertyGroup>
<configuration>
<runtime>
<gcConcurrent enabled="true" />
</runtime>
</configuration> <configuration>
<runtime>
<gcConcurrent enabled="false" />
</runtime>
</configuration> | Server GC | Non-Concurrent Workstation | Concurrent Workstation | |
| Maximize throughput on multi-processor machines for server apps that create multiple threads to handle the same types of requests. | Maximize throughput on single-processor machines. | Balance throughput and responsiveness for client apps with UI. | Design Goal |
| 1 per processor ( hyper thread aware ) | 1 | 1 | Number of Heaps |
| 1 dedicated GC thread per processor | The thread which performs the allocation that triggers the GC. | The thread which performs the allocation that triggers the GC. | GC Threads |
| EE is suspended during a GC. | EE is suspended during a GC. | EE is suspended much shorter but several times during a GC. | Execution Engine Suspension |
<gcServer enabled="true"> | <gcConcurrent enabled="false"> | <gcConcurrent enabled="true"> | Config Setting |
| Non-Concurrent Workstation GC | On a single processor (fallback) |
dotnet publish -r win10-x64 /p:PublishSingleFile=true
| With ReadyToRun images | IL-only Application |
| Startup time: 1.3 seconds | Startup time: 1.9 seconds |
| Memory usage: 55.7 MB | Memory usage: 69.1 MB |
| Application size: 156 MB | Application size: 150 MB |
<PublishReadyToRun>true</PublishReadyToRun>
dotnet publish -r win-x64 -c Release
<PublishTrimmed>true</PublishTrimmed>
dotnet publish -r win-x64 -c Release
Add Mono to the dotnet\runtime repository
