I've a .net web application that creates a new directory on the server, followed by copying classic ASP files into the new directory.
When I do this on my pc and then try to point to one of these files e.g.
<!-- m --><a class="postlink" href="http://127.0.0.1/new_directory/index.asp">http://127.0.0.1/new_directory/index.asp</a><!-- m -->
the server claims not to find it. This is remedied if I restart IIS but this won't do.
Is there something I need to do?
ThanksHumm.... good question! The application might need to restart (just the application, if you restart iis the application will restart). You might be able to force a restart without restarting iis, but I do not know how you would do that, though I believe it is possible.The only problem might be if I lose any session variables (I don't think that I have any at that point but I should check.
I'll explore this idea anyway, it sounds like it might work.
Thanks.yes, if you application dies all of the active sessions for that application would die too. This could create a real problem if you have several users.
When I do this on my pc and then try to point to one of these files e.g.
<!-- m --><a class="postlink" href="http://127.0.0.1/new_directory/index.asp">http://127.0.0.1/new_directory/index.asp</a><!-- m -->
the server claims not to find it. This is remedied if I restart IIS but this won't do.
Is there something I need to do?
ThanksHumm.... good question! The application might need to restart (just the application, if you restart iis the application will restart). You might be able to force a restart without restarting iis, but I do not know how you would do that, though I believe it is possible.The only problem might be if I lose any session variables (I don't think that I have any at that point but I should check.
I'll explore this idea anyway, it sounds like it might work.
Thanks.yes, if you application dies all of the active sessions for that application would die too. This could create a real problem if you have several users.