Mario Guerra

This `CppNet` is an old library that parses C/C++. It is used in the Stride's shader compiler to pre-preocess the shader files to expand pre-processor `#define`s, `#ifdef`s, etc.

Nice to hear. We need however to ensure that current shaders work properly, as some of them have complex macros and `#define`s (IIRC). Look at _FXAA_ shader for example.

Currently the standard I think is **projective decals**, commonly implemented as deferred decals (see [this page](http://www.humus.name/index.php?page=3D&ID=83). They are even optimized in modern engines using tricks similar to those of tiled...

> Instead, we should either properly reimplement the custom workspace/host or reuse the one provided by RoslynPad library. That won't do. The RoslynPad workspace is not a MSBuild workspace operating...

I've made tests in which I replaced the external reference to RoslynPad as a package and instead integrate only the necessary parts inside Stride solution. I was succesful in doing...

@dotnet-policy-service agree

A question about one of the commits: As of this PR `Stride.Core.AssemblyProcessor` can be built both for `net6.0` and `netstandard2.0` and it will be copied to `deps`. Should we delete...

I'd tend to agree. But as I've written in the PR, I think `netstandard2.0` is still needed by the .NET Framework version of MSBuild that Visual Studio uses. Whenever I've...

I could try to include the Assembly Processor project in the main solution, setting the order so every other project builds after it. It could also be set to build...

In theory, the assembly produced by compiling the Assembly Processor is not locked because it is first copied to `deps`, and then also copied to a temporary directory based on...