I have the source code of BizTalk 2010 applications that needs to be re-written for BizTalk 2013.
What i am doing so far is that I am creating new BizTalk 2013 project, adding the existing files from 2010 project (schemas maps orchestrations pipelines etc.) and compiling and building the project (fixing the errors on the way).
Is this approach correct?
Will this produce BizTalk 2013 applications?
I am able to deploy new apps to BizTalk 2013 by the way. I have tried looking for migration techniques over the internet but no luck.
No, just make a backup of the entire solution (file copy, branch, label), then open it in Visual Studio 2012 for BizTalk Server 2013 or Visual Studio 2013 for BizTalk Server 2013 R2.
That is the correct approach and I would actually recommend abandon your previous attempt.
You do not need to create new projects for 2013 from scratch. If you open Visual Studio Solution file in VS 2013 then it will automatically upgrade to BizTalk 2013 version files. Most of the time this migration will work without any errors.
Related
my job is to maintain a word-addin, created many years ago, developed by many young programmers like me ;) the addin works fine and there are only a few and easy changes to do from time to time, so my task is to bring the development environment up to date.
The addin was handed over to me as an visual basic project with Visual Studio 2005(in XP-Mode) and a .dot-file
Now I wanted to use Visual Studio 2015, but when I tried to migrate the project there is an error which says the word-version i'm using is not supported by VS2015 and tells me to use Office 2010 minimum. The problem is, my company just uses Office(Word) 2007.
So how can i get VS2015 to migrate the project properly and to use word 2007? Or do I have to use 2010? I read 2010-addins can be used in 2007 and via versa, so this should not be the problem.
Following software is installed:
Microsoft .NET Framework 2.0 SP2
Microsoft .NET Framework 3.0 SP2
Microsoft .NET Framework 3.5 SP1
Microsoft .NET Framework 4/4.5/4.5.1/4.5.2/4.6
Microsoft Office Developer Tools for Visual Studio 2015
Microsoft Visual Studio 2010 Tools for Office Runtime
Visual Studio 2005 Tools for Office Second Edition Runtime
Visual Studio 2015 Community
Microsoft Office Word 2007
thanks for help :) and please excuse my bad english
The short answer is that you cannot use Visual Studio 2015 to open the original project, but you can recreate the code in a new project that will still work with Office 2007:
https://msdn.microsoft.com/en-us/library/bb772080.aspx
I have an existing Visual Studio 2005 project for which I get a conversion wizard prompt when opening in the freshly installed Visual Studio 2010. What are the implications of carrying out this conversion? Converting to anything more recent than 2010 is not an option.
The conversion process is usually pretty seamless, it will take your 2005 project and upgrade it to a 2010 project.
It should not be an issue unless you have projects with 3rd party components which, for whatever reason, do not like the newer version of Visual Studio. The only one I've ever had a problem with is Crystal Reports and that was going from a .NET 1.1 project in VS2003 to .NET 4.0 in VS2010. (But hey, one does not simply do things with Crystal Reports)
The conversion wizard will also back up your old project if you tell it to, although I would hope it's in source control of some kind anyway.
Of course, people who only have VS2005 on their machine will no longer be able to open your upgraded 2010 project, you are effectively committing to VS2010. It can always later be upgraded to VS201x at a later date if this becomes an option.
Currently our BSP is built using Visual Studio 2005. I would like to update this to use VS 2010 at the very least, preferably 2012. I have not been able to find anything that will allow me to do this. I tried to upgrade the project to VS 2008, but it failed to load the project. I was wondering if anybody had some ideas or could at least point me in the right direction.
Visual Studio 2008 does support the Platformbuilder Plugin and creating Applications for Win CE, however the import wizard is not perfect, you may need to change some settings by hand.
Visual Studio 2010 does not support creating BSPs or applications for Win CE.
Visual Studio 2012 will support creating of BSPs and applications for Windows Embedded Compact 2013.
It also includes a new faster version of the .Net Compact Framework.
http://blogs.msdn.com/b/windows-embedded/archive/2012/11/14/windows-embedded-compact-v-next-uncovered.aspx
http://channel9.msdn.com/Events/Visual-Studio/Visual-Studio-2012-Virtual-Launch/Visual-Studio-2012-support-for-Windows-Embedded-Compact
I have already using Visual Studio 2010 for my project. Now I have to work with a Visual Basic 2006 legacy application. Can I install VB 2006 Enterprise Edition on my system?
Will this affect Visual Studio 2010?
Yes. Visual Studio 2010 and Visual Studio 6 will happily install side-by-side.
You can run multiple versions of Visual Studio on the same machine. I currently have VS2003, VS2005, VS2008 and VS2010 installed and am using all of them.
Where you may get into problems is with something like hooking up the older ones to TFS. This can be done, as I have VS2003 and VS2008 connected to TFS2010, but my VS2005 won't work as it whinges about the provider for some reason.
Another area to watch out for is IIS. As you have already installed VS2010, IIS may be defaulting to .Net 4.0 so if you start deploying .Net 2.0 apps then the websites may not work without some adjustment of things like app pools.
But if you are just using them independently of each other then you should be fine. If you're really paranoid, consider creating a VM and installing the old VS on it.
EDIT
I see from your edited post that you were talking about VB6. This also can be installed alongside any of the later versions of Visual Studio.
I have an existing Visual Studio 2010 web project that I want to migrate to Visual Studio 2012. Can anybody suggest steps on how to do it?
Just open your solution with VS2012, it's compatible: http://msdn.microsoft.com/en-us/library/vstudio/hh266747.aspx