Visual Studio Profile Publishing - Why not track source control?

Question

I studied deployment options for my ASP.NET web application by creating a publish profile when I noticed that .pubxml files are included in this .gitignore file (which I used):

https://github.com/github/gitignore/blob/master/VisualStudio.gitignore

The search around seems to be that either the links to the publication profile or the links in the publication profile contain absolute paths or other information that can only be valid on the local machine at that time.

Can anyone confirm the rationale for this exception?

Answer 1

I cannot confirm the reasoning, but I can tell you what we are doing. I am including .pubxml files in the source control because either of us can publish in our DEV or TEST environments. I even checked the files myself and did not see any local paths. But keep in mind that we are using web deployment, if we all have access to the same server for deployment, then there is no problem.

So, this really, IMO, depends on what deployment options you use, and if all your teams have access to the same servers.

Our .pubxml files do not store credentials, and no local paths are stored.

Answer 2

. , , . .