Hi!
Cassini does attempt to close the socket and free the port when unloading an application, but that does not guarantee that the port will actually be freed. You should see a Warning entry in the Event Log when an application is unloaded but its port is not released. In the upgrade scenario your application may fail to start (with an error entry in the Event Log) if Cassini can't start listening on the port. We usually see this issue on slower machines. When you are installing an application on a static port, your installer has to be sure the port is free. We provide the functionality in the
Cassini Configuration API. If you can't use .NET programming in your installer, you could write your own code that will attempt binding the socket at port 8080. If it's not free, you could wait a little bit to ensure it's not a socket that is tied up by unsuccessful release of the port, and then if it does not free up, you would either fail the installation, or offer listening on another port.
Please let us know if this helps.
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.