If you're unsure where your .NET application is looking for it's config file, check the AppDomainSetup.ConfigurationFile property.
This property gets or sets the location and configuration filename for the running app domain.
AppDomain.CurrentDomain.SetupInformation.ConfigurationFile
Pretty unnecessary when you're writing sensible software, but when your dealing with "Notes + Javascript + ActiveX + .NET" lunacy you might just need this.
Thanks to Stonie for the pre-written post ;)
Rather than just commenting out code that is deprecated, use the Obsolete Attribute to decorate types and members of types that are obsolete and will cause compiler warnings to be generated if that type or member is used. It’s a great way to make developers aware that a particular object is changing, and the functionality they are using will be disappearing in a future release.
IISAPP.VBS
You can use the command-line script iisapp.vbs, which is stored in systemroot\system32, to view any worker processes that are currently running.
