Question 1

How to set up a shared runtime with NetBeauty 2?

Accepted Answer

Enable the `BeautySharedRuntimeMode` property in your .csproj file and specify `BeautyLibsDir`. NetBeauty organizes dependencies into a shared directory, allowing multiple apps to reuse libraries, as detailed in the shared runtime structure example.

Question 2

NetBeauty 2 vs NetCoreBeauty: which should I choose?

Accepted Answer

NetBeauty 2 supports more deployment models (FDD, FDE) and doesn't always require patching, while NetCoreBeauty is limited to SCD. Choose NetBeauty 2 for flexibility, but if you only need SCD and prefer the older approach, NetCoreBeauty might suffice, based on the feature comparison table.

Question 3

Can I hide files on Linux with NetBeauty?

Accepted Answer

No, the `--hiddens` option is explicitly stated to be Windows-only in the README. For Linux or macOS, you'll need to rely on other file management methods or accept visible dependencies.

Question 4

How to exclude specific DLLs from being moved by NetBeauty?

Accepted Answer

Use the `BeautyExcludes` property in your .csproj file, listing DLLs like `dll1.dll;lib*;...`. This keeps critical or custom files in the main directory without affecting other dependencies.

Question 5

Does NetBeauty 2 work with .NET 5 or .NET 6?

Accepted Answer

Yes, since it supports .NET Core 3.0+, it is compatible with .NET 5 and .NET 6, as they are part of the .NET Core lineage. Ensure your target framework is set correctly in the project.

Question 6

What changed in NetBeauty 2.1.5 that might break my setup?

Accepted Answer

The startup hook was renamed from `nbloader` to `libloader`, but backward compatibility is maintained through policies like `BeautyNBLoaderVerPolicy`. Check the breaking changes section and issue #80 for details to avoid disruptions.

NetCoreBeauty

What is NetCoreBeauty?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions