Using the vs12 nuget package extension manager <solution> | "enable nuget package restore" option does what you expect it to do, i.e. adds <solution>\.nuget files that result in nuget packages to not be included in the set of version control managed files. This is goodness as I don’t want to store binaries in my version control repository and it enables project import statements that allow packages to be automatically pulled in a clean workspace environment, e.g. new dev/test wks or build machine.
The new vs12 team explorer offline workspace support currently includes nuget packages in the pending changes | excluded changes | detected changes set when the above nuget package restore option is enabled. You ultimately do not want this happening so you see a valid, smaller, list of detected changes from which I can review and promote the appropriate files.
in a separate thread I was pointed to http://msdn.microsoft.com/en-us/library/tfs/ms245454(v=vs.110).aspx which contained info on a new .tfignore file that controls detected changes behavior allowing you to address this issue, e.g. see option 2 below. I might be reasonable to expect that the enable nuget package restore processing automatically creates that $(SolutionDir)\.tfignore file and the "packages" entry OR adds the entry in cases where that file already exists.
1. use pending changes | excluded changes | detected changes | <select any file under under $(SolutionDir)\packages path and select “ignore by folder (packages)” to generate a <workspace root>\.tfignore file containing a <relative path to $(SolutionDir)\packages> entry and added the file to my pending changeset.
2. since option 1 involved a mgmt. of a x-workspace .tfignore file I move it instead to $(SolutionDir).tfignore and changed the relative path entry to simply be “packages” at which point I had a solution path specific story for having nuget packages folder content excluded from offline workspace detected changes entries.
Comments: Is it possible that you break up the description into paragraphs for better readability?
The new vs12 team explorer offline workspace support currently includes nuget packages in the pending changes | excluded changes | detected changes set when the above nuget package restore option is enabled. You ultimately do not want this happening so you see a valid, smaller, list of detected changes from which I can review and promote the appropriate files.
in a separate thread I was pointed to http://msdn.microsoft.com/en-us/library/tfs/ms245454(v=vs.110).aspx which contained info on a new .tfignore file that controls detected changes behavior allowing you to address this issue, e.g. see option 2 below. I might be reasonable to expect that the enable nuget package restore processing automatically creates that $(SolutionDir)\.tfignore file and the "packages" entry OR adds the entry in cases where that file already exists.
1. use pending changes | excluded changes | detected changes | <select any file under under $(SolutionDir)\packages path and select “ignore by folder (packages)” to generate a <workspace root>\.tfignore file containing a <relative path to $(SolutionDir)\packages> entry and added the file to my pending changeset.
2. since option 1 involved a mgmt. of a x-workspace .tfignore file I move it instead to $(SolutionDir).tfignore and changed the relative path entry to simply be “packages” at which point I had a solution path specific story for having nuget packages folder content excluded from offline workspace detected changes entries.
Comments: Is it possible that you break up the description into paragraphs for better readability?