I am trying to build and deploy an SSRS project (rptproj) but MSBuild does not support this project type. What can I use to build and deploy this project?
I looks like I can use RS.EXE and Dev Env. What are the benefits of each?
It actually is recommended to install Visual Studio on the TFS Build machine to support building various types of projects that MSBuild alone does not support. You don't have to worry about licensing because as long as you have a Visual Studio license then you can put it on all of your machines.
You can find more details here.
Related
I think this is about as basic question as I can have, but what version of Microsoft Visual Studio and what packages do I need to install in order to create SSIS Packages that I can install in SQL Server to run in scheduled jobs? I have done this before, but now whenever I download Visual Studio my toolbox is empty and I cant seem to find any of my data flow tasks no matter what I install. Any help would be much appreciated as this basic task has me a bit frustrated.
For VS2017 and earlier versions, you can easily find it after creating an SSIS project.
In a solution where includes SSIS project:
For VS2019, as this document states the required functionality to enable Analysis Services, Integration Services, and Reporting Services projects has moved into the respective Visual Studio extensions.
To find SSIS Toolbox in your VS2019:
Download the extension for SSIS here
Create a new SSIS project and you can find the ToolBox
I haven't been able to find anything about this directly online. I am about to make an automated Chocolatey script for build agent configuration.
Is MsTest part of Microsoft Build Tools?
I figured out that it is not the case. Visual Studio 2015 is needed, or you can choose to install something Microsoft released separately, called Microsoft Test Agents 2015.
I have a mstest project that uses Microsoft fake assembly. The test methods are executing fine in my local Visual studio ultimate. I never check in the fake dll in to repository (SVN), assuming that it will be created in the build server (Jenkins). Later I understood that the build server is using MSBuild.exe to build the solution and since MSBuild.exe doesn't know how to create the fake assembly, the build seems failing. Installing the Visual studio ultimate in the build server is the only one option or is there any other ways to execute the unit test (like check in the fake dll in to repository).
You need Visual Studio Ultimate or Visual Studio Premium (if you are using a version later than Visual Studio 2012 Update 2) to be able to generate fakes. Also please make sure that your build script is using vstest.console.exe to execute tests. Fakes is not supported by MSTest.exe
I am under Visual Studio 2008 unfortunately and I know that there is the tfs powertools for later versions of viusual studio. But I am tasked with transferring build definitions from TFS 2010 to TFS 2012. How to do it efficiently?
The "Clone Build Definition" Power Tool (from TFS2010/12) only works on Build Definitions in the same Team Project, if they are in separate Team Projects, or Collections it is not possible. This would be the case if you used VS2010/12 instead of 2008.
The assumption from Microsoft is most likely that the Build process templates may differ, so copying the definition could fail.
is it somehow possible to run tests with it?
I am always getting message:
(CoreTestConfiguration target) ->
MSBUILD : warning : Visual Studio Team System for Software Testers or Visual Studio Team System for Software Developers is required to run tests as part of a Team Build.
Well it is possible, we have such configuration (VS2010 project and TFS2008 where we store it). Probably when you set up the build on build server you have chosen to run the tests with this build - so please install proper Visual Studio version (Visual Studio Team System for Software Testers or Visual Studio Team System for Software Developers) on the Build Machine. Or setup the build without test option.