pubxml in gitignore - by Membrane

Status : 


Sign in
to vote
ID 794103 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 7/16/2013 5:44:12 AM
Access Restriction Public


Hello, in the default .gitignore file in Visual studio 2013, *.pubxml are marked to be excluded from source control. 

If I'm not mistaken the pubxml files are used to populate the list in the publish dialog, and in a scenario with multiple developers and multiple deployment settings, with the current gitignore setting, each developer would need to create the same publish profiles each time a repository is cloned.

Is this correct? and if so, what is the reasoning for not keeping pubxml in source control?
Sign in to post a comment.
Posted by Deon [MSFT] on 4/29/2014 at 12:30 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from:
Posted by Shawn South on 8/8/2013 at 4:22 PM
I would argue this is actually NOT the desired behavior (having the publish profile in source control). The problem is that the .pubxml file contains an absolute path. Different developers may not have the same path structure on their workstations, and so everyone using the same settings is not appropriate.

It appears that this behavior has been changed - Visual Studio 2012 now includes the .pubxml file in source control, which is causing problems for us.

I could also envision a scenario where different developers may not have the same level of deployment access. For example: Junior developers may need to deploy to a shared folder where their files can be reviewed before pushing to the server.
Posted by Microsoft on 7/24/2013 at 2:06 PM
Hello Membrane,

Another internal user raised the same good point you made - this will be fixed for our next external release. Thank you for reporting the problem!

TFS Version Control
Posted by Microsoft on 7/17/2013 at 3:14 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 7/16/2013 at 5:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(