[CLOSED] Define different entry points for the application


Hello everyone,

we are in the process to migrate a VWG application to WiseJ and need guidance to achieve one of our goals.
Hopefully you canpoint us in the right direction or let us know if our goal is achievable at all.

Our Goal

We would like to define different entry points for our application.
Let me highlight our goal in a quick example:

Entrypoint Displayed Page
/ DefaultEntryPointPage
/special SpecialEntryPointPage

So if the user calls “https://example.com/special a different entrypage will be shown. For all other requests the default page will be shown.

The WebGUI Approach

It was possible to define different EntryPoints within the web.config of WebGUI

<?xml version="1.0" encoding="utf-8"?>
           <Application Code="special" Type="SpecialProject.SpecialPage, SpecialProject" Authentication="Default" Stateless="False" ForceSSL="False" />
           <Application Code="app1" Type="Application1.Page1, Application1" Authentication="Default" Stateless="False" ForceSSL="False" />

Our field tests

We tried to replicate the behaviour by checkinf the Application.Uri path during program startup and set the Application.MainPage accordingly.
To achieve this we added a rewrite rule to the IIS that rewrites the “/special” request to “Default.html” and “/” respectively.
Both approaches loaded the WiseJ Application but the page only showed the spinner briefly and after the spinner disappeared the page we saw was an empty white page.

Our Questions

  • Is it possible to achieve our goal?
  • Can you think of a reason the different pages stay blank?
    • Did we forget anything?
    • Are the rewrite rules correct?


  • Please find a sample project attached, which shows our approach


Thank you very much in advance.

  • You must to post comments

Hello Frank,

thank you very much for your answer.

I forgot to mention that we tried the approach you mentioned, but were looking for an alternative way for the following reasons

  • The URL “https://example.com/special” looks more natural for the enduser compared to “https://example.com/special”
  • Changing the hash value does not fire a new request

As far as i am aware, we would need to handle the HashChanged Event to register a user changing the hash value to change the displayed page accordingly.

Are there any other ways to accomplish our goal, or is using the Hashvalue the only option?

  • Frank (ITG)
    Can you please clarify this sentence: “The URL “https://example.com/special” looks more natural for the enduser compared to “https://example.com/special”” TIA, Frank
  • Florian Bogner
    Excuse me, i made a copy and paste error. The sentence meant to be: The URL “https://example.com/special” looks more natural for the enduser compared to “https://example.com#special” And the sentence means that our users are used to URLs containing the slash and may not be used to URLs containing the hash symbol so we were looking for a solution with “normal” URLs. I hope that makes sense.
  • You must to post comments

Hi Florian,

thanks for your interest in Wisej.

Did you take a look at our DeepLinking example at GitHub:


It shows the concept of having different URL entry points and
I hope that gives you a direction for your migration.

Please let us know if you encounter any further questions.

Best regards

  • You must to post comments
Showing 2 results