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
During the net472 upgrade we didn't update the packages.config to reference net472 as the targetFramework. This really isn't that big of a deal, but we should update all of the packages.config to reference net472 for 10.0
Screenshots
N/A
Error log
N/A
Additional context
N/A
Affected version
10.0.0 nightly build
9.4.1 nightly build
9.4.0 latest supported release
Affected browser
N/A
The text was updated successfully, but these errors were encountered:
We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically.
If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!
This issue has been closed automatically due to inactivity (as mentioned 14 days ago). Feel free to re-open the issue if you believe it is still relevant.
Description of bug
During the net472 upgrade we didn't update the
packages.config
to referencenet472
as the targetFramework. This really isn't that big of a deal, but we should update all of thepackages.config
to reference net472 for 10.0Screenshots
N/A
Error log
N/A
Additional context
N/A
Affected version
Affected browser
N/A
The text was updated successfully, but these errors were encountered: