Migrate from powerbuilder 12.5.2 version to powerbuilder 2017,espcially using EAServer in the application? - powerbuilder

What will be required to migrate from powerbuilder 12.5.2 to powerbuilder 2017,espcially using EAServer in the application?SQL Server using as the database server.

You would need to get rid of EAServer in order to upgrade to PowerBuilder 2017. The reason is that SAP is no longer continuing development of this product, and so this feature has been discontinued from PowerBuilder 2017 and newer versions. This discontinued feature and other migration considerations are documented in the migration guide: https://www.appeon.com/support/documents/appeon_online_help/pb2017r3/migrating_pb_apps/
There are two options to move forward, which both relate to getting rid of EAServer:
Move all your EAServer NVOs back to the client-side (as PowerScript NVOs).
Port your EAServer NVOs to C# Web APIs (running on IIS or Kestrel) with PowerBuilder 2019's new C# migration solution: https://www.appeon.com/support/documents/appeon_online_help/pb2019/whats_new/ch02s01.html


Use Team Foundation Server in Delphi 7?

I'm a .NET developer and use VS2008/TFS2008. Recently, another developer has left our company and now I have to maintain his code. He was a Delphi developer (Delphi 7 mostly, but also Delphi 2007) and he didn't use any source control.
Is there a way to put his code in Team Foundation Server? Integration in the Delphi IDE is a big plus.
To get IDE integration with TFS in Delphi 7, you need can use the MSSCCI provider for TFS in conjuction with SourceConnexion which gives MSSCCI support to Delphi. You will need to install the following on your machine if you do not have them already:
Microsoft Team Explorer 2008 (The TFS Client)
The Microsoft MSSCCI provider for TFS 2008
You need to ensure that you have TFS client access licenses for any of the Delphi folks connecting to TFS and get them a license for the SourceConnexion plug-in.
As you already have VS2008 installed on your machine talking to TFS2008 you probably only need to install items 2 and 3.
See Eyal's blog post for more information (a little out of date but stil valid).
We use SourceConnexion (3rd party plugin) with D2007:
(Works nice with SCC api plugin of Plastic SCM, which has better branching support than TFS :-) )
I realize that this is an old thread but during my reserach on how to use TFS2012 with Borland Delphi 2006 the posts here helped me a lot, so I wanted to share my experience.
To use TFS2012 or TFS2010 with Borland Delphi 2006 please follow these steps.
Download and install Microsoft Team Explorer 2010.
Download and install TFS MSSCCI provider TFS2010 (make sure you download the 32-bit version even if on a 64-bit machine!).
Download and install SourceConnexIon.
Open Borland Delphi 2006, click on the Source Control menu item and follow the configuration wizzard.
You must follow this order or SourceConneXion won't detect TFS.

Migrate IIS 6 to IIS 8.5 without using MS Deploy toolkit

I am looking for a way to migrate IIS 6 to IIS 8.5 (server 2003 to server 2012 R2) web pages without using third-party applications or non-native tools like MS Deploy. The reason is so specific: I am a student and I have the challenge to migrate the web pages using only native resources.
I have searched on internet and I just found the MS Web Deploy tool and other alternatives just supported by server 2008 and 2012, like appcmd command.
I found this question on stackoverflow that points this alternatives:
IIS shared configuration (It is not supported by IIS 6/Server 2003)
WebDeploy (It is not a native tool)
XML export/import using Appcmd (Appcmd is not available in server 2003)
So I am asking a new question. Is there any form to export/import web pages between IIS 6 and IIS 8.5?
Thank you in advance!
I'm unclear what you mean by a 'native tool'. MSDeploy is provided by Microsoft and the IIS team suggests using this tool for migrating sites:

Is ProClarity supported on SQL Server 2012?

I'm currently in the process of coming up with our upgrade plan for our migration from SQL Server 2005 to SQL Server 2012, and some of our business units still use ProClarity.
I'm aware that this is essentially a "dead" application; where Microsoft isn't upgrading it anymore, and it's scheduled to be EOL'ed in the future.
After googling and digging around on Microsoft's forums, I still can't come up with a definitive answer as to whether the 2012 upgrade will be incompatible with Proclarity. (Business users are on 6.2; which is one minor revision behind)
Has anybody tried this out and been successful? Would we need to keep this portion of the BI tools on SQL Server 2008?
Upgrade was successful, and the users were able to connect to 2012 Analysis Services using ProClarity

How can we migrate existing web applications from .net 2.0 to 4.0 in installshield project

We have a number of Installshield projects that install and configure IIS applications. We have shipped several versions of the different applications (over 7 versions of 3 applications) and would now like to upgrade to use .net 4.0 instead of 2.0 & 3.5.
After modifying the "Internet Information Services" settings to change the ASP.NET Version on the web sites/application to 4.0.30319 and the .Net Framework version to v4.0 under the application pool, the installer correctly creates an application with the 4.0 version in IIS 6 and below, and in IIS 7 and above it correctly sets the pool to use v4.0, but upgrades do not work for any targets.
The upgrades install OK, but the .Net version of the virtual directory or application pool remain unchanged. Changing it manually works of course, but this would lead to increased support issues.
I have tried changing the upgrade to be a major upgrade, with no success, I am currently working on a custom action to change the .Net version after installation, but I don't have much experience with this feature of Installshield.
Has anyone experienced this issue? Are there any preferred ways of achieving this? (custom actions, or a .Net installer class, WIX is not an option)
Without spending hours to dig into it... one quick solution would be to rename the app pools in your new installer and let a major upgrade create the new and remove the old. After all, if you are changing from .NET 2.0 to 4.0, in a sense you are creating a component that is not backwards compatible and thus should be a new component.

Sharepoint 2010 Foundation with .Net Framework 4.0

I am having a Web Application with build target as .Net Framework 4.0.
I want to interact with the Sharepoint Object Model API's but it gives a framework 4.0 runtime does not supports Sharepoint.dll error.
Is their any tweak such that I can use Sharepoint 2010 with .Net Framework4.0.
Note: I cannnot change the build target of the web app to any other framework as I am using some exclusive features of .net 4.0 in my application.
Sorry you probably will have no luck:
There appears to be some confusion
around whether or not ASP.NET 4 is
supported for both MOSS and SharePoint
2010 - in short, the answer is that it
is not currently supported in either
Whilst it is possible to use ASP.NET
3.5 in MOSS by making some modifications to the SharePoint site
web.config (instructions for doing
that in MOSS here; SP2010 uses 3.5 by
default), this is unfortunately not
the case with version 4.
The reason? ASP.NET 4 uses a new
version of the Common Language Runtime
(CLR). Whilst .NET 2.0, 3.0 and 3.5
all used version 2.0 of the CLR, .NET
4 uses version 4. I'm not entirely
sure what happened to version 3. There
is a decent post on stack overflow
with further details.
from SharePoint 2010 and .NET 4: confused?
Maybe .NET 4.0 Support will be added in a future update (SP1?) who knows...
Unfortunately, .Net 2.0 to 3.5 use a different application pool type from .Net 4.0; Mixing in the same app pool is not going to work.
What features of .Net 4.0 are you using, and perhaps the community can help you with a 3.5 solution?