I have a TFS 2012 configuration, and the majority of my assets are based on C# in VS 2012 solutions. Right now I'm trying to integrate some other assets into my build, however these are BizTalk 2010 assets in a VS 2010 solution.
BizTalk 2010 is explicitly not supported in VS 2012; instead, VS 2012 supports only BizTalk 2013. My challenge is to build this VS 2010 solution in our TFS 2012 environment, alongside our VS2012 solution, since upgrading to BizTalk 2013 is not an option.
I tried naively to add the VS 2010 solution to the build definition, but the compiler barfs on my btproj files, probably because it's treating them as if they were BizTalk 2013.
CSC (0): Source file 'C:\Builds\1005\TeamProject\Sources\Source\BizTalk\BizTalk.Schemas\SchemaHelper.xsd.cs' could not be found
For what it's worth, there is no evidence that my BizTalk 2010 project references this .xsd.cs file; I'm assuming this is a sidecar file introduced with BizTalk 2013 that the compiler is expecting to find. My build server has both VS 2010 and VS 2012 installed.
Has this kind of thing come up before? I can't seem to find much information. My first instinct is to attempt to add a copy of the "Items to Build" field in the build process parameters that will be used explicitly for VS2010 solutions, and then attempt to define an activity to invoke the 2010 compiler against those projects.
Does this sound sane? Is there a better way?
While you can likely get it to work in the 2012 build server by forcing the build through 2010 I believe that the only result of trying to build Biztalk 2010 is pain and suffering. Notwithstanding 2012.
You can create a purely 2010 build server and environment and plug that into TFS 2012: http://nakedalm.com/visual-studio-2012-update-2-supports-2010-build-servers/
Related
We have an old MVC2 project stranded in Visual Studio 2010 and assigned to TFS 2010.
Is it possible to copy this project into VSTS and access VSTS in Visual Studio 2010?
Because it is an old project there is no need to migrate the version history.
What are my options?
Yes, you can access Visual Studio Team Services (VSTS) from Visual Studio 2010, however, you will need two software updates:
Visual Studio 2010 Service Pack 1 (KB2736182)
TFS 2012 compatibility update for Visual Studio 2010 (KB2662296)
Having said that, upgrading to Visual Studio 2017 is preferable if you can do that.
To bring your data into VSTS, the easiest way to do that is to use the TFS to VSTS migration tool, which providers an easy, high-fidelity migration into the cloud. However, since you don't require history, you can also perform a manual migration, where you simply check your assets into TFS directly.
I am trying to install Azure biztalk services SDK and then create project in vs 2013 and vs 2015 community edition but dont see any project template.
I can only see project template for biztalk in vs 2012 professional.
This is also made clear in the link here
http://www.microsoft.com/en-au/download/details.aspx?id=39087
However the issue is the microsoft doesnt sell vs 2012 online anymore and i dont see any reason in buying a 3 year old IDE when i have VS 2015.
So just checking if any one here has been able to create biztalk projects for azure in vs 2015.
Its the same problem with Microsoft at Every Release of BizTalk and Visual Studio, the same question you asked get asked everytime
I have VS 2010 but BizTalk project 2006R2 template doesn't appear
I have VS 2012 but BizTalk project 2010 template doesn't appear
...
You have to know that unfortunately BizTalk Project templates are not backward compatible this means that unless you have VS 2012 you won't be able to get those templates.
BUT There is maybe a chance that you can copy those templates from an existing install and get it on your computer (i'll try this at home and edit my answer later) i think it can work if it does i'll post this stuff
I have created a c/cpp project in microsoft visual studio 2012, but the test machine has microsoft visual studio 2008, is there a way to tell visual studio 2012 to be compatible with 2008
No. You need to maintain two different project and solution files, one for each version. The only compatibility is between Vs2010 and VS2012 (and promised for future versions too).
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.
What are the steps I should do and everything I should consider when upgrading from Visual Studio 2005 Team Suite to Visual Studio 2010 Ultimate?
Where can things go wrong?
Consider the fact I'm using TFS 2008 and have Continuous Integration and Nightly Builds on build machines.
One big Problem are Unittests with autocreated Private Accessors. If you want to touch them you have to rewrite them...
The issue is described Here