I’m working to create my first build with .NET 4.5 project out of SVN.
My first step is just to get the solution to build. I have 1 configuration at this time, and I’m using a global repository.
I have 2 stages: 1 - create directory, 2 - MSBuild
The directory creates successfully, and it’s able to connect and pull down the files from the repository successfully, but my problem when when it attempts the actual build command. The build fails and says it’s unable to find some of the references listed in the project file - specifically those with a network path (format: \server\share\folder*.dll).
In order to investigate I first copied the hint path that was output by the build process that resides in the .csproj file - i copied and pasted that in a file explorer window to be sure there was not some error. The hint path was correct.
Because I’ve only installed this locally for the time being to evaluate the product, I changed the AppPool identity to my own username to be sure there was not a permissions issue with the default identity. That still did not resolve the issue.
Last I changed all continua component services to also use my identity in case it was something outside of IIS, but still this did not resolve the issue.
What should I be looking to change in order to get this to build properly? I can pull down the project to my machine, and it builds without issue.
Thanks for any help you can provide! Let me know if there’s some additional information I can provide to help with the diagnosis.
The build runs on the agent under the user the agent service runs as. There is no need to mess with the app pool identity. We’ll test unc references here today, but I can’t see why they wouldn’t work. You can also specify the path as a property on the msbuild action, e.g :
[code]AdditionalLibPaths=C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web; [/code]
I will try that, though since the MSBuild output shows that it “considered” the correct path, I would think that the additional parameter shouldn’t be necessary in this particular case. Doesn’t hurt to try, though. Thanks.
Just curious if anything was learned from your tests. Thanks for your help.
I’ve tested the situation you were describing and didn’t have any errors myself - so could you please send through a copy of the .csproj file and also a screenshot of your build log output through to the support email address- hopefully we can track the problem down with those.