L
Laura Stern
Guest
It seems strange that this should work during development but not at run-time. When you run from r-code, we don't even need the assemblies.xml file because the assembly-qualified name of all referenced classes are in the r-code. Though you still can use the .xml file. So you could try using -assemblies to point at an assemblies.xml in your app directory. I don't remember if the current-working-directory is one of the places .NET looks for assemblies or if it is only where we look for them, when loading via the .xml file. Fact that may be of interest: When the AVM loads assemblies from the assemblies.xml file, if there is one that fails to load, we do NOT give an error message. We just keep going and try to load the rest. So if you are seeing an error it is because the .NET run-time cannot find the assembly you are referencing in the r-code based on its assembly-qualified name - or that one of its dependencies is missing. But since it works when the .dlls are in $DLC/bin, that means the dependencies are there. You could also try to use the tool fuslogvw.exe. I've never used it myself, but I believe it will help you determine where .NET is looking for assemblies, so you will know why it is not finding them.
Continue reading...
Continue reading...