Hello,
If I'm not wrong, you can choose where to extract your embedded files. Just when need to extract a file you need to provide a target path in order to be extracted. Anyway you can use the "[PubDir]" anytime and probably is the best option you can choose. In fact it's a bad idea to use "static" paths in our software because we cannot know if other computers have these paths availables or not. Probably not. So we need to avoid this.
So the "[PubDir]" variable is the starting point for paths relatives to your executable's. However, sometimes you need a little more than this variable. NeoBook have some other variables that allows you to know certain system paths, and plugins like
npInfo allows you to know some special system paths like the user documents, the common application data path, etc. You are encourage to use this kind of variables instead hard writen paths.
Sometimes you can need a system or user path (say "My Documents", for example) because "[PubDir]" can be not the best choice. For example, supose you need to extract a file from your publication and this are executed from a CDROM. In this case you cannot use "[PubDir]" in order to write anything, because the any CDROM path are writable. In cases like this you can use the NeoBook paths or as I suggest before a plugin like npInfo.
So in conclusion (and in my honest opinion/experience):
1º Avoid the use of hard writen paths like "C:\xxx\yyy" or something else. Simply never use something like that.
2º Use "[PubDir]" always than possible, deploying your publications files accordingly (relative to your executable's).
3º When you need other paths use others NeoBook path's variables or something like npInfo to obtain the right path
Hope this can help you in some manner.
