#1
|
|||
|
|||
VS.NET link file build problem
We have VS.NET C# project. This is a Class Library, not a web project, with only source code *.cs files.
The project was building successfully as part of a solution in VisualBuild Pro, using the “Make VS.NET” step. Two new files were added to the C# project. These files are shared across the solution, so they were added as links to files outside of the project’s folder hierarchy (i.e. in VS.NET: “Add Existing Item” -> browse to file - > Use “Link File” command, instead of “Open”. VS.NET then compiles successfully. However, when attempting to rebuild in VisualBuild Pro, the build would fail, with the following error: Details: Step: Build [projectname] Status: 1 Output: Pre-processing... [projectpath].csproj...setting properties... [solutionfolder]..\..\..\[projectpath].csproj...setting properties... Error pre-processing project file '[solutionfolder]\..\..\..\[projectpath]': Could not find file '[linkedfilepath].cs'. Is this just a feature that isn't implemented in VisualBuild? We are going to use a source control workaround but it would be nice if this was supported. ...Dave |
#2
|
|||
|
|||
Is one of the linked files named AssemblyInfo.cs? It does appear that the VS.NET action does not currently handle that file being a linked file when updating properties or versions.
|
#3
|
|||
|
|||
yes, the files are all *.assemblyinfo.cs.
|
#4
|
|||
|
|||
The download has been updated with a fix for this (VisBuildDOTNET.dll version 5.2.0.5).
|
|
|