Hi *,
to support showing process name in monitoring table we have a special
handling for ASP.NET applications, where in most cases the process
name is useless, but the application path could be helpful (though it
may be wrong under special conditions). But this adds dependency to
System.Web, which isn't included in Client framework profile. All the
rest is there (incl. EF).
So what's in my head.
1. Remove dependency to System.Web and simply use the process name
(IIS worker process, mod_mono under Apache process etc.)
2. Use reflection to conditionally load assembly and get the information.
3. Don't do anything. :)
Votes? :)
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.cincura.net/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
