identify .NET single file bundles

executable/installer/dotnet/bundled-with-dotnet-single-file-deployment.yml

@@ -0,0 +1,20 @@
+rule:
+  meta:
+    name: bundled with .NET single-file deployment
+    namespace: executable/installer/dotnet
+    authors:
+      - [email protected]
+    scope: file
+    references:
+      - https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview?tabs=cli
+      - https://github.com/dotnet/runtime/blob/84de9b678613675e0444b265905c82d33dae33a8/src/installer/managed/Microsoft.NET.HostModel/AppHost/HostWriter.cs
+    examples:
+      - a83339b07cf2bf1aeda192de42760c625d4b2f106260f58c902d02f4766848d5
+  features:
+    - or:
+      - and:
+        - match: contains PDB path
+        - string: "singlefilehost.pdb"
+          description = symbol file for the native executable when PublishSingleFile is true
+      - export: DotNetRuntimeInfo
+      - export: corehost_initialize

internal/limitation/file/internal-dotnet-single-file-deployment-limitation.yml

@@ -0,0 +1,19 @@
+rule:
+  meta:
+    name: (internal) .NET single file deployment limitation
+    namespace: internal/limitation/file
+    authors:
+      - [email protected]
+    description: |
+      This sample appears to be built with the single-file deployment in .NET.
+
+      Single-file deployment allows all the application-dependent files to be bundled into a single binary.
+      The size of the single file in a self-contained application is large since it includes the runtime and the framework libraries.
+      The main application and the libraries are contained in the overlay section.
+      You may need to extract the runtime configuration files such as *.deps.json and *.runtimeconfig.json files to determine the main .NET library and extract it with the tool SingleFileExtractor.
+    scope: file
+    examples:
+      - a83339b07cf2bf1aeda192de42760c625d4b2f106260f58c902d02f4766848d5
+  features:
+    - or:
+      - match: executable/installer/dotnet