// Oprogramowanie Roman Ryltsov
Isolated property is supposed to enable referencing in-process COM servers as a registration free COM dependency, but something got broken on the way: Visual Studio 2019 Preview and .NET 5 produce applications that lose the link. It is still preview so hopefully things get resolved timely. The issue on GitHub: Single-File Executable Cannot Use Registration…
In one of the earlier posts I mentioned a problem with registration-free COM dependency setup up by Visual Studio as a part of build process. This post is about the tool that offers an alternate solution for the problems, and also gives more: standalone, independent from build, addition/removal registration-free COM links automation of registration-free COM…
Visual Studio offers COM reference isolation to applications so that COM dependency is used in a usual way, and in the same time there is no need in its registration or another copy of the COM server might be registered system wide, or using per-user registration, and the application would still prefer a local copy…