If your application has no Common Looking Field pages it will show only very basic HTML structure. To fix the issue you can start here:
Read article How to Fix NORMS When It Displays Nothing When Running Locally
Read RDIMS #8252648. However, it is outdated at the moment (Jun-22-2022)
It is assumed that everything is installed in the proper order:
Visual Studio with IIS Express
StreamTagfilter 1.0.6.2 - version is important in the steps below!
CLFPagePlugin
CLFPagePlugin Templates in C:\Program Files (x86)\Transport Canada\CLFPagePlugin\Templates
There are 2 ways of setting the application CLF. It is fully related to IIS Express version. If you installed only VS2019 or below consider 1st way. If you installed VS2022 consider the second. However, keep in mind that if you somehow installed the very latest version of IIS Express then consider the second option. But it is fully ok to try #1 first and if it failed, try #2
Option #1 (oldest versions of IIS Express)
Try to run application first time and get HTML only page. This will initiate IIS Express settings. If you see the blank pages try this:
Go to the source files folder and find hidden .VS folder
There you can find something like
Open config folder and find applicationhost.config file
Open it and find <system.webServer><modules> section
At the bottom of <modules> add this lines. Make sure that you didn’t add it somewhere else
<add name="StreamTagFilter-2.0" type="Utility.IIS.StreamTagFilterModule, StreamTagFilter.NET.2.0, Version=1.0.5.0, Culture=neutral, PublicKeyToken=d3d707ec692e4024" preCondition="runtimeVersionv2.0" /> <add name="StreamTagFilter-4.0" type="Utility.IIS.StreamTagFilterModule, StreamTagFilter.NET.4.0, Version=1.0.6.2, Culture=neutral, PublicKeyToken=d3d707ec692e4024" preCondition="runtimeVersionv4.0" />
The first line designed for .NET 2.0 - 3.9 and is outdated. The second line is for .NET 4.0 and higher. Make sure that the version in the lines is the same as installed version of StreamTagFilter in this example it is 1.0.6.2
Save it and re-run the application.
If this fails, try Option #2
Option #2 (newest IIS Express versions)
…..
Add Comment