on 10-04-2016 10:51 AM
Hi,
We are trying to figure out how to do an automated deploy with PowerBuider.Net 12.6.
Since we usually use PowerBuilder Classic for development we first need to migrate the sources to Powerbuilder.Net.
Usually we have a Workspace just for the migration, where we first delete the Target and afterwards add it again.
Afterwards we open another workspace which contains additional Powerbuilder.Net libraries + the source we just migrated and deploy this Solution.
So the steps are:
We already managed to get step 4 working using this link:
http://nntp-archive.sybase.com/nntp-archive/action/article/%3C4e60108f.44c4.1681692777@sybase.com%3E
Is there any documentation for the commands specified in this link?
Maybe we would be able to migrate or add a target using those commands.
Thanks in advance
Thank for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Christian;
Before you get too far into migration, I would like to point out that there is currently no future road map for PB.net. When SAP turned over PB to Appeon on July 5, 2016, the wheels were already set in motion to only move PB Classic & InfoMaker forward and not PB.net.
This means that when SAP drops PB support on January 31, 2018, this will also be the EOL for PB.net. That being said, my question to you now is why would you want to migrate away from PB Classic as PB.net at this time is basically a known "dead end"?
PB Roadmap: Appeon - PowerBuilder Tools, Native Mobile & Web Development platform, Professional Service
Regards ... Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Christian,
We are well aware that one of the main reasons people are using PB.NET in production today is for the .NET WCF Services. We have plans to incorporate this into the native PB IDE in Appeon's PB 2019 release. But unfortunately, temporarily for PB 2017 and PB 2018 you will need to use PB.NET 12.6 to maintain your .NET WCF Services and use PB 2017 and PB 2018 to maintain your desktop apps.
Regards,
Armeen Mazda
CEO, Appeon
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.