When I modify an existing publish profile, Visual Studio 2013 Update 1 does not always save the corresponding pubxml file in the /Properties folder. I'm playing a constant game of modifying files until my changes are registered correctly in the file system.
For example, one publish profile that I edited and "saved" using the prompt has its pubxml file marked as delete. I suspect the profiles are cached and Visual Studio 2013 is not reflecting what's in the file system in real time.
The save prompt only shows up when I go to another profile or hit the publish button. It would be nice to have a save button that would force the pubxml files to show the latest.
Does anyone have a clear workaround this? I had a similar experience with web.config transformation in the same project and ended up editing the project file.
I'm certain this is not bound to the specific project I am currently dealing with as I see the same behavior in other projects. I never had this issue in Visual Studio 2010.
You'll not see this issue if you have just created new profiles. I am only seeing this behavior when I modify the existing profiles.