L
Laura Stern
Guest
Sorry, I've never used fuslogvw, so I don't know what it shows you. And I don't understand what you said before about the "bindings" and logs other than you got some error-files that you think aren't relevant. You could try procmon instead - which can show you all the files the process is trying to access. What we need to see is where Microsoft is looking for the dlls. You could look at the case that works and then the case that doesn't work and see what's different. Without help from some kind of tool, I don't think I can help you. And maybe someone more experienced with fuslogvw can pipe in here.
Continue reading...
Continue reading...