J
Jeffrey Z. Wolf
Guest
Hello Didier I am looking into a similar issue. I found that fuslogvw.exe does not give a full picture of where .dll are being looked for. I found that the Windows Sysinternals tool entitled procmon gave a much fuller view of what files are being touched when in the process of binding assembiles. There is a lot more stuff to wade through, but at least with procmon the information is available. Regards.
Continue reading...
Continue reading...