dayssitespeed.blogg.se

the resx gets embedded in the application). This "imported resource" is compiled into the resx and is not deployed with the application in production (b.c. Otherwise, it can go to a different resx in the project but that creates a folder "Resources" when it imports the file If you load an image into a picture box and choose "Local Resource" it goes to your Form's resx file as shown in the image above. Here is a picture showing you how a Form's RESX file is configured to be embedded: For more information, read the above link for Resources in Applications. (and the easiest way to work with them) and you have already seen how they work. A resx contains its resources and can be embedded in an assembly. This is typically how WinForms resx files are compiled Obviously, how a RESX file works is a much more complicated discussion (I'll save that for later but it's homework for you). 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.