Skip to main content

anti patterns codin'

Search This Blog

Async and Threading guidelines for dotNET from Microsoft

August 02, 2023

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Async coding can be tricky, even in dotnet C#.

Thankfully, Microsoft have published best practice documents:

1. async await best practices

https://learn.microsoft.com/en-us/archive/msdn-magazine/2013/march/async-await-best-practices-in-asynchronous-programming

2. Related: TAP - Task based Asynchronous Pattern

https://learn.microsoft.com/en-us/dotnet/standard/asynchronous-programming-patterns/task-based-asynchronous-pattern-tap?redirectedfrom=MSDN

Related material

- https://channel9.msdn.com/Series/Three-Essential-Tips-for-Async

- https://en.wikipedia.org/wiki/Referential_transparency

ASP.NET C# Threading

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Comments

Post a Comment

Popular Posts

Hosting a proxy in an ASP.NET or SharePoint application - limits of NTLM (double hop issue) and how to overcome

Hosting a proxy in an ASP.NET or SharePoint application - limits of NTLM (double hop issue) and how to overcome ISSUE: If you host a proxy page (ASHX) in ASP.NET or in SharePoint, and the target server is a different machine, and the target server requires Windows Authentication , then you should know that NTLM has a restriction, where it cannot pass credentials on the 'second hop' from the proxy to the target server, unless it has an explicit username and password. this is called the ' double hop NTLM issue ' and is better documented elsewhere: http://blogs.msdn.com/b/besidethepoint/archive/2010/05/09/double-hop-authentication-why-ntlm-fails-and-kerberos-works.aspx note: if your application uses Negotiated (Kerberos) Authentication, and Kerberos is correctly setup, then my understanding is that Kerberos can handle the second hop from the proxy to the target server. if you *must* use NTLM (for example, if you must deploy to an existing SharePoint Web App), th

XAML - using a constant in place of a string

XAML - using a constant in place of a string To keep code consistent, it can be useful to use constants rather than 'magic strings'. Here is how XAML can be changed, to refer to a constant, rather that to a string: 1. create a C# class, that contains the string constant: public class MyConstants { public const string ContentRegion = "ContentRegion"; } 2. In the XAML , add a namespace, to the Assembly and Namespace, that contains the class: <window ... ... xmlns:inf="namespace=MyApp.Infrastructure;assembly=MyApp.InfrastructureLibrary" > where: a. the C# class is in the namespace: MyApp.Infrastructure b. the C# class is in the assembly MyApp.InfrastructureLibrary 3. Now in XAML , instead of using a 'magic string': < ... prism:RegionManager.RegionName=" ContentRegion " /> you can reference the constant string: < ... prism:RegionManager.RegionName="{x:Static inf:MyConstant

TypeScript - runtime check if an object implements an interface

problem: TypeScript - how to perform *runtime* check, if an object implements an interface In JavaScript there is no such thing as an interface, so it can be tricky to perform a *runtime* check to see if object A implements interface I. for example, the instanceof operator will not work against an interface type. export interface MyInterface { getName(): string | null; } CLIENT CODE (broken): if (object instanceof MyInterface) { // MyInterface is an interface, not a class // so this code will not work at run-time // (and should not compile!) } solution: one approach is to use a helper method. The helper method checks for the existence of a distinctive method of the interface, and then uses the is keyword in the return type, to return the expected interface type. export function isMyInterface (object): object is MyInterface { const myInterface = object as MyInterface; return myInterface.getName !== undefined; } CLIENT CODE (

Powered by Blogger