Question

3
Replies
144
Views
MichaelD4660 Member since 2017 13 posts
Fifth Third Bank Bank
Posted: 2 years ago
Last activity: 2 years 9 months ago
Closed
Solved

How to access .NET class library Properties.Settings from Pega/OpenSpan automation

Can a Pega/OpenSpan automation project use config file settings to change values used in "Properties.Settings" of a .NET DLL? I am trying to something similar to how one might set up a Visual Studio solution.

For example, a VS solution might have two projects: a web application project and a class library project. The class library project might have property settings, which enable type-bound references like "MyProjectNamespace.Properties.Settings.Default.MySettingName". Using Properties.Settings would generate entries in the app.config file something like that seen below. Then in the consuming web application project, the configSections and applicationSettings configuration elements would be copied/pasted into the web.config file.

<configuration> 
 <configSections> 
  <sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, ... etc..." > 
   <section name="MyProjectNamespace.Properties.Settings" type="System.Configuration.ClientSettingsSection, ... etc..." /> 
  </sectionGroup> 
 </configSections> 
 <applicationSettings> 
  <MyProjectNamespace.Properties.Settings> 
   <setting name="MySettingName" serializeAs="String"> 
    <value>SomeValue</value> 
   </setting> 
   <!-- ... etc ... -->
  </MyProjectNamespace.Properties.Settings> 
 </applicationSettings> 
</configuration>

My question is if something like this is possible with Pega/OpenSpan? For example, can the RuntimeConfig.xml file be modified in a way, so that the DLL from the .NET class library project would pick up new settings (e.g. - prod vs. dev)? Or, can an existing app.config be deployed in a way to be picked up by the solution? If so, please describe the correct procedure, or a viable work-around. I have tried adding the above settings (leads to error), and I have tried putting an app.config file in various locations including the location of the Pega project, and the Pega installation folder.

Thanks!

***Edited by Moderator Marissa to update SR Details***

Low-Code App Development SR Exists
Moderation Team has archived post
Share this page LinkedIn