Hi Steve,
The typical model is to add VDIR_UserName and VDIR_UserPass to InstallWizard.xml and have them entered by the operator running the deploy wizard. Those two properties are intended for server deployments, not in Visual Studio deployments. It's fine to put them in the spreadsheet instead of the wizard.
Since most developers need to configure a specific AppPool identity and no one wants his/her personal user account password in the spreadsheet or .btdfproj, the Deployment Framework assumes that for VS deployments the developer has manually created and configured the AppPool. That's why you don't see it being configured.
FYI, for (future) v6.0 I've completely redesigned and rebuilt the IIS integration.
Thanks,
Tom
The typical model is to add VDIR_UserName and VDIR_UserPass to InstallWizard.xml and have them entered by the operator running the deploy wizard. Those two properties are intended for server deployments, not in Visual Studio deployments. It's fine to put them in the spreadsheet instead of the wizard.
Since most developers need to configure a specific AppPool identity and no one wants his/her personal user account password in the spreadsheet or .btdfproj, the Deployment Framework assumes that for VS deployments the developer has manually created and configured the AppPool. That's why you don't see it being configured.
FYI, for (future) v6.0 I've completely redesigned and rebuilt the IIS integration.
Thanks,
Tom