The IronWrapping system allows you to embed files directly into the host application (or into separate AXS files). The files will be hidden from the user and is only accessible by the host application.  

Note that because the files are completely virtualized by the IronWrap system, the host application accesses them in exactly the same way it would if they were physically on disk as separate files.  Thus, no changes are necessary to the source code of the protected host application.

What Does Embedding Files Do?

Embedding files adds another layer of protection to your programs.  The more files you embed, the more difficult it would be for any potential cracker to remove the DRM system from your program.

What Kinds of Files can I Embed?

You may choose to embed binary files that your program uses (like DLL's or EXE's). Your program accesses these files in exactly the same way it would if the binaries were on disk as separate files.

You may also choose to embed read-only data files.  This can be any kind of file whatsoever, but could include movies, textures, text-files, help-files, graphics of all kinds, etc, etc.

It is important to note that the files are read-only. Your programs cannot successfully write to an embedded file.

How are the Embedded Files Themselves Protected?

The files may be encrypted and compressed just like the host itself - all individually using their own keys.  Other advanced protection options are also available for binary files, (such as relocation table protection, resource protection, and the IronWrap API Filter Protection).

Binary files may even be set to auto-execute if you wish.  If you choose to auto-execute a binary file, the program is executed before the host is executed.  You may choose to pass any command line parameters to the embedded executable as well as optionally wait for the embedded executable to terminate before passing execution to the host.