Basic concepts of CSS grid layout

What is a grid?

A grid is a set of intersecting horizontal and vertical lines defining columns and rows. Elements can be placed onto the grid within these column and row lines. CSS grid layout has the following features:

Fixed and flexible track sizes

You can create a grid with fixed track sizes – using pixels for example. This sets the grid to the specified pixel which fits to the layout you desire. You can also create a grid using flexible sizes with percentages or with the fr unit designed for this purpose.

developer.mozilla.org/en-US/docs/Web/CSS/CSS_grid_layout/Basic_concepts_of_grid_layout

How ArrowJS compares to React and Vue.js – LogRocket Blog

What is ArrowJS?

ArrowJS is an experimental tool for building reactive user interfaces using pure JavaScript. It uses modern JavaScript features, such as template literals, modules, and proxies, to implement its templating structure, observable data, and declarative/reactive DOM rendering capabilities.

The creator of ArrowJS believes it’s not necessary to have a complex framework to create impressive and performant user interfaces on the web because JavaScript has evolved to be powerful enough to handle these tasks natively.

As a result, ArrowJS has no dependencies, no Virtual DOM, no build tool, and no special templating language. It is also very lightweight, weighing less than 3kB (min+Gzip). This makes it ultra-fast compared to frameworks like React and Vue, which have comparable features.

blog.logrocket.com/how-arrowjs-compares-react-vue-js/

How do I store session data in Server-side Blazor?

First to access browser Session Storage in Blazor apps, write a custom code or use a third party package. The accessed data can be stored in the localStorage and sessionStorage.  The localStorage is scoped to the user’s browser. If the user reloads the page or closes and reopens the browser, the state persists. Session storage is similar to the local storage but the data in the session storage will be cleared after the session.

Source: How do I store session data in Server-side Blazor?

dnSpy – .NET debugger and assembly editor

dnSpy is a debugger and .NET assembly editor. You can use it to edit and debug assemblies even if you don’t have any source code available. Main features: Debug .NET and Unity assemblies Edit .NET and Unity assemblies Light and dark themes

Debugger

  • Debug .NET Framework, .NET and Unity game assemblies, no source code required
  • Set breakpoints and step into any assembly
  • Locals, watch, autos windows
  • Variables windows support saving variables (eg. decrypted byte arrays) to disk or view them in the hex editor (memory window)
  • Object IDs
  • Multiple processes can be debugged at the same time
  • Break on module load
  • Tracepoints and conditional breakpoints
  • Export/import breakpoints and tracepoints
  • Call stack, threads, modules, processes windows
  • Break on thrown exceptions (1st chance)
  • Variables windows support evaluating C# / Visual Basic expressions
  • Dynamic modules can be debugged (but not dynamic methods due to CLR limitations)
  • Output window logs various debugging events, and it shows timestamps by default 🙂
  • Assemblies that decrypt themselves at runtime can be debugged, dnSpy will use the in-memory image. You can also force dnSpy to always use in-memory images instead of disk files.
  • Public API, you can write an extension or use the C# Interactive window to control the debugger

Source: dnSpy/dnSpy: .NET debugger and assembly editor

Setup SCSS for Blazor

I have a few needs for SASS. Firstly, I need to be able to write SASS (or more correctly, .scss files) in Visual Studio and get all the help that Visual Studio is known for – syntax highlighting, snippets, etc. Ideally, I’d like to keep the SASS files separate from the other files so that I am messing with the wwwroot directory as little as possible. I should be able to build the SASS files into CSS files and have them auto populate the wwwroot directory. Finally, and most importantly, I need to be able to execute a build within a CI/CD platform without relying on Visual Studio and the existance of a specific setup.

https://adrianhall.github.io/asp.net/2022/08/26/adding-sass-to-blazor/

.NET 8 – The minimal API AOT compilation template

One of the big focuses of .NET 8 is Ahead of Time (AOT) compilation. In this post, I look at the new “AOT-ready” template shipping in the .NET 8 SDK preview releases, point out some of the interesting features, and demonstrate one of the main benefits of AOT – faster startup times.
andrewlock.net/exploring-the-dotnet-8-preview-the-minimal-api-aot-template/

Chrome for Testing: reliable downloads for browser automation – Chrome Developers

The infrastructure around Chrome for Testing unlocks interesting opportunities beyond Chrome itself. For example, the difficulties we previously mentioned around finding a matching Chrome and ChromeDriver binary can be completely eliminated by integrating the ChromeDriver release process into the Chrome for Testing infrastructure. In addition to solving this user-facing pain point, this also aligns ChromeDriver releases with Chrome’s, and eliminates the manual ChromeDriver release process.