Due to limitations with an existing application, we need to call CSLA-based components from a "classic" ASP page. The component on our web server will communicate with an app server using the remote data portal. We struggled to determine the name and location of the config file that contains the URL of data portal site. It appears that the CSLA components are running under the w3wp.exe process, so it requires a config file named w3wp.exe.config on C:\Windows\System32\Inetsrv. Putting the config file in this location works.
This would be ok, except we are restricted from access to the C:\ drive on our deployment servers. The actual assemblies reside on D:\. We would prefer to store the config file with the assemblies. We have not been able to figure out the name or location to accomplish this. We tried putting a config file named <assemblyname>.dll.config in the same directory as the assembly, but it was not recognized.
Is there any way to do this without modifying the CSLA code? We have ASP.NET clients accessing the components as well.
Copyright (c) Marimer LLC