Aug 12, 2014 at 8:33 PM
Edited Aug 12, 2014 at 8:34 PM
Just thought I would give you some tips on my experience with vcdeploy.exe
- IIS6 management compatibility tools installed in Windows Features
- Compiled vcdeploy with VS2008 sp1
- all of the SRC elements in your deployment .xml file are capitalized
- Deploying atl server apps to IIS7.5 usually means you need to create a 32 bit app pool. This can be accomplished through the IIS gui or by using appcmd. If you are using legacy libraries (such as ATL71.dll) make sure they are in the syswow64 folder.
- The <APPISOLATION>2</APPISOLATION> node in the deployment .xml file should be like this (isolated)
- vcdeploy automatically creates the handlers for you in IIS7.5. They have some obscure name like AboMapperCustom-12xxxx
- If you plan on hosting more than 1 atl server app per site, you will need to delete the second AboMapperCustom-1xxx handler (which vcdeploy automatically creates) and manually create an isapi handler using the gui.
- Don't forget to edit the script map so that you give your Isapi execute permissions.
- Don't forget to map your application to the correct application pool in the basic settings section of the IIS7.5 gui
- Also don't forget to set the Isapi and CGI Restrictions to Allowed for each Isapi
- using icacls, set read and execute permissions on your dll's for the app pool