Server Side Inspections (.NET) with Build Parameters

I'm looking for a way to run the Inspections (.NET) build runner against a Visual Studio Solution and is failing because the "Solution has unresolved references:". The reason it's failing is legitament, because our build server doesn't have any software packages that it extends, physical installed on the machine, instead it pulls the assemblies from a respository. The reason we take this approach is because this allows us to support multiple verions of the software on the same machine.


Is there a way to specify build parameters to the Inspections (.NET) build runner (similiar to the Visual Studio (sln) build runner), that way it can be confiured to resolve the references based on the parameters?

3 comments
Comment actions Permalink

Yes, virtually it is possible. You could specify config parameter in TeamCity build configuration and reference it in HintPath sub-element of Reference element in your project files (.csproj).
But it will work only in next 8.0 EAP. With that version we will release new version of .net cmd tools with full MSBuild project model support.

0
Comment actions Permalink

That's good news, I'll take a look at the 8.0 release once it comes out.

0
Comment actions Permalink

Any time frame for when 8.0 is getting released?  I am looking at moving my system to EAP soon, and wanted to know how many more EAPs are planned until release.

Thanks,

0

Please sign in to leave a comment.