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
{{ message }}
This repository was archived by the owner on Nov 12, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,11 +9,16 @@ These extensions expand the upgrade-assistant tools's functionality to make Opti
9
9
Install the latest vesion of the upgrade-assistant `dotnet tool install -g upgrade-assistant` or upgrade `dotnet tool update -g upgrade-assistant`
10
10
11
11
12
-
Grab the latest release from [here](https://github.com/episerver/upgrade-assistant-extensions/releases) and unzip the file to a location of your computer (ex C:\temp\epi.source.updater). Technically you should be able to point the zip file instead of extracting but there seems to be a bug in upgrade-assisant at the moment for that.
12
+
Grab the latest release from [here](https://github.com/episerver/upgrade-assistant-extensions/releases) and unzip the file to a location of your computer (ex C:\temp\epi.source.updater). Technically you should be able to point the zip file instead of extracting but there seems to be a bug in upgrade-assistant at the moment for that.
13
13
14
14
## Using the extension
15
+
Some of the source code upgrade code analyzers requires that packages referenced are available in selected target framework. So for now when CMS targets net5.0 the recommendation is to target net5.0 when converting as well (target framework can be set to net6.0 after conversion is completed). To achieve this first set environment variable like:
16
+
```
17
+
set DefaultTargetFrameworks__LTS=net5.0
18
+
```
19
+
then run upgrade-assistant with flag *--target-tfm-support LTS*, like:
0 commit comments