Keep application pool associations

Install Processes
Out of the scope

If I set an eSpace to a custom IIS application pool different from "OutSystemsApplications", this association will be lost if I publish the eSpace again. The eSpace will be moved to OutSystems default application pool.

The publishing process should not reset my application pool association.

This is very useful in x64 environments where I need to have my eSpace on a 32bit application pool:


Created on 14 May 2010
Comments (2)
I believe that the expected behavior should be to maintain the current application pool of the eSpace and thus if this isn't happening, it is a bug and not a feature request.

Can you submit the details of your configuration to support or create a post in the network detailing the circumstances under which the pool is reset?
Changed the status to
Out of the scope

out of scope