Closed andrew-potachits closed 7 years ago
I guess this may be something to do with the routing: the browser ends up here after navigation:
http://localhost/My.Subfolder/#
however I don't use any routes in my application (and not use routing at all).
The issue was caused by link.
I'm developing the Angular2 application that is bootstrapped from ASP.NET MVC controller. I deployed the whole web application to IIS under virtual subfolder. So, the url to application looks like this (for dev):
http://localhost/My.Subfolder/MyController/Action?param1=123
the page baseurl is set to /My.Subfolder/:
<base href="/My.Subfolder/"/>
Everything works fine until I open the color picker and click the element that opens color picker. It looks like during dialog initialization, something causes angular to navigate away.
How can I help diagnosing the problem?