From b649129df7dc59c0ae7398629bdc9a7ae567e3e7 Mon Sep 17 00:00:00 2001 From: sara-rn Date: Wed, 15 Nov 2023 14:04:46 +0100 Subject: [PATCH] deleted older file limitation rule --- ...nternal-dotnet-bundled-file-limitation.yml | 20 ------------------- 1 file changed, 20 deletions(-) delete mode 100644 internal/limitation/file/internal-dotnet-bundled-file-limitation.yml diff --git a/internal/limitation/file/internal-dotnet-bundled-file-limitation.yml b/internal/limitation/file/internal-dotnet-bundled-file-limitation.yml deleted file mode 100644 index d34b54d1..00000000 --- a/internal/limitation/file/internal-dotnet-bundled-file-limitation.yml +++ /dev/null @@ -1,20 +0,0 @@ -rule: - meta: - name: (internal) .NET single file bundles limitation - namespace: internal/limitation/file - authors: - - "@sara-rn - 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 determines the main .NET library to be analyzed. - - scope: file - examples: - - a83339b07cf2bf1aeda192de42760c625d4b2f106260f58c902d02f4766848d5 - features: - - or: - - match: runtime/dotnet/bundled-with-dotnet-single-file-deployment \ No newline at end of file