I have a few projects that I had configured for Web Deploy Packaging using VS 2010. I had configured these to pick up the local IIS settings and include them in the deployment process. Thus, a password was set for these. This worked just great when packaged using VS 2010. We use the IIS GUI - clicking Import Application to publish these packages. After selecting the package to import, a prompt displays asking for the encryption password.
The packaging process seems to have changed in VS 2012. When I build a package using this tool, the specified password no longer works to open the file. I can go backwards and build the package using VS 2010 - without changing anything in the property sheets - and it works as expected. However, with both VS 2012 and 2013, the password is not being defined the same way.
Am I doing something wrong?