I'm hoping this isn't closed as a duplicate of Is TF Build 2013 compatible with TFS 2012? because the question is almost two years old, the only answer it got was of low quality and the answer was not accepted.
My company is currently running an on-premises TFS 2012 Application Tier with a TFS 2012 Build Agent, which builds BizTalk 2013 projects. We're considering an upgrade to BizTalk 2013 R2, but we know that BizTalk 2013 R2 doesn't build in VS 2012.
We know we will eventually have to upgrade our TFS installation, but for now we don't have the resources and we're looking for a short-term solution. Our idea was to investigate upgrading only the Build Agent to the 2013 version (or potentially even just the Visual Studio installation on the Build Agent machine?) so that we don't have to expend the effort to upgrade both systems simultaneously.
Specifically, is it possible to build BizTalk 2013 R2 projects if the TFS Application Tier is still 2012?
More generally, is it possible to upgrade only the Build Agent to 2013 or higher if the TFS Application Tier is 2012?
I'm not sure as I don't use Biztalk, but I'd think installing VS2013 on the TFS2012 build server would resolve it.
Where I work we have TFS2012.4 and VS 2012.4 & VS2013.4 on the installed on the build server so that we can build newer project types and .net 4.5.2 stuff.
You could test by running a build agent/controller, either on your machine or in a Hyper-V VM if you have Win 8 or greater - just remember to "tag" the agent so it doesn't get picked up.
TFS and Build of Biztalk are two separate thing, you don't need to upgrade TFS to upgrade Biztalk. If you install VS 2013 on build agent that will fix yr problem. In order to test I would recommend to have a new build server with VS2013 and Biztalk 2013 R2.
Related
In the process of evaluating the way we develop and deploy apps to our 2 environments (Test & Live).
Current setup:
Test Server with VS 2013 and BizTalk 2013R2 installed (all app dev is done here, tested and then exported to MSI and installed on Live BizTalk server)
Intended setup:
Local Developer Desktops would have VS 2013 and BizTalk 2013R2 installed, with app development development done locally. Apps would then be deployed to Test Server for QA, and finally exported as MSI across to Live Server.
Questions;
Can you deploy from a local desktop to a network/server location?
Do you have to develop in VS 2013 to deploy to Biz 2013 R2, or are the compatibility settings in VS 2019 that you can configure to emulate VS 2013?
Can you deploy from a local desktop to a network/server location?
No, you cannot deploy from Visual Studio to another server.
What you can do however is to create a build server that gets the code from source control, and creates a MSI package, that is then pushed out to your target server via tools such as Microsoft DevOps, BTDF, Octopus Deploy, Power Shell scripting etc.
Automating your build and deployment reduces a lot of risks.
Do you have to develop in VS 2013 to deploy to Biz 2013 R2, or are the compatibility settings in VS 2019 that you can configure to emulate VS 2013?
Each version of BizTalk needs to be developed in a specific version of Visual Studio with the appropriate BizTalk SDK installed. So no, you cannot use Visual Studio 2019 for BizTalk 2013 R2.
I'm upgrading from Visual Studio 2012 to 2013 for MSBI.
I have downloaded Visual Studio 2013 and SSDT separately.
SSDT fails to install:
Unspecified error. One or more issues caused setup to fail. Please
fix the issues and then retry setup.
It creates a log file every time.
If you want to develop Business Intelligence projects, what you need is SSDT-BI, not SSDT. SSDT is for SQL Server database projects and publishing etc.
SSDT-BI is for BI projects such as Integration Services, Reporting Services and Analysis Services.
You can download SSDT-BI 2013 from here.
If you want it only for business intelligence projects you don't need to download Visual Studio separately, SSDT-BI comes with Visual Studio shell.
You can as well start using SSDT-BI 2015 which supports SQL Server 2016 too.
Good luck.
We have several .NET solutions (desktop apps and an MVC website) we've been working on. The projects were all built in VS2013 and are hosted on a TFS 2013 server. We would like to update to VS2015...but I'm a little wary about it. If we update to VS2015, do we also need to update to TFS 2015? Or is it smarter to run VS2015 alongside VS2013? If we do the latter option, would be still need to update TFS to 2015?
You can quite happily use VS 2015 and TFS 2013 together.
In the olden times (TFS 2010 or earlier) you might have wanted to keep the old version of VS around to manage the TFS server but these days most functions are available from the TFS web UI.
The only thing you would need to be careful with is if you are using TFS Build for your CI server. If this is the case you will need to update the version of VS installed on your build agents.
You don't need to update to TFS2015. You can still use VS2015 with TFS2013.
But if you want to build for C#6/.Net 4.6 applications, you need to pay attention to your build enviroment. Such as install MSbuild Tools 14.0, amend the build templates to point to MS Build version 14.0. For detail you can reference: TFS 2013 building .NET 4.6 / C# 6.0
One of our TFS 2010 requirements is to support software projects that still use Visual Studio Team System 2008 for development. My question is whether a Build Server based on Team Build 2010 can compile 2008 code by itself. I mean connecting to TFS 2010 using Visual Studio Team Suite 2008, which means we are planning to install the Forward Compatibility Update on all development machines.
We have an existing TFS 2008 system and according to that the build server requires VSTS 2008 to be installed in order to compile code and run automated tests. I would assume the same for TFS 2010 where VS 2010 Ultimate should be installed in the build server, but we are not sure whether VSTS 2008 is required "as well" in this use case.
I hope someone could share their thoughts about this. Thanks.
As long as you install;
Visual Studio 2008 Team Suite,
Visual Stduio 2008 Team Explorer
VS2008 SP1
and 2008 GDR forward compatibility pack next to Visual Studio 2010 on the buildserver, Team Build 2010 can compile and unittest 2008 solutions. There are however some known issues with Workflow projects, so install VS 2010 and TFS 2010 SP1 and test your solutions.
I need to get VS 2010 projects that are using Visual Studio Tests building on a TFS 2008 build server. I didn't want to have to install VS 2010 but am now willing to do so after trying the advice one person posted here:
http://www.richard-banks.org/2009/11/how-to-build-vs2010-solutions-using.html
and some other posts I've found but am still getting errors from the VS Test dlls.
What version of VS 2010 do I need to install to support builds with VS Tests for a TFS 2008 build server?
I was able to get VS 2010 projects to build using TFS 2008 source only by installing Team Foundation Server Build and Team Foundation Server 2010 Build agents. I also had to install Microsoft Windows SDK for Windows Server 2008.
I followed the advice here as well to set TFS 2008 build agent to use .net 4:
http://www.richard-banks.org/2009/11/how-to-build-vs2010-solutions-using.html