Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved .NET Desktop Runtime 6.0 Distribution

  1. How-to
0
Votes
Undo
  1. David Sowray
    David Sowray
  2. PowerBuilder
  3. Friday, 19 January 2024 15:15 PM UTC

We're looking to upgrade our application from PB2022 (R1) to PB2022R3. The application is 32-bit pcode distributed using PowerClient.


We have the problem that:

  • The app's db connection uses ADO.NET, which for PB2022R3 appears to have a prerequisite of .NET Desktop Runtime 6.0
  • The client computers do not have .NET Desktop Runtime 6.0 installed
  • Client users do not have admin rights (and many don't have easy access to someone with admin rights) so installing .NET Desktop Runtime 6.0 is not an option

Is it possible to distribute the .NET Desktop Runtime 6.0 components with the application so it will work for non-admin users? And if so, how?

Many thanks,
David

Is there any specific issue with "OAuthClient" and...
what is the difference between runtime.msi file an...
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 19 January 2024 16:05 PM UTC
  2. PowerBuilder
  3. # 1

Hi David;

  What DBMS, its version & build are you using?
Regards ... Chris

Comment
Load more comments
Steen Jakobsen
  1. Steen Jakobsen
  2. Monday, 22 January 2024 06:48 AM UTC
Chris, SQLCA.DBMS = "MSO" what is that ?
  1. Helpful
David Sowray
  1. David Sowray
  2. Monday, 22 January 2024 07:10 AM UTC
Maybe we're unusual, but ADO.Net seems to be the one driver that everyone has pre-installed and it never gives us any trouble.



MSOLEDBSQL gives the error message "Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) is not installed".
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 22 January 2024 13:59 PM UTC
Yes, the "MSOLEDBSQL" which is the latest Microsoft SS DB client going forward but you'll have to pre-install it. That should be easily using a Windows Policy rollout.
  1. Helpful
There are no comments made yet.
Steen Jakobsen
Steen Jakobsen Accepted Answer Pending Moderation
  1. Monday, 22 January 2024 06:50 AM UTC
  2. PowerBuilder
  3. # 2

You can include a package that dynamically downloads and installs .net 6.0 desk runtime.

 

https://www.codeproject.com/Articles/20868/Inno-Setup-Dependency-Installer

Comment
David Sowray
  1. David Sowray
  2. Monday, 22 January 2024 06:53 AM UTC
Doesn't that require admin rights?
  1. Helpful
Steen Jakobsen
  1. Steen Jakobsen
  2. Monday, 22 January 2024 06:55 AM UTC
I dont know. But I think so.
  1. Helpful
David Sowray
  1. David Sowray
  2. Monday, 22 January 2024 07:21 AM UTC
Unfortunately our client users do not have admin rights (and many don't have easy access to someone with admin rights), so that's not an option. But thank you anyway for the suggestion, Steen.
  1. Helpful
There are no comments made yet.
Mora Wang @Appeon
Mora Wang @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 23 January 2024 07:20 AM UTC
  2. PowerBuilder
  3. # 3

Hi David;

Distributing the.NET 6.0 desk runtime components on the client side instead of installing them to enable software support to ADO.NET may cause unpredictable problems. We suggest you install and configure the clients that need to use .NET 6.0 desk runtime through the IT management department first and then run the PowerClient application.

In addition, I recommend consulting with Microsoft to see if they have a better solution for this issue.

Best Regards,

Mora

Comment
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.