Going to try to move this over 50 year old, exclusively client-server, PB Developer into the cloud/multi-tier/web-service world, basically because my customers are forcing me to ;-)
OK, so my development environment consists of a Macbook Air running Windows 10 under VMWare Fusion. I have a daytime job where I prefer the Apple ecosystem. The PB work is a side gig, so don't really need an impressive development rig.
The first customer I want to move (eventually) to their app running via the "cloud" (hope I'm using that term correctly) is currently running running a native PB app (using PFC) with SQL Server database connected via ODBC. I know old school right? They have been very happy with the situation so far - no need for a large tech-savvy IT org to support this app (will get to this point later).
So the plan I have in my mind is:
- Move to PowerClient - to address the need to deploy the PBDs/EXE.
- Move to PowerServer - they have a future need to create some APIs to allow other applications to access the business logic.
So for PowerClient step:
- Can I install Microsoft IIS Express on my VMWare Mac to test the PowerClient deployment (local server).
- How do I instruct a "non-server" savvy (like me actually) IT department to create a Web Server?
I've read a lot of PowerClient docs, white papers and tutorials, but maybe I've missed some?
Thanks in advance for all your help.
I guess I just want to take it in small steps. I need to bring the customer's IT dept. along with me.
I'll go simple with PowerClient then move to PowerServer when their IT Dept (and myself) are comfortable.
Again, right now, my development environment is a Macbook Air running Window 10 in a VM. Perfect for my client-server development needs on the road (i.e, plane journeys, hotels) but not good for full-blown multi-tier development.
Am I the only one still developing PB apps this way? ;-)
I understand your point of doing a stepped approach... first taking care of the the client app deployment with PowerClient and then moving the app from client/server to cloud with PowerServer. The only thing I would suggest is for the Web server use something compatible with .NET Core so then when you move from PowerClient to PowerServer you don't have to change Web servers.
With that said, it would probably be simplest just to go with IIS (not IIS Express). Only if you expect thousands of users or it is important to run on a Linux server, then I would look into fancier configs using a reverse proxy along with Kestrel. Here is info from Microsoft about this: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel/when-to-use-a-reverse-proxy?view=aspnetcore-5.0