After applying MR 1506, if you want to create a new launcher profile, you will need to make sure the runtime version is 1506. The runtime version cannot be an earlier build such as MR 1311 or GA 1288 when you create a new launcher in MR 1506.
In MR 1506, changes have been made to the template of the PowerServer C# solution. You will either have to
-
Generate a brand new PowerServer C# solution (in Build 1506)
This new solution will be generated from the latest template. However, if you have made your own changes to the solution before, those changes will not be retained in the new solution, you will need to manually incorporate those changes to the new solution.
-
Or, use the existing PowerServer C# solution
This can keep your own changes in the solution. The solution will still use the old template even if you use Build & Deploy PowerServer Project in PowerBuilder IDE at Build 1506 to build the solution again. You will have to manually change the following areas in the solution (to be in sync with the new template):
-
Upgrade PowerServer.Core and PowerServer.Api to the latest compatible version. See this table for a list of NuGet packages compatible with the application deployed via PowerServer Toolkit from different builds.
-
Add the following script to the PowerServer C# solution > ServerAPIs project > Startup.cs:
app.UsePowerServerPathBase();
-
Add the following script to the PowerServer C# solution > ServerAPIs project > Server.json:
"PathBase": "/vpath1",
"PathBase" is used to specify the sub-folder of the Web site where PowerServer Web APIs is deployed, for example, "/vpath1", or null if no sub-folder is used.
Note
Step 2 & 3 is required only if have specified a sub-folder of the Web site in the Web API URL (for example, http://172.168.168.88:5000/vpath1) when using a Kestrel server, otherwise, the PowerServer C# solution created in GA 1288 or Build 1311 will not work with Build 1506.
-
