Hi,I am trying to configure an existing Wt application to run with Microsoft IIS. I have followed the wiki instructions and I have succeed running the Debug version. The problem starts when I try to run the Release version.
At IIS level I have configured one virtual directory for each dll, Debug and Release, under the same Web Site (Default Web Site) and using the same Application Pool (DefaultAppPool), with all configuration tweaks recommended in the ISAPI wiki.
When I surf to the Debug version all run smoothly (including the resource folder and local file folder stuff) but when I try to use the Release version I get a "Service Unavailable, HTTP Error 503: The service is unavailable" at browser level and at IIS level the application pool stop running.
The source code is exactly the same for both Debug and Release versions but using different compilation/linking options (including code optimization options for the release version). Before start a backtracking session to figure out what compiler/linker options are generating the problem I would like to ask if you already have any documented issue about this situation.
Thanks. Regards. ________________________ Mario Diethelm Guallar
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
