(Replacing message template with parser tag) |
No edit summary |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
<message>Write the content here to display this box</message> | <message>Write the content here to display this box</message> | ||
For Turnkey on .netCore, there is a page: views\\turnkey\\StartupViewTemplate.htm that will be updated with : | For Turnkey on .netCore, there is a page: views\\turnkey\\StartupViewTemplate.htm that will be updated with: | ||
System.IO.File.ReadAllText(path).Replace("###BASEURL###",Common.GetApplicationServerUrl()); | System.IO.File.ReadAllText(path).Replace("###BASEURL###",Common.GetApplicationServerUrl()); | ||
And then returned to client, if the TurnkeyApp has not fully started yet. | We also do a replace of the tag '###GOALURL###' , this will be the original url the user tried to reach, even if this may seem trivial And then returned to client, if the TurnkeyApp has not fully started yet. | ||
The Turnkey app takes some time during startup to extract the model from MDrivenServer and expand the model out to disk to be faster the next time it starts - if the model has not changed checksum. | The Turnkey app takes some time during startup to extract the model from MDrivenServer and expand the model out to disk to be faster the next time it starts - if the model has not changed checksum. | ||
| Line 10: | Line 10: | ||
_AssetsTK\\Views\\EXT_OverridePages\\StartupViewTemplate_AppOverride.htm. Read more on [[Documentation:AssetsTK|AssetsTK]]. | _AssetsTK\\Views\\EXT_OverridePages\\StartupViewTemplate_AppOverride.htm. Read more on [[Documentation:AssetsTK|AssetsTK]]. | ||
For Turnkey on Framework, the StartUp page uses the built in IIS support that requires you to change the web.config file as described in this article: [[Documentation:Simple_URLs_and_Azure_redirect]] | |||
You should not underestimate the work with waiting for server start + routing through external login + handling this for both client side urls (# like angular) and full urls like DWV and Blazor. | |||
For Turnkey on Framework, the StartUp page uses the built in IIS support that requires you to change the web.config file as described in this article: [[Documentation:Simple_URLs_and_Azure_redirect|Simple_URLs_and_Azure_redirect]] | |||
{{Edited|July|12|2025}} | |||
[[Category:MDriven Turnkey]] | [[Category:MDriven Turnkey]] | ||
[[Category:MDriven Server]] | [[Category:MDriven Server]] | ||
[[Category:IIS]] | [[Category:IIS]] | ||
Latest revision as of 05:00, 25 March 2025
For Turnkey on .netCore, there is a page: views\\turnkey\\StartupViewTemplate.htm that will be updated with:
System.IO.File.ReadAllText(path).Replace("###BASEURL###",Common.GetApplicationServerUrl());
We also do a replace of the tag '###GOALURL###' , this will be the original url the user tried to reach, even if this may seem trivial And then returned to client, if the TurnkeyApp has not fully started yet.
The Turnkey app takes some time during startup to extract the model from MDrivenServer and expand the model out to disk to be faster the next time it starts - if the model has not changed checksum.
You can also modify the displayed page by providing a page that works the same way under the name:
_AssetsTK\\Views\\EXT_OverridePages\\StartupViewTemplate_AppOverride.htm. Read more on AssetsTK.
You should not underestimate the work with waiting for server start + routing through external login + handling this for both client side urls (# like angular) and full urls like DWV and Blazor.
For Turnkey on Framework, the StartUp page uses the built in IIS support that requires you to change the web.config file as described in this article: Simple_URLs_and_Azure_redirect