Hello, Thanks for the reply. I have tried to configure it but it doesn't work. I keep getting the same error

and some options don't appear in the configuration. I am using Windows Server 2022



Thanks

Luis

It's difficult to troubleshoot your config mistake in forum without accessing and inspecting your environment. I would suggest just save the package to your local disk using the "Folder" option and use FTP client like Filezilla to transfer it to the server. That is our recommended approach.

No, that's not what I'm saying. In the screenshot you attached to your post go look there is radio button right next to IIS selected that is called "Folder". Select that and it will save the compiled app to your developer machine. Then you use FTP client like Filezilla to FTP it over to IIS web server. Once it is on IIS Web server the latest version of PowerClient installs and updates app to your users same as before. So that part is not changing. All that is changing is how you get the app from your dev machine to the IIS server.

Ok, thanks for the answer.

I don't understand. I see the structure of the application on the web server and it doesn't look like anything that the compiler generates. I see a directory that identifies the compiler version and subdirectories with several files. That's not what I get when compiling the system.



I don't understand why Appeon makes the work more complicated instead of easier.



Thanks

Luis

If you'd like we can schedule a meeting with one of our staff and go over this deployment process. The new process does require some manual step but much more flexible. I know you were happy with the FTP deployment but we got quite a few complaints, and so we first made the change with the PowerServer project type and after period of releasing it to the market for real-world usage we now synchronized the change into PowerClient so both PowerServer and PowerClient project types deploy same way.