softworkz

I think this image makes the relationships very clear:  Chapter 4, where the fixed bandwidth allocations are discussed is talking about the **DVCC Transport Channel** having the constant bitrate,...

I'm not coming empty-handed...: 

How about setting up a new branch for this, like nextgen or so? My typical approach for such things is to "race" over all the tough points to get to...

I'm starting a series of posts, documenting and explaining the changes I've made so far, Let's start with this: ## .NET Project System Extension & Manifest Replacement In the screenshot...

# Building ## Prerequisites ### RID-Specific Builds Since we always end up having RID-specific output, we can do so right away, even when not publishing. This allows pinpointing platform-specific issues...

## Incremental Build Demo Note that "Building Electron" here means to copy (update) the changed files and run `npm install` in the `.electron` folder. https://github.com/user-attachments/assets/a16e097c-5958-4fe9-99ed-c7b9355ad4a2

> One challenge I see here, which is why I didn't make it freely selectable by design in the past. For example, there are many breaking changes between the native...

> For support native Electron extensions, we have integrated a feature, called Electron Hooks, typically require an Electron CLI again. This is because it manages triggering actions like "npm install,"...

## ElectronHostHook That part was a bit mind-bending to figure it out. Not about how to handle it but rather about understanding the way how it's done and how it...

Host Hook is all good now. I've changed the first post into a task list for tracking progress. Next point is: # Debugging I belive this is a point where...