You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ReadMe.md
+59-47Lines changed: 59 additions & 47 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,57 +12,72 @@ The included analyzer helps you ensure license compliance by identifying package
12
12
Additionally, these tools offer optional configurations to generate code that provides access to icons, license texts, ReadMe content, release notes, and other package information.
13
13
You can include these additional resources based on your specific needs.
14
14
15
-
Key Features:
16
-
* Generate code for easy access to package data
17
-
* Analyze and enforce license compliance
18
-
* Customizable configuration settings
19
-
* Seamless integration with your projects
20
-
* Possibility of use with CI/CD
15
+
Currently, the project only supports C#, but it is designed in a way that allows for future support of VB.NET or F#.
Generate simple and easily accessible code to retrieve detailed information about the packages installed in your project.
21
+
With this code, you can easily access package versions, dependencies, licenses, and other data.
22
+
23
+
3.**Check License Compliance:**</br>
24
+
The included analyzer helps you ensure compliance with licensing requirements.
25
+
Identify packages that contain licenses not compatible with your project or company policies, enabling you to address potential licensing issues early on.
26
+
27
+
5.**Customizable Configuration:**</br>
28
+
Tailor the behavior of the tool to perfectly match your requirements.
29
+
Adjust the configuration to change how package contents are loaded, code is generated, and license analyses are performed.
30
+
31
+
7.**Seamless Project Integration:**</br>
32
+
The project can be seamlessly integrated into your existing projects.
33
+
Install the required NuGet packages and configure the settings accordingly. Accessing package data and license information is straightforward through the generated code.
34
+
35
+
9.**Possible Use with CI/CD:**</br>
36
+
The .NET Tool allows integration into CI/CD processes, automating package analysis and management in your continuous integration and deployment workflows.
The Analyzer can be configured directly in your project and supports checking which packages and licenses are allowed.
31
45
32
46
# Installation
33
47
34
-
For both options, you need to install the NuGet package [PackScan.PackagesProvider.Abstractions](https://www.nuget.org/packages/PackScan.PackagesProvider.Abstractions) in those projects in which you want to use the generated code.</br>
35
-
You can install it using the NuGet package manager or add the following lines to your project:
48
+
### Analyzer
49
+
50
+
Install the analyzer:
36
51
37
52
```
38
-
<ItemGroup>
39
-
<PackageReference Include="PackScan.PackagesProvider.Abstractions" Version="x.x.x" /> <!-- use the latest version -->
40
-
</ItemGroup>
53
+
dotnet add package --prerelease PackScan.Analyzer
41
54
```
42
55
43
-
## .NET Tool
56
+
Additionally, you need to install the following package in all projects where you want to use the code:
<Description>Simplify package information retrieval and license compliance in your .NET projects. Access comprehensive package details, including dependencies, icons, license texts, ReadMe content, and release notes directly from your code.</Description>
18
+
<Description>Simplify package information retrieval and license compliance in your .NET projects. Access comprehensive package details, including dependencies, icons, license texts, ReadMe content, release notes and more directly from your code.</Description>
title:"Packages without a license are not allowed",
154
-
messageFormat:"Empty licenses are not allowed. Possibly the license could not be read. Consider allowing the package directly (AllowedLicenseByPackage) or empty licenses (AllowEmptyLicense). Affected packages: {0}",
154
+
messageFormat:"Empty licenses are not allowed. Possibly the license could not be read. Consider allowing the package directly (AllowedLicenseByPackage) or empty licenses (AllowEmptyLicenses). Affected packages: {0}",
0 commit comments