Showing posts with label ssns. Show all posts
Showing posts with label ssns. Show all posts

Tuesday, March 6, 2012

.NET config file for Custom event Provider?

Hello all,

I'm creating a custom event provider for SSNS 2005 using .NET. My custom provider needs to get configuration info from a file (e.g. app.config).

Is there any (acceptable?) way of making my config file data available to my provider if I'd like my provider to be hosted by SSNS? Perhaps I could hack it by making or adding to an app.config for some part of SSNS (the instance service executable perhaps?) but that doesn't sound appetizing.

The only thing I can think of is to force my event provider to run as a standalone EXE (which means a standard app.config should work).

Help?

OK, I found that it is quite simple to use a specific config file for my DLL (especially using EntLib).

However, issues with codebases and so forth for dependent assemblies has turned me to switch. I'm now using a standalone event provider because it avoids all these issues around config files, dependencies, and so forth (everyhing is simply in one standard bin folder).

.NET config file for Custom event Provider?

Hello all,

I'm creating a custom event provider for SSNS 2005 using .NET. My custom provider needs to get configuration info from a file (e.g. app.config).

Is there any (acceptable?) way of making my config file data available to my provider if I'd like my provider to be hosted by SSNS? Perhaps I could hack it by making or adding to an app.config for some part of SSNS (the instance service executable perhaps?) but that doesn't sound appetizing.

The only thing I can think of is to force my event provider to run as a standalone EXE (which means a standard app.config should work).

Help?

OK, I found that it is quite simple to use a specific config file for my DLL (especially using EntLib).

However, issues with codebases and so forth for dependent assemblies has turned me to switch. I'm now using a standalone event provider because it avoids all these issues around config files, dependencies, and so forth (everyhing is simply in one standard bin folder).