I've created a sample website using the 'Ext.NET Classic Mvc Application' project template. When I run this website using Development-Time IIS debugging support, links to the core ExtNET scripts are not resolved relative to the application virtual root path. Instead, they are resolved relative to the website root path. My website is running at the location http://localhost/extnetcoresample, so I would expect links to the core ExtNET scripts to be generated as http://localhost/extnetcoresample/extnet/. Instead, they are being generated as http://localhost/extnet/ which isn't resolvable. I would have expected the Ext.NET framework to be able to automatically take account of the application virtual root path when generating these links, as it did with the legacy .NET Framework versions of the product. I did try setting the base path in my Startup.cs file by adding a call to 
app.UsePathBase("/ExtNetCoreSample");
in the 
Configure(IApplicationBuilder app, IWebHostEnvironment env)
method, but this didn't have any effect. Please can you advise whether this is a bug, or if there is something else I need to do when running a website from a subfolder?