PowerServer Project deployment refactoring
The PowerServer project deployment has been refactored, and
settings for the development environment and the production
environment have been greatly simplified and completely separated, so
that developers can easily and quickly get started with PowerServer
now:
-
Setting up a web server (such as IIS) for hosting the client
app is no longer a must in the local development environment; as
client app can be directly hosted in the internal Kestrel
server.-
Developers need not to set up a web server (such as IIS)
to host the static files during the development stage. When
you select to deploy and run within IDE, the static files
(including the client app, launcher, and runtime) will be
automatically deployed and hosted (alongside the PowerServer
Web APIs) in the internal Kestrel web server. -
Kestrel is automatically included and enabled, so
developers can start developing and testing without needing to
install and configure any server on the local machine. In one
word, developers now can deploy and run a PowerServer project
in only a few clicks (view this
video). -
To use the other servers such as IIS, developers will
need to set up the server (for example, set up a local IIS
server, set up a remote IIS
server).
-
-
The client app can be generated as part of the PowerServer
Web APIs when deployed to the local Kestrel; or they can be
generated as separate parts so they can be easily moved around and
deployed to different sites or servers.-
Developers can create a package that includes not only
the cloud app launcher, runtime files, & application
files, but also the compiled Web APIs (targeting Windows
32-bit or 64-bit, or Linux 64-bit); and can directly deploy
them to the same (or different) site. -
Developers can also publish the compiled Web APIs to the
docker container using Dockerfile (view
more).
-
-
PowerServer Web APIs can be directly published to the server
from the PowerBuilder IDE.-
Developers can directly publish the PowerServer Web APIs
from the IDE to the local Kestrel, local/remote IIS, or local
folder; and can directly compile and run the Web APIs from the
IDE when deployed to local Kestrel or IIS. -
When deployed to the local/remote IIS, ASP.NET
Core hosting bundle must be installed on the server, in
order for the IIS process manager to automatically launch the
PowerServer Web APIs. -
When deployed to the local Kestrel or local/remote IIS,
the site URL will be used as the Web API URL by
default. -
Developers need to launch SnapDevelop or Visual Studio
to publish the PowerServer Web APIs only when they want to
publish to Azure App Service etc.
-