Sorry if this is a stupid question...but it has had me stumped and I am wondering now if there is a way to do this...

I am working with a team of developers that will be working on several different ASP.Net applications that will be sharing several common assemblies. We have been doing research on the best (and simplest) way to handle how these are accessed from these applications.

After doing some research we really liked the possibiities of using <runtime><assemblybinding><probing> to load these, but we do not want to have to worry with a way of maintaing one of these for each application, so we thought the machine.config would be a more logical choice.

I have been doing some quick testing and I have had success using the app.config, but not the machine.config. Can this be done?

Thanks for any input.