-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leverage packages provided by framework rather than polyfill/deprecated packages #5106
Comments
To address your inquiry about the necessity of certain NuGet packages for Elsa Workflows, it's important to understand that the need for explicit package references can depend on the target framework of your application. For applications targeting .NET Core 3.0 and above, many ASP.NET Core related packages are included as part of the shared framework, which is referenced by using the However, if you are targeting an older framework or a framework that does not include these libraries as part of a shared framework, you may need to reference them explicitly. Here's a breakdown of the packages you mentioned:
For Elsa Workflows, you should review the framework compatibility and dependencies listed in the documentation or the NuGet package information to determine if you need to reference these packages directly. If you are using .NET Core 3.0 or above, it is likely that you do not need to add these packages explicitly unless you have a specific reason to do so. Please let me know if you need further clarification or if you have a specific scenario in mind that requires these packages. |
The following nuget packages should only be required on older frameworks where the framework is not providing the libraries:
The text was updated successfully, but these errors were encountered: