The reason for an explicit interface implementation is to avoid name collisions with the end result being that the object must be explicitly cast to that interface before calling those methods. You can think of these methods not as being public on the class, but being tied directly to the interface. There is no reason … Read more
I wont be wrong if I think that await will release the calling thread but Task.Result will block it, would it be right? Generally, yes. await task; will “yield” the current thread. task.Result will block the current thread. await is an asynchronous wait; Result is a blocking wait. There’s another more minor difference: if the … Read more
I recommend you start out with my intro to async/await and follow-up with the official Microsoft documentation on TAP. As I mention in my intro blog post, there are several Task members that are holdovers from the TPL and have no use in pure async code. new Task and Task.Start should be replaced with Task.Run … Read more
I have worked on a project that had similar pluggable architecture like the one you described and it used the same technologies ASP.NET MVC and MEF. We had a host ASP.NET MVC application that handled the authentication, authorization and all requests. Our plugins(modules) were copied to a sub-folder of it. The plugins also were ASP.NET … Read more
AddIdentityCore adds the services that are necessary for user-management actions, such as creating users, hashing passwords, etc. Here’s the relevant source: public static IdentityBuilder AddIdentityCore<TUser>(this IServiceCollection services, Action<IdentityOptions> setupAction) where TUser : class { // Services identity depends on services.AddOptions().AddLogging(); // Services used by identity services.TryAddScoped<IUserValidator<TUser>, UserValidator<TUser>>(); services.TryAddScoped<IPasswordValidator<TUser>, PasswordValidator<TUser>>(); services.TryAddScoped<IPasswordHasher<TUser>, PasswordHasher<TUser>>(); services.TryAddScoped<ILookupNormalizer, UpperInvariantLookupNormalizer>(); // No … Read more
TryGetValue is slightly faster, because FindEntry will only be called once. How much faster? It depends on the dataset at hand. When you call the Contains method, Dictionary does an internal search to find its index. If it returns true, you need another index search to get the actual value. When you use TryGetValue, it … Read more
Maybe the “K” format specifier would be of some use. This is the only one that seems to mention the use of capital “Z”. “Z” is kind of a unique case for DateTimes. The literal “Z” is actually part of the ISO 8601 datetime standard for UTC times. When “Z” (Zulu) is tacked on the … Read more
I can reproduce this on 4.5.2. No RyuJIT here. Both x86 and x64 disassemblies look reasonable. Range checks and so on are the same. The same basic structure. No loop unrolling. x86 uses a different set of float instructions. The performance of these instructions seems to be comparable with the x64 instructions except for the … Read more
I tend to agree (that it seems needlessly verbose), although this has been an issue our team hasn’t yet resolved and so our coding standards still insist on verbose properties for all classes. Jeff Atwood dealt with this a few years ago. The most important point he retrospectively noted is that changing from a field … Read more
SignalR is like Socket.IO in that it supports transport negotiation/fallback. It is a framework and not a server, so you need to host it on a server of some sort. We have hosts for ASP.NET, OWIN (e.g. Kayak) and self-host, so you can run it in your own process easily, e.g. a Windows service. SignalR … Read more