Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
using System; | |
using System.Reflection; | |
using CommonDomain; | |
using CommonDomain.Core; | |
using CommonDomain.Persistence; | |
using CommonDomain.Persistence.EventStore; | |
using EventStore; | |
using EventStore.Dispatcher; |
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
/* | |
Example use (from an email I sent) | |
I’m using WhenAny to either register for a callback on any of the pending operations and to use | |
the IO thread that comes up with their respective completion or to execute handling of completed | |
work on the current thread (‘borrowing’ the IO thread). | |
So if I read from a socket and from a queue, first both ops hang. Queue read completes and I get | |
called back on an IO thread which continues the await. I process that completion in the loop. | |
Meanwhile the socket read completes. That IO thread pops up and just registers the fact that it’s |
namespace Analogy | |
{ | |
/// <summary> | |
/// This example shows that a library that needs access to target .NET Standard 1.3 | |
/// can only access APIs available in that .NET Standard. Even though similar the APIs exist on .NET | |
/// Framework 4.5, it implements a version of .NET Standard that isn't compatible with the library. | |
/// </summary>INetCoreApp10 | |
class Example1 | |
{ | |
public void Net45Application(INetFramework45 platform) |
Connections to the Azure Event Hubs service are made using the fully qualified namespace name assigned for the Event Hubs namespace as the root of the endpoint address. Because the Event Hubs service ensures the appropriate CNAME records are configured in DNS as part of the provisioning process, this provides an endpoint address that is strongly associated with the Event Hubs namespace and easier for developers to remember.
While the standard approach works well under normal circumstances, it can be troublesome in certain environments when a proxy is in use or when an Express Route circuit is used with certain configuration. In these scenarios, an alternative host name is needed to allow for proper routing to the Event Hubs service.
import SwiftUI | |
import WebKit | |
@main | |
struct MonacoApp: App { | |
let codeSnippet = """ | |
var body: some Scene { | |
WindowGroup { | |
EditorView(content: codeSnippet, language: "swift", theme: "vs-dark") | |
} |