IIS holding dlls ...

[pfelsted]

I have an IIS application. We make alot of changes to it during the day as others are using it. It is currently written in ASP. We are migrating to ASP.NET. So an approach we are taking is moving ASP script code into VB.NET com modules. These can be used in both ASP and ASP.NET.

Anyway, the problem is that once the CreateObject is called on the COM module we can not replace it without doing an iisreset. If I turn off Cache ISAPI exensions then it is more easy to replace (we get a message about resource not availbe for about 5 secs). I know this will affect performance but we are constantly making changes adding new functionality etc. We have also noticed that when we turn offf Cache ISAPI exensions now any objects we hold in session data get deleted.

Questions:
1) Is there an easy and performant way to replace dlls loaded by IIS without restarting iis?
2) Why does turning off Cache ISAPI exensions cause session data to be destroyed?
3) Maybe our approach to going to ASP.NET is wrong any suggestions?

Thanks

[kenobewan]

My belief is that you have a project management issue, welcome to the level of corporate level applications. This is where upgrades are handled through the stages of project management and outages are scheduled for times of little or no application usage; and minimal customer inconvenience.

You can of course keep searching for methods to avoid the issue and your questions all have solutions. Its up to you :).