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.
If I include files in my Silverlight app and need to load them as raw byte arrays programatically, which Build Action should I set them as, and how do I refer to them? If they are included as Content, can I load them by path as a regular file? If I include them as Resource is there a collection of embedded resources where I can grab a reference to them? What are the pros and cons and differences between the two approaches?
Set the Build Action to “Embedded Resource” and use
Assembly.GetManifestResourceStreamto load them. I believe the “Resource” build action is meant for resource files (resx) which are slightly different, although I’ve never been entirely sure 🙂If you include them as regular content, you may have difficulty deploying the files – I’m not entirely sure, to be honest. (That’s a Silverlight-specific area.)
Personally I like using Embedded Resources so long as you don’t need to be able to update them independently – at that point it’s helpful to have them on disk as normal files.