Managing static content - linked resources or what?

[paperjam]

I have quite a lot of static client-side content files that are delivered to my embedded browser via CefSchemeHandler.

Right now, these are linked into the exe as resources but I wondered if there are better ways to do this that require less maintenance. Ideally I'ld like my Visual Studio build process to wrap up all files in my content folder either into the exe itself or a separate file. So when I add a new content file, I don't have to change resource.h, .rc, and my scheme handler code.

What are others doing?

[magreenblatt]

You can have a pre-build step that creates a zip archive and then embed that archive as a resource. Files can be extracted from the archive using CefZipReader. See the WBEA application for an example of using CefZipReader (viewtopic.php?f=11&t=194).