1. Sim Joo Pee
  2. PowerServer
  3. Friday, 2 June 2023 04:07 AM UTC

Hi All,

 

  I had below questions while working on Power Server 2022 project. Please advice. Thanks.

 

1. Target framework .net 6 or .net 3  <- which one to choose? what criteria determina which to choose?

2. Power Server vs power client?  <--- what is the different?

3. signing tool? how it work?  <---Example video to show?

4. What is signing? What is the benefit?

5. SSL? <---Exmaple video to show?

6. How to debug in power server? Run from IDE no issue, but if PS, it has issue?

7. changes like update of application ini, add text files, change db name, need recompile and redeploy?

8. if changes/updates only happened in application and/or db settings, need redeploy all including c# solution/api?

9. Databae Basic and Advance tab, after configure db at basic. Also need set the same again at advance tab?

10. During Uploading package/unpackage , what will happened if user is still working on the current application while the uploading/unpacking is happening together?

11.  Can multiple cloud application connect to one .net server ? **Only one copy of webapi

Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Friday, 2 June 2023 14:41 PM UTC
  2. PowerServer
  3. # 1

Hi Sim,

I can help you with some questions:

1. Choose .NET 6, .NET Core 3.1 is out of support

2. PowerClient helps with distributing updates of your PB applications. PowerServer also does this BUT ALSO extracts the application's data access operations and creates a .NET Web API. This removes the database dependency of the client applications (you no longer have to distribute the DB access credentials to each one of your clients) and moves it on to a server

3. ---

4. Signing an cation helps to verify that it's been created by the real developer and it has not been altered or provided by some other malicious actor

5. What about SSL? How to implement it in your server? See here

6. Debugging in PS is as easy as debugging in PB, see here

7. Correct

8. If you make changes only to layout or business logic, you don't need to redeploy the Web API. If you add a new DataWindow or ESQL, you MUST redeploy PowerServer AND the Web API. If you make changes to the DB settings, you most likely also need to redeploy the Web APIs

9. If the Basic tab is enough for you to do what you need, there's no need to also go to the advanced tab.

10. It's always advised that updates are only pushed when no one is using the application. On this point, restarting the Web APIs will immediately erase all currently active PS sessions, and all clients will see a "Session does not exist" error

11. You should not do this. You should use 1 Web API per application

Hope this helps clear out some of your doubts

Regards,
Francisco

Comment
  1. Miguel Leeuwe
  2. Friday, 2 June 2023 15:12 PM UTC
Hi Francisco,

You mixed 3. and 5.

Why SSL, isn't TLS the recommended way nowadays?

just curious as I haven't got a clue myself :)
  1. Helpful
  1. Francisco Martinez @Appeon
  2. Friday, 2 June 2023 15:22 PM UTC
True! I'll fix this right away.



TLS is definitely the way to go. SSL has been long obsolete, but it has become a synonymous to TLS
  1. Helpful 1
  1. Miguel Leeuwe
  2. Friday, 2 June 2023 15:27 PM UTC
Great! Indeed people mix SSL with TLS, but the link you provided on how to configure IIS, seems to be specificly TLS. Sorry if I'm wrong about that.

Appreciate all of your great work!
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.