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 has been archived by the owner on May 7, 2024. It is now read-only.
I found this project during MS Learn Tutorial: https://docs.microsoft.com/pl-pl/learn/modules/aspnet-session/
During exercise I was told to download project from this repository. As stated in instructions, VS asked me to install additional components. During all this time, solution did not compile.
Unfortunately VS provided only ambiguous messages about missing or conflicting packages without any error code. However, after some research, I was able to fix this error by downgrading log4net nuget package to 2.0.8.0.
I can prepare a pull request if needed.
The text was updated successfully, but these errors were encountered:
Hey @PRudykIteo, yes, your analysis was correct. 👍 There is some issue with the log4net package. Actually, within the src\eShopLegacyWebForms\eShopLegacyWebForms.csproj file package is still pointing to the old version 2.0.8.
And that's the reason if you downgrade the log4net, then the project gets build successfully. My suggestion would be, let's update the solution with log4net version as 2.0.10`.
You could submit a PR with the changes. We will be happy to review and merge the changes with the main branch.
I found this project during MS Learn Tutorial: https://docs.microsoft.com/pl-pl/learn/modules/aspnet-session/
During exercise I was told to download project from this repository. As stated in instructions, VS asked me to install additional components. During all this time, solution did not compile.
Unfortunately VS provided only ambiguous messages about missing or conflicting packages without any error code. However, after some research, I was able to fix this error by downgrading log4net nuget package to 2.0.8.0.
I can prepare a pull request if needed.
The text was updated successfully, but these errors were encountered: