.NET MSBuild - Best practise for .Net Framework package jobs?

I'm wondering how I should create package jobs for .Net Framework with TeamCity.

Due to the switch to .NET MSBuild, we're having an issue creating web application package. When using the old meta runner, we could define an output directory for the compiled software. We can't define an output directory in the .NET metarunner.

Microsoft recommends using MSBuild for compiling .Net Framework. So I'm rather confused why TeamCity is recommending going for the new .NET metarunner.

 

0

Please sign in to leave a comment.