We started to use Team service on visualstudio.com for our versioning control.
As I don't intend to install vs2015 on the server, how can I download the latest version on the server from the Team service?
compiling and publishing on the server is easy
When you install the VSTS Build & Release Agent from VSTS it will include tf.exe, which is all that's needed to map and download sources from the commandline. An alternative to installing the agent is to install Team Explorer (stand-alone download would be 2013) or download the Cross Platform TFS Commandline tools.
You can also download the TFS Client Object Model through Nuget and call it directly from PowerShell.
As far as I can tell there is no stand-alone download of the TFS/VSTS commandline tool (tf.exe).
Related
I'm new to .net application (non-web application) project and using jenkins for continuous build and release. I completed creating builds for my project and got the .exe and dll files. But i need to repackage it(create a msi) before deploying to servers. So can anyone give a stepwise information for rePackaging and tool to be used with jenkins for packaging. I want to automate this process in jenkins CI AND CD.
Jenkins is not capable to pack any applications directly.
It will always use an external tool via a plugin or installed by you.
In MSI case, you need an windows agent with an app that will receive the command in command line and produce your deliverable.
Applications:
Installshield (very old - paid)
visual studio (paid)
TFS (on premises or cloud) (paid)
MSIX (? I don't know much about it)
WIX (free)
Jenkins plugin here
We are planning to do version control for our SSIS packages. I want to know how to install TFS and configure it to checkin SSIS packages.
I have read this SSIS TFS configuration. But here I couldn't find anything about installation. it contains only connection information TFS. Should I install from SSIS extensions? Should i install Team explorer? It is showing so many options as shown below.I don't know the right one. Also is installing this requires any license? Please guide me here. Any link with the steps is also fine.
I'm using Visual Studio 2015 and SQL Server 2012.
I want to know how to install TFS and configure it to checkin SSIS packages.
Refer to Install and configure Team Foundation Server and Integration Services (SSIS) and Visual Studio Team Foundation Server for details.
Should I install from SSIS extensions? Should i install Team explorer?
Yes, to design the SSIS packages you need to download and install SSDT (SQL Server Data Tools). It's an official addon for Visual Studio which adds templates for SSIS and SSAS projects. Refer to Download and install SQL Server Data Tools (SSDT) for Visual Studio for details.
And you need to install the Team Explorer to connect to TFS and manage the source control.
is installing this requires any license?
It's based on your VS subscription, you can try community version of Visual Studio, it's free.
Besides, find following blogs for your reference, hope that helps.
SSIS 2012 with Team Foundation Server - Part I
SSIS 2012 with Team Foundation Server - Part II
Installing SSIS, SSRS and SSAS with Visual Studio 2019
When I click on 'browse market place' for our production TFS server, it directly links to our VSTS account. If I then try to install the Sonarqube extension I only have the option to get it.
I can install it directly for VSTS or download it for our on-premise environment.
(it behaves the same way for other extensions as well)
The strange this is that on our test on-premise environemnt I still do have the option to directly install it.
2 questions:
1) What can I reconfigure on our production env to get a connection to it in the marketplace.
2) How do I get the downloaded file into our on-premise environment?
Update:
You could still be able to install the extension to TFS. Simply Click get it free option, there should be an option download at the bottom of the pop-up dialog.
You could then upload the locally extension to TFS server follow this tutorial, finally install to your team project collection.
If you are running on TFS earlier than 2017 Update 2, you will need to download and manually install the latest 3.x version of the VSIX.
You can download the VSIX on the "Releases" page of the GitHub repository
Versions 4.x are compatible with:
TFS 2017 Update 2+
TFS 2018
VSTS
You could directly get it from server through url, and it will show as Get it free.
More details please take a look at this tutorial: Analyzing with SonarQube Extension for VSTS/TFS
Beside suggest you could also go through below tutorialshow to get/install extension from TFS/VSTS:
Install extensions for Team Foundation Server (TFS)
Install free extensions for VSTS
I am looking for some more specific support details.
I have managed to persuade our management to use Artifactory.
We currently use the following, mostly for WinForms development. We have several dozen products we support.
Visual Studio 2015 Enterprise
TFS 2012 on Prem (working to persuade management to upgrade this soon)
NuGet 3.5. with Project.JSon
I am just not sure if Artifactory can support some of the older tools we use. I can't find any details on their website that are version specific. It just says it supports "TFS".
I read mention in some samples of Packages.config, but we got rid of those bad boys some time ago. Project.json is much better. Once we move to VS 2017 the project.json goes away too.
Does Artifactory support TFS 2012? Project.Json files?
Artifactory NuGet support is agnostic of how you manage your project, the only requirement is that your builds use supported clients (like the one integrated into VS). You can deploy and resolve your own packages or have Artifactory proxy a remote location (as long as it supports the NuGet API)
TFS support is provided by the MSBuild Artifactory Plugin which collects info from your build and also enables you to resolve dependencies via Artifactory, and deploy build artifacts.
If you are on TFS2012, it's still using XAML build. Which means you need to use MSBuild Artifactory Plugin.
The MSBuild Artifactory Plugin is installed as a "Project
Template" using Visual Studio as follows:
Under Tools, choose Extensions and Updates..., select the Visual Studio Gallery source under the Online section, and run a search for
"Artifactory".
Select Artifactory Template Package extension found, and click Install.
So, instead of TFS version limitation, it should be more related to VS version.
And according to the Artifactory Template Package in VisualStudio Marketplace, which including VS2015.
I've installed the prerequisite (Team Explorer 2013) to the best of my knowledge, but when I try to set up a VCS root to connect to our TFS Version Control server, I continue to get this error message:
"No TFS assemblies were found on the system. Please make sure you have
Microsoft Team Explorer installed. Supported versions: 2015 2013 2012
2010 2008 2005"
The Team Explorer I downloaded from Microsoft just seemed to be a plugin for Visual Studio, which doesn't make much sense as a server-side component. Anyway, I configured a connection to our TFS box within Team Explorer/Visual Studio on my TeamCity server.
So I have two questions that seem to be undocumented by JetBrains:
What does it mean to set up and configure Team Explorer? How can I validate that I have set up and configured Team Explorer on my TeamCity server correctly?
How does TeamCity know how to find the Team Explorer assemblies? Is there some sort of configuration I am supposed to do? Where is this documented?
I guess I'm looking for a true step-by-step set of instructions that make no assumptions about my understanding of TFS or Team Explorer, or any assumptions about what I may have already installed on my TeamCity box.
I've read the two articles on the JetBrains site regarding how to set this up, and they don't cover actually installing and configuring the prerequisites or configuring TeamCity to discover the Team Explorer assemblies it needs.
Team Explorer is the client software that you use to access Visual Studio Team Foundation Server functionality from Visual Studio. You can simply launch Team Explorer on your TeamCity server to create a team project and check in a project, to validate whether it is installed correctly.
I couldn't find any documentation that mentioned how does TeamCity find Team Explorer assemblies. But, based on my understanding, there is no configuration needed to detect Team Explorer. Please make sure your TeamCity server is running under Windows.
If the issue that can't find Team Explorer persists, you can install VS Premium instead of Team Explorer.
Setting up Jetbrains TeamCity for CI with Team Foundation Server:
Install Jetbrains TeamCity
If you are planning on using IIS or TFS on the same server, configure Jetbrains TeamCity to run on a port other than 80 or 8080
Once TeamCity is up and running, you can begin configuring your TeamCity installation for CI Builds.
Log into TeamCity with your user name and password
Create a new TeamCity Project
Create a new build configuration
You will now see a series of build configuration settings that you will have to complete presented in a Wizard-style navigation view.
Enter General Settings
Enter VCS Settings
After entering VCS Settings, Create and attach new VCS Root
Enter the relevant information for your TFS instance
Create a Build Step using Visual Studio as your build runner. You can create as many build steps as you need and specify the order of the steps (similar to a TFS Build Workflow).
For setting up Continuous Integration builds, you will need to specify a Build Trigger. CI Builds will generally use a VCS Trigger that is triggered on each source control check-in.
If you need to pass any parameters to your build, you can configure these in your Build Parameters.
That is all! You can then either run your Builds manually by clicking on the Run button in TeamCity or simply verify that your builds are triggered by the next check-in into TFS.