Page History
For step-by-step instructions on how to deploy a VLF.NET application, see Check List/Planning Sheet WEB-NET.
Also, see VLF.NET Manual Deployment – An Alternative Way of Deploying VLF.NET
When you save the Framework with the VLF.NET feature activated, additional .NET files are created in addition to the normal VLF.WEB HTML and JS files.
If your Framework was stored in an XML file named My_Framework.XML and enabled for languages ENG and FRA, these additional .NET files would be produced during a save:
ENG | My_Framework_ENG.application My_Framework_ENG.exe.manifest My_Framework_ENG.framework.deploy My_Framework_ENG.app.exe.deploy |
FRA | My_Framework_FRA.application My_Framework_FRA.exe.manifest My_Framework_FRA.framework.deploy My_Framework_FRA.app.exe.deploy |
So there are four files per language, suffixed with .application, .exe.manifest, .framework.deploy and app.exe.deploy.
...
- In the MIME tab, click on the ADD button to add the following Content-type entries:
| File Extension | Value |
|---|---|
application | application/x-ms-application |
manifest | application/x-ms-manifest |
deploy | application/octet-stream |
Or if editing the configuration file with a text editor, in the relevant section add these lines:
AddType application/x-ms-application application
AddType application/x-ms-manifest manifest
AddType application/octet-stream deploy