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
Endless Lifecycle Support (ELS) for .NET from TuxCare delivers security fixes for .NET components distributed through NuGet packages. This allows you to continue running your .NET applications without vulnerability concerns, even after official support has ended.
3
+
Endless Lifecycle Support (ELS) for .NET from TuxCare delivers security fixes for .NET library, framework, and tool packages, distributed through NuGet packages. This allows you to continue running your .NET applications without vulnerability concerns, even after official support has ended.
4
4
5
5
NuGet is the standard package manager for .NET, used to deliver the reusable components applications depend on. ELS applies fixes at the package level, so your applications receive security updates without requiring changes to your own code.
6
6
@@ -10,20 +10,17 @@ NuGet is the standard package manager for .NET, used to deliver the reusable com
10
10
11
11
Other versions upon request.
12
12
13
-
## Connection to ELS for .NET components Repository
14
-
15
-
This guide outlines the steps needed to integrate the TuxCare ELS for .NET components repository into your .NET project.
16
-
17
-
### Prerequisites
13
+
## Prerequisites
18
14
19
15
* .NET SDK installed. A TuxCare-supported .NET SDK build is also [available](/els-for-runtimes/dotnet/).
20
-
* Access to the TuxCare NuGet repository (credentials required).
16
+
* Access to the TuxCare .NET NuGet repository (credentials required).
17
+
You need a username and password to use the TuxCare ELS for .NET repository. Anonymous access is disabled. To receive the credentials, please contact [sales@tuxcare.com](mailto:sales@tuxcare.com).
21
18
22
-
### Step 1: Get User Credentials
19
+
##Adding the Repository
23
20
24
-
You need a username and password in order to use the TuxCare ELS for .NET components repository. Anonymous access is disabled. To receive the credentials, please contact [sales@tuxcare.com](mailto:sales@tuxcare.com).
21
+
This section describes how to add the TuxCare ELS for .NET repository as a package source.
25
22
26
-
### Step 2: Add TuxCare NuGet Source
23
+
### Adding the NuGet Source via CLI
27
24
28
25
Add the TuxCare NuGet repository as a package source using the `dotnet` CLI:
**Replace `<USERNAME>` and `<PASSWORD>` with the credentials provided by sales.**
42
39
40
+
### Adding the NuGet Source via nuget.config
41
+
42
+
As an alternative to the CLI, you can configure NuGet package sources using a `nuget.config` file. This approach is useful for sharing configuration across a team or for version-controlled source settings.
43
+
44
+
#### Understanding NuGet Configuration Hierarchy
45
+
46
+
NuGet configuration follows a hierarchy (from highest to lowest priority):
47
+
48
+
1.**Project-level**: `nuget.config` in your project folder
49
+
2.**Solution-level**: `nuget.config` in the solution folder (parent directory)
* The `<clear />` element removes inherited package sources, giving you full control.
78
+
* The `nuget` source points to the official NuGet.org repository.
79
+
* The `TuxCare` source points to the TuxCare ELS repository.
80
+
81
+
#### Adding Credentials for nuget.config
82
+
83
+
If your `nuget.config` requires authentication, you can add credentials using the CLI or by adding a `<packageSourceCredentials>` section to your `nuget.config`:
Avoid committing credentials to version control. Consider using environment variables or a separate local configuration file for sensitive information.
92
+
:::
93
+
94
+
### Verifying the Source
95
+
43
96
To verify that the source was added successfully, list all configured NuGet sources:
This section explains how to install and use packages from the TuxCare repository.
119
+
120
+
### Navigating to Your Project
60
121
61
122
Ensure you are in a directory containing a valid .NET project. The folder must contain a `.csproj` file.
62
123
@@ -68,7 +129,7 @@ dir *.csproj
68
129
69
130
</CodeWithCopy>
70
131
71
-
If a `.csproj` file is found, you can proceed with package installation. If not, you need to navigate to a valid .NET project directory or create a new project:
132
+
If a `.csproj` file is found, you can proceed with package installation. If not, create a new project:
72
133
73
134
<CodeWithCopy>
74
135
@@ -79,7 +140,7 @@ cd MyProject
79
140
80
141
</CodeWithCopy>
81
142
82
-
### Step 4: Install a Package
143
+
### Installing Packages
83
144
84
145
Install a package from the TuxCare repository using the `dotnet add package` command:
You can find a specific component version in your TuxCare account on [Nexus](https://nexus.repo.tuxcare.com/repository/els_dotnet/) (anonymous access is restricted).
105
-
106
-
### Step 5: Build the Project
107
-
108
-
After installing the package, verify that everything works correctly by building the project:
If the build completes successfully, the TuxCare package is successfullyintegrated into your project.
175
+
**You can find available package versions in your TuxCare account on [Nexus](https://nexus.repo.tuxcare.com/repository/els_dotnet/) (anonymous access is restricted).**
119
176
120
-
##Managing NuGet Sources
177
+
### Using Package Source Mapping
121
178
122
-
### Remove a Source
179
+
If you use a `nuget.config` file, you can add package source mapping to route specific packages to the TuxCare feed. This ensures certain packages are always fetched from TuxCare while others come from NuGet.org.
123
180
124
-
If you need to remove the TuxCare source:
181
+
Add a `<packageSourceMapping>` section to your `nuget.config`, for example, Newtonsoft.Json:
125
182
126
183
<CodeWithCopy>
127
184
128
-
```text
129
-
dotnet nuget remove source TuxCare
185
+
```
186
+
<packageSourceMapping>
187
+
<!-- Allow nuget.org to serve any package -->
188
+
<packageSource key="nuget">
189
+
<package pattern="*" />
190
+
</packageSource>
191
+
192
+
<!-- Route specific packages to TuxCare feed -->
193
+
<packageSource key="TuxCare">
194
+
<package pattern="Newtonsoft.*" />
195
+
</packageSource>
196
+
</packageSourceMapping>
130
197
```
131
198
132
199
</CodeWithCopy>
133
200
134
-
### Update Source Credentials
201
+
**You can find available package versions in your TuxCare account on [Nexus](https://nexus.repo.tuxcare.com/repository/els_dotnet/) (anonymous access is restricted).**
135
202
136
-
To update the credentials for an existing source, remove and re-add the source:
203
+
### Building the Project
204
+
205
+
After installing packages, verify that everything works correctly by building the project:
If the build completes successfully, the TuxCare package is successfully integrated into your project. Check the output folder to confirm that the package DLL (e.g., `Newtonsoft.Json.dll`) was downloaded from the TuxCare repository.
216
+
217
+
### Upgrading Packages
151
218
152
219
To upgrade to a newer TuxCare release, update the package in your project:
153
220
@@ -167,4 +234,47 @@ Then rebuild the project to verify the upgrade:
167
234
dotnet build
168
235
```
169
236
170
-
</CodeWithCopy>
237
+
</CodeWithCopy>
238
+
239
+
## Managing NuGet Sources
240
+
241
+
This section covers common tasks for managing the TuxCare NuGet source.
242
+
243
+
### Removing a Source
244
+
245
+
If you need to remove the TuxCare source:
246
+
247
+
<CodeWithCopy>
248
+
249
+
```text
250
+
dotnet nuget remove source TuxCare
251
+
```
252
+
253
+
</CodeWithCopy>
254
+
255
+
### Updating Source Credentials
256
+
257
+
To update the credentials for an existing source, remove and re-add the source:
0 commit comments