We are moving to BTS 2010 and I would like to know if I can simply redeploy our 2009 apps onto 2010?
I have tried finding this information out on the web and I have found anecdotal evidence of people saying the 2009 apps run on 2010 but nothing from Microsoft on the issue.
Microsoft released this document here about the in-place upgrade path, but this does not mention apps at all. Additionally we are not looking to do an in-place upgrade but to build a completely new environment for 2010 and then switch it over.
Has anyone tried this?
Yes, certainly it works - we've installed MSI's generated off our BizTalk 2009 / VS 2008 environments directly onto BTS 2010, including retention of the 2009 binding files. The BTS 2010 environment was a multi-server clean install.
In fact, many of our incumbent, stable BTS 2009 apps are still running on our BTS 2010 prod servers - we haven't bothered to rebuild them.
According to Jeremie Devillard it is possible to deploy 2009 apps on a new 2010 environment (see comments section).
Many thanks Jeremie.
Related
Is there any hidden tool from MS we can use for BizTalk application migration prior to load solution into VS2015 ? I need some information about what are characteristic we may need to change specially BizTalk.btproj solution to load all project file etc., wonder to know easy approach migrating BizTalk application solution if any.
As various blogs posts and MSDN threads you needed to have an intermediate Development BizTalk environment (BizTalk 2010) and then upgrading it to the later version like BizTalk 2013/R2 and up.
You can download the developer edition here and install the SDK so you can open it in Visual Studio.
The only other way to migrate is to create new BizTalk Projects in Visual Studio 2015 / BizTalk 2016 environment, and then copying the artefacts such as Schemas, maps and re-creating any Orchestrations.
In either case you will have to do extensive retesting as there are certain changes such as the XSLT compiled transform that may cause you issues
No need for a hidden tool. Visual Studio is the tool.
When you open a downlevel Solution, Visual Studio will attempt to update any project and provide a report of what was automatically updated and what could not be updated, requiring manual intervention.
You can do this on a copy of you Solution to get a preview of any work necessary for the real upgrade.
Coming from BizTalk Server 2006, you will need an intermediate version to eventually target BizTalk Server 2016. You can download BizTalk Server 2010 from MSDN. All you need to install is the SDK. You don't need to setup/configure full BizTalk Server.
Is BizTalk Server 2013 compatible with the Dynamics AX 2009 AIF BizTalk Adapter?
I've searched but can't find any information to say either way.
I found that BizTalk Server 2010 is compatible with AX2009 SP1 RU7: http://blogs.msdn.com/b/emeadaxsupport/archive/2011/09/29/microsoft-biztalk-server-2010-passes-compatibility-testing-with-microsoft-dynamics-ax-2009-sp1.aspx
(Apologies if this is not the correct site for this question, as it's not directly programming related; however I couldn't find another Stack Exchange site which looked more suitable).
I did not find anything newer announced at Partner Source.
This does not imply that BizTalk 2013 is not compatible, only that it is not a tested scenario, and that if you choose to use, it is your own risk.
Unfortunately, the BizTalk+AX story has alwasy been a little mysterious in terms of what exactly is 'supported' and not.
However, the Adapter interface is unchanged from BizTalk Server 2010 to BizTalk Server 2013 so the '2010' Adapter should run without issue in 2013.
Worst case, PSS will only offer 'best effort' support, though it's highly unlikely you'd ever need it.
I've got Visual Studio 2010 Ultimate edition on my machine, and I've been working with ASP.NET a lot (my job). I recently installed Visual Studio 2012, to test it out. Noticed that I had a few issues with VS 2010 after installing VS 2012, with Unit Testing etc.
Anyway, I have been debugging & testing the ASP.NET pages in 2012 to test it out. Went back to debug and test on VS 2010 and that's when it all went wrong! Sometimes it debugs, most of the time it doesn't, and when it does the layout and formatting is horribly wrong.
Tried the ASP.NET project on my employee's machines, and it runs fine and the layout is all correct. (They use VS 2010)
I've uninstalled VS 2012 completely and tried debugging and testing in VS 2010 and I still have the same issue! I also have re-installed VS 2010 twice, and yet it still does not work.
Anybody know whats wrong with it? Or what else I can do to ensure VS 2010 and 2012 stuff has been properly uninstalled before I try another re-install?
Thanks for your time..
Create a Virtual Machine and install VS2010. In a clean install, it should work fine. Otherwise, VS2012 could have made some changes to your code. I wouldn't discard it -¿config files? ¿a new version of the bundled web server? ¿a new functionality?-.
Once you have discarded code changes due to the new version, give a try to your preferred uninstall software and delete VS2012...
We recently upgraded our biztalk server 2006R2 to SP1. The problem is that we're having some small issues now, for example the administration console crashes when I browse for a folder if I want to make a file send/receive port.
Any idea what might cause this problem?
I'm having no problems when I browse for a folder with our normal explorer and then copy paste its address into the biztalk folder browser.
Make sure you update towards the latest CU for your service pack.
For BizTalk 2006 R2 with SP1, this is CU4.
See http://support.microsoft.com/kb/2682056 for more information on CU4 for BizTalk 2006 SP1.
If this still does not help, there is a temporary workaround to export/import bindings of existing receive locations/send ports with a FILE adapter. This allows you to still create the ports/locations you need and unblocks the situation.
In any case, if the problem persists, you might want to check with Microsoft about the issue.
That is in case your license includes the extended support option which lasts until 12 July 2016.
If you don't have extended support, the support ended on July 11th 2011 I'm afraid...
Not exactly a programming question in the technical sense, but it's impacting my development nonetheless and I'm hoping someone here might have encountered and solved this issue before.
I recently got adventurous and installed Office 2010 beta onto my PC here, and I've noticed that Visual Studio has begun to hang whenever I'm editing an ASPX file, sometimes right away, sometimes after a few minutes. In my research I came across this post:
http://abdullin.com/journal/2009/5/12/visual-studio-2008-locks-or-freezes-in-aspx.html
It seems to imply that there's a dependency between Office and Visual Studio. Is anyone here successfully running Office 2010 64-bit with Visual Studio 2008? I'm on Windows 7 64-bit, also.
Josh
Edit: I have confirmed that the Setup.exe file referenced in that post is in fact being run by VS. It is indeed a vestige of the Office 2007 suite. I moved the directory it was in, and (of course) the process isn't spawned, but VS hangs on "loading cache" on this project. I think I'm getting closer though.
Hope this helps:
http://blog.hinshelwood.com/archive/2009/07/19/office-2010-gotcha-2-visual-studio-2008-locks.aspx
Unfortunately, doing a repair install of the Office-based Visual Web Developer component wouldn't work — the setup application kept crashing. I ended up solving this problem by doing a complete reinstall of Visual Studio. For some reason, doing a simple repair wasn't possible — the VS setup kept crashing, too.
I did a manual remove using an uninstall tool designed for the VS2008 RC. It did a complete install of all VS components, after which point I reinstalled VS2008, which in turn reinstalled the Office-based visual web developer component.
It was a long and painful process, but it worked. It didn't seem to be a direct incompatibility between Office 2010 and VS2008, as we have another PC here with the same combination that wasn't having the problems. I believe it had to do with the fact that my PC originally had Office 2007, which I had to uninstall before installing Office 2010. The other PC that wasn't having this problem never had Office 2007. I can only assume that the uninstall process for Office 2007 either removed those Visual Web Developer components or removed dependencies that were originally put in there by the VS2008 setup program.
office 2010 runs on wpf and its major portion is build on dotnet framework. And there is always connectivity between office and vs coz vs can make office apps also. If you use office 2010 as your default for aspx page editor and vs is also opened with the same project. it will sometimes hang due to lack of resources and also vs 2008 was made for 32bit os, so if ur running it on 64bit os with office 2010 64bit it can sometimes cause problem of resouce management. Already wpf uses hell lot of resouces and then 32bit vs 2008' connection to it will use more resouces.
So what i suggest is try to use 32bit 7, 32bit office 2010 ans vs 2008.
Regards,
Apurva