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.
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 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 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.
I just installed SQL Server 2005 and it installed Visual Studio 2005 too. What's the point of this? Is there an option in the SQL Server installation that can prevent this. If I uninstall Visual Studio now will it mess anything up? What if I now install Visual Studio 2008 too?
The visual studio that you get is a shell called Business Intelligence Development studio and it allows you to create Analysis Services, Integration Services, and Reporting Services projects. Also it allows you to deploy those projects to your SQL Server. If you already have Visual Studio installed, it will add those project types to it.
With the Development Studio you can add .Net projects such as C# or VB to your Analysis Services or Reporting Services projects to create custom components for them. There are additional benefits, but you should just do a search for Business Intelligence Development Studio to see what else can be done.
EDIT:
I just noticed that you were asking about what happens if you uninstall Visual Studio 2008. There should be a listing under your installed Programs called Visual Studio Shell or something of that nature, which is the Business Intelligence Development Studio and is independent of the main Visual Studio 2008 install. Both of them will allow you to create the Ms SQl Projects that I listed above. When you uninstall Visual Studio 2008 it won't uninstall this application and vice verse. If you do accidentally delete it, you can always install it again using your MS SQL CDs. There are instructions on the web to do so.
The version of Visual Studio that gets installed is necessary for doing the work you need to do in SQL Server. The old tools are going away, and this is part of the new.
Personally, I miss the Enterprise manager and SQL Query Analyzer from the SQL Server 2000 days, but they aren't likely to come back.
Edit - added
OK. The above was a bit flippant for an answer.
But to answer your comment, Management Studio IS Visual Studio, configured and modified to work with SQL Server.
Not too familiar with dtsx packages - can they be created/run outisde Visual Studio?
Is BIDS (Business Intelligence Development Studio) just required to do all the above (in Visual Studio) or is it an independent development enviroment for dtsx packages?
Please shed some light if you can (and get some eazy rep)!
Absolutely! Just double click on it (launches dtexecui.exe) or use the dtexec command. See how all the ways stack up here.
Answering some of the other questions:
BIDS is the sole environment to build SSIS packages. You could handwrite the XML, but good luck to you on that one. BIDS is a standalone product as well as an integrated one, so just install it off of the SQL Server DVD. You will not have to buy Visual Studio in order to use BIDS.
Visual Studio is based on sets of functionality in Visual Studio "packages" (vspackages). BIDS is just Visual Studio with the vspackages for SSIS, SSRS, and SSAS development. Those same vspackages can be used through "normal" Visual Studio if you already have that installed.
If you don't have Visual Studio installed, then installing BIDS installs it.
Although you can run SSIS packages outside of VS, there's little you can do to debug them that way. It is not practical to create them outside of VS.
Is there a reason you want to do this?
Yes, you can get rid of VS2005 as far as BIDS is concerned. Install Visual Studio 2008 SP1, then install the SQL Server 2008 bits you need, including BIDS 2008.
If you still need to work with SQL Server 2005 SSIS packages, then you still need VS2005 to work with them.