Hi I have the binary file, in my workspace. i.e. the output dll from the LimeUtilities project. Wich I want to build in a seperate job, and not having it stored as an articfact. I think you got a point about it probably is incorrect use / parameters passed to the msbuild Gotta test further, debugging in a command line style Thanks K
Den søndag den 7. oktober 2012 13.08.34 UTC+2 skrev gboissinot: > MSBuild Plugin is only a wizard in order to help to configure the MSBuild > tool. > Your issue relies on the MSBuild tool. Try to capture the generated command > line generated by Jenkins (with all arguments) and launch this command in > shell for trying to debug it. > However according the log, 'LimeUtilities' project is missing. It is a > layout issue. Do you have it in your workspace? > > On Fri, Oct 5, 2012 at 10:04 AM, Kenneth <kenneth....@gmail.com<javascript:> > > wrote: > >> Hi All >> >> I've got one job building a dll, that uses a dll that i have stored as an >> artifact, and gotten into the outputfolder for that job. >> It still complains about the dependency when compiling though. how should >> i workaround that? >> >> C:\Windows\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : >> warning : The referenced project '..\LimeUtilities\LimeUtilities.csproj' >> does not exist. >> Done building target "ResolveProjectReferences" in project >> "LimeUtilitiesUnitTests.csproj". >> Am I using msbuild plugin correct? >> >> > >
