tfs2010 - How to specify the solution file location for versioning assembly info files in MSBUILD -


I'm negligible with this for a day but there is no luck. The assembly edition with the MSWUILD was used to work first, but recently we have moved the solution files to a separate folder within the project's root, and since then the version is not working.

Code folder

-> Project A folder

-> ProjectB folder

-> ProjectC folder

-> Solution folder

* The first solution (.sln) files were under the Code folder.

When we run MSbold I get the following warning.

Delete Workspace

No assembly information file was provided

The cut version of the build log below is.

Delete Workspace

00:00 Delete Source Directory

00:00 Create Workspace

01:14 Get Workspace

00:00 Verging Assemblies

00:00 Assembly Assembly and AssemblyPhilion assembly version processing: use version number pattern included in definition of build

00:00 Assign all assembly property values ​​(b) assemblies with the following pattern Version: AssemblyVersion (1.0.0.0) and Assemb LyFileVersion (yyyy.mm.dd.b) No assembly information files provided

<. / Blockquote>

Below is the output of MSBuild that logs

  & lt; Local: VersionAssemblyInfoFiles AssemblyFileVersionPattern = "[AssemblyFileVersionPattern]" AssemblyInfoFilePattern = "AssemblyInfoFilePattern]" AssemblyVersionPattern = "[ "[BuildConnectInfoFiles]" ForceCreateVersion = "[ForceCreateVersion]" SP: VirtualizedContainerService.HintSize = "BuildDirectory =" [BuildDirectory] "BuildNumberPrefix =" [BuildNumberPrefix] "BuildSettings =" [BuildSettings] "DisplayName =" Version Assemblies "DoCheckinAssemblyInfoFiles =" [DoCheckinAssemblyInfoFiles] "200,22" mva: VisualBasic.Settings = "assembly reference and imported namespaces are sorted as XML namespaces" UseVersionSeedFile = "[Us EVersionSeedFile] "VersionSeedFilePath =" [VersionSeedFilePath] "workspace =" [workspace] "xmlns: local =" clr-namespace: TfsBuild.Versioning.Activities; assembly = TfsBuild.Versioning.Activities "& gt; & Lt; Summary: WorkflowViewStateService.ViewState & gt; & Lt; SCG: Dictionary X: TypeArguments = "X: string, x: object" & gt; & Lt; X: Boolean X: main = "ShouldCollapseAll" & gt; False & lt; / X: Boolean & gt; & Lt; X: Boolean X: main = "ShouldExpandAll" & gt; This is true & lt; / X: Boolean & gt; & Lt; / SCG: Dictionary & gt; & Lt; / Abstract: WorkflowViewStateService.ViewState & gt; & Lt; / Local: Version: ThemesInfofiles & gt;  

I also considered the suggested solution but there is no luck. Can anyone tell me in the right direction? I am not an expert in MSBuild.

Thanks in advance.

I have finished the following solution. We have no option to move all solutions at the root level of the project.

A. Create a new solution i.e. something App.Lib.Versioning.sln This solution will remain under the root folder and it will only be used for the rest of the versions.

B. That Project for T SomeApp.Lib.Versioning.sln will remain at the same level as the remaining projects (.csproj).

then the new structure

code folder

-> project a folder

-> projectb folder

- > Project C folder

-> Solution folder

-> SomeApp.Lib.Versioning.sln

-> SomeApp.Lib.Versioning folder

c. Now I refer to SomeApp.Lib.Versioning.proj from one of the solutions in the software folder. This means some App.Lib.Versioning.proj has two solutions that are linked to the hit.

The project that displays the build version, some apps. Versions. POS

will use the standard file type. According to the standard build version someApp.Lib.Versioning.proj will have the correct build version (SomeApp.Lib.Versioning.sln is in the root level)

Note: This is just a work and not the ideal solution. This project will not be a version of all the assemblies. For example, if we want to know which version of which assembly was created in which version it will not work, it is just a holder to get the build version of the solution.


Comments

Popular posts from this blog

sqlite3 - UPDATE a table from the SELECT of another one -

c# - Showing a SelectedItem's Property -

javascript - Render HTML after each iteration in loop -