I've busted this question into three parts. This is part one.
Over the last few months, I've dragged and dropped some chart controls and some other ASP standard and data controls onto some web forms in my project. Subsequently, some assembly references have appeared in my project Web.config file.
- Figure 1 shows the project's current assembly references in Web.config.
- Figure 2 shows the project's current assembly references in the manifest.
- One more piece if interesting information: If I delete all
assembly references from Web.config on the development server, I can still build the project successfully.
I've noticed that there's some overlap (System.Web.DataVisualizat
ion is referenced in both places). Mostly, however, the references don't overlap.
What's up with the two sets assembly references?
How does .NET decide make the decision, "Aha, this assembly reference belongs in Web.config whereas this assembly reference belongs in the manifest."?