D
DenDuze
Guest
Hi Laura, That's new! I thought the assemblies.xml was always needed... I already tried with the -assemblies startup-parameter but still the same. Yes the dependancies are there and also the dll exists (with the same version and culture) in the root of the application. The problem with fuslogvw.exe is that it's a part of the SDK and we do not want to install that SDK on production environments. That's why I use the registry solution to output the binding information to disk. But like I said I do not really understand how that works because there are 2 directories where the output goes to, a prowc.exe and a OE application directory. In the prowc.exe directory I get an error-file for all bindings (Telerik, Infragistics, ...) - what's normal because it only searches the $DLC\bin and the dll's are not there In the OE application I ony get a few error-files (but these are not important for me, they are about some Telerik-theme's, the dll's that I use in my screens are correct. So why do i get the "could not load file or assemblies ..." when starting the screen. Isn't there some setting to give a search-path to find the dll's for the bindings? I found something like a prowc.exe.config on the web but I can't make that to work (or must that file have another name). regards Didier
Continue reading...
Continue reading...