Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Okay, so ASP.net allows one to embed Images into an Assembly and access them using WebResource.axd.
I just wonder: What are the Pros/Cons of using Web Resources instead of Images in a folder on the Web Server, like how it’s being traditionally done?
This article mainly mentions ease of deployment, but that doesn’t seem to justify the extra amount of work.
One clear scenario is: third party controls.
I really don’t want to deal with different script/image files for controls we are not developing. With embedded resources, its just the .dll file and that’s it :).
The same applies if you are developing custom web controls that you will be using across different web sites.