

they were embedded in the EXE itself and not dependant on the directory structure). You moved the app to a different directory (b.c. Not true, and this is why those "worked" when Last, you assumed the project's resource file (RESX) contents were needed in your application's runtime directory (such as the ones created/used when you add an Image to a PictureBox). Will break your path as I've laid out in much detail in my previous posts.

Let me try to summarize these two issues one last time for you:įirst, you were adding an extra "/" to the beginning of your relative path for a loose file and this I think I understood how you get here, hence another post. Resources in Applications, which are usually embedded in an assembly, with loose files your application can load at runtime using a relative path. That's not his problem in this case, but good to point out for him none the less.
