My.(se.name).propertyvalue = ss.settings.get(se.name).value.valuexml. My.(se.name).propertyvalue = ss.settings.get(se.name). Ss = Ctype(rc.sectiongroups("applicationSettings").sections(().getname().name + ".my.mysettings"), )ĭim se as ttingelement = ctype(key, ttingelelement) If rc.sectiongroups("applicationSettings") isnot nothing then Rcfm.execonfigfilename = ().location + ".config"ĭim rc as = (rcfm, )ĭim ss as = nothing
#VB NET 2010 CONFIGURATION SYSTEM FAILED TO INITIALIZE CODE#
You may use this code below (vb.net) not c# :-) Dim rcfm as new If you will be able to load correctly the config file you need to implement on your NEW routine a way to load the config file ! Exception Message: Configuration system failed to initialize. In that case it takes the values specified before compiling your assembly. This enables you to link the other config file (not loading). By default the only config file loaded is the config file from the main application. If you call an application or assembly from another application or assembly you need to implement in you called assembly a way to load the config file. When I placed in the System-directory under Host Integration Server I ended up with this error on the eventlog :Ĩ34) A Transaction Integrator HIP Application called a user application which failed and returned the following Error Description:Ĭonfiguration system failed to initializeĪny tips or examples of config-files would be greatly appreciated :)
Is there some special trick to make this work? Should the config-file be placed in a special directory Through the HIS it's being controlled by HIPService.exe and then it should read parameters from, right? But we can't seem to make it work. We've made a small Windows-applikation to test the method and it works like it should, reading parameters from. When we build the dll we get a config-file on the standard format.
NET dll and takes some parameters from a config-file. The method we invoke is implemented in a. We have a Host Initiated Process being called from mainframe.
0 kommentar(er)
