Currently files are only available to customers with internal access and no public beta is available at this time.
IntraWeb 17 does not have an installer yet and one will not exist until much later in the development cycle. Currently some manual steps are required.
If you do not have IIS installed, it must be installed first.
Because IntraWeb 17 is not hooked into the Delphi back end yet, a web server is required. Any web server will work but these instructions cover IIS only. IntraWeb 17 cannot be run using simply the file system because of browser security restrictions regarding access to local files.
- If you have Skype running, exit it. Don’t worry you can restart it later, nothing will break.
- Open Control Panel and select Add or Remove Programs.
- Select Add/Remove Windows Components.
- Select Internet Information Services (IIS) check box.
- Click Next
- Wait for IIS to install.
- Click Finish.
- Restart Skype if you exited in step 1.
Add MIME Type
IntraWeb 17 uses .iwml files. These can also be served as plain .txt files in case a user does not have access to add new mime types, but this is generally a corner case and even most shared hosts allow custom mime types at least at the application level.
For this setup the MIME type is installed for a specific web site, however the MIME type can also be installed at the server level so that all sites will recognize the MIME type.
Any website or path can be used, but these instructions will use the default website. Select the default web site, and then open MIME types.
Add .iwml as shown below and click OK.
The IntraWeb files need to go somewhere. The easiest way is to find the default wwwroot for IIS and make an IW17 folder and simply extract the files there. Since IW17.zip has an IW17 folder already inside it, extract it to wwwroot directly so that wwwroot only has one IW17 folder and is not nested.
The default folder is:
Assuming that the files are then put in C:\inetpub\wwwroot\IW17 you can now open up a browser and enter the following address.
This URL is a bit fugly, but it is to bypass debugging code that currently exists which at various times may lead you to the current area we are working on rather than the intended landing page.