This repository has been archived by the owner on Sep 13, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 432
Upgrade of ASP.NET on 4.6 to 4.7.2 fails: The type 'System.Object' is defined in an assembly that is not referenced. #877
Labels
Milestone
Comments
For reference, here is the pre-re-targetting packages.config, in full:
I guess, something about this set of dependencies, introduces an irreconcilable dependency issue when migrating. Beyond that... it's a mystery. |
This was referenced Oct 15, 2018
This was referenced Oct 24, 2018
Closing as dupe of #936 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've commented in #481 about this, but in order to avoid cluttering that thread, here are the specific details:
Given a 4.6 ASP.Net project, the following steps were taken, as recommended in #481:
PackageReference
by hand, manually converting files inpackages.config
into the correct format and adding them to anItemGroup
in the csproj file.assemblyBinding
section of the web.configThis generates the following assembly binding section in the web.config:
Notice that
System.Runtime
is not found in this section after using the VS tooling.The application compiles, but at runtime it generates this error:
Other conflicting advice exists in various places, including the suggestion that
PackageReferences
are not support in ASP.Net, however, in order to cover my bases, I also tried the following:assemblyBinding
section of the web.configThis resulted in the identical error.
I also tried:
assemblyBinding
section of the web.configThis resulted in the identical error.
In order to further ensure I was not experiencing a local issue, I repeated these steps from the clean repo clone on a different machine, with identical results.
I notice that after a build, there is no
System.Runtime.dll
in the bin folder when targeting 4.7.2, because, as noted in https://github.com/dotnet/corefx/issues/31536, not version targeting that runtime appears to currently exist.I conclude that the VS tooling to automatically generate bindings doesn't work correctly in some cases (eg. mine), and that it is simply not possible to currently migrate some current ASP.Net projects.
If nothing else, I leave this here for other people to find on the issue tracker.
The text was updated successfully, but these errors were encountered: