dotNetify | yet powerful way to build | Websocket library

I have a custom binding handler that I am binding to a complex object in my view model.

The binding handler works correctly and the update function is called when any of the observable's properties update. However, the update function is called for every updated property, leading to odd behaviour since I am relying on the entire object to be available and up to date.

I understand why this is happening, as each property is causing an update to be called, and I think I know how to prevent this - by using the deferred updates functionality of Knockout.

However, I am unable to find how to enable deferred updates just for the observable in my custom binding. I do not want to enable it application wide as I am writing the binding as a library function.

I have tried many different methods including:

• trying to extend the binding handler itself;
• extending the init function;
• extending the valueAccessor;
• replacing the valueAccessor with a new observable with deferred applied;
• creating a computed observable and rebinding the element;

All of which have not worked.

I have not found any other custom binding handler that comes remotely close to this sort of function and have been trying to piece it together from other functions.

My binding code itself is relatively simple, I am taking the bound object and simply splitting out the parameters and passing them to a Code Mirror instance.

Im trying to test my React class, that has import dotnetify from "dotnetify"; import. That works fine, but Jest says, that dotnetify is undefined. If i change to import dotnetify = require("dotnetify");, Jest passes test, but this is silly workaround. How to explain Jest, that dotnetify is not undefined?

Than you in advance.

I implemented the possibility to add "properties" at runtime to objects with special SystemComponent.PropertyDescriptor-s.

Due to the fact that these properties are only accessible with the ComponentModel.TypeDescriptor and not via Reflection, the properties work well in WPF environment but not with Serialization.

This is because of all JSON serializers, that I know, use reflection on the type. I analyzed Newtonsoft.Json, System.Json, System.Web.Script.JavaScriptSerializer, System.Runtime.Serialization.Json.

I don't think I can use any of these serializers because none of these allow modifying the retrieval of the properties on an instance (e.g. ContractResolver not possible).

Is there any way to make the JSON serialization work with one of those serializers? Maybe by special configuration, overriding certain methods on the Serializer or similar? Is there another serializer available that fulfills this requirement?

Background:

The idea of the runtime properties is based on this blog entry.

The serialization requirement comes from using dotNetify that serializes the viewmodels to send them to the client.

Currently, I made a fork of dotnetify and made a temporary workaround for the serialization by partially serializing with Newtonsoft.Json and a recursive helper. (You can look at the diff if interested in it: the Fork).

As the title says... I've been using C# MVC for most of my web dev needs for many years. We have a bunch of legacy systems here so my technology choices have been set in stone.

New system time! Looking at React, dotnetify seems cool but it pushes towards Core. Core is so very very different to what I'm used to. As an example, no FormsAuthentication.

I'm obviously fine with learning a new tech if that's what "everybody is doing" -- but are they? Or is the .NET world split between .NET 5 and Core?