D
DenDuze
Guest
Hi Laura, Already done that, you need exe and dll. But really this does the same as what I already did with the logging of the bindings. The only difference is that this is a GUI of those logs (from cache) and you can set some properties so the logging gets done on disc (and those settings are the ones that I already used in the registry). In that GUI fuslogvw: I see also the OE application where the ChartView binding is succesfull (because the Appbase = I also see a prowc.exe where the ChartView binding failed (because the Appbase = $DLC\bin) So completly the same as I mentioned before. But what those prowc.exe-entries and thos OE application-entries mean and which are used by my application is unclear to me. I guess the prowc.exe-entries are used because it does not work and if i put the dll under $DLC\bin (what we do not want to do) it works without a problem. Do you know if we can manage another behaviour with the prowc.exe.config of with the prowc.exe.manifest (or better with some other file that is not under $DLC\bin) regards Didier
Continue reading...
Continue reading...