The job of a framework library is to provide a basic package of necessary services and components.
ASP.NET 2.0 made it easy with the WebResourceAttribute. And I was hunting for a bug today:
We have this bit of code on the masterpage in the framework, as soon as we use this in applications it stops working.
We get a 404, "invalid webresource request".
The issue actually was quite easy to fix once we what the Type argument was for. It's for ASP.NET to work out which assembly to look for the resource.
Which fixed the problem.