Sorry that is not enough information to track down any problem but as I recall, DevExpress components are problematic. If you have any error information at all please pass it on and I'll see if I can reproduce the problem.
I think some DevExpress components are late-bound and aren't recognized as a dependency. So
1. Is SmartAssembly embedding the DevExpress stuff (you can see this in the project settings)
2. If not, you can try this advice from DevExpress: http://devexpress.com/Support/Center/Is ... id=B195350
Maybe there is an exception happening, but DevExpress is catching it? If you're handy with a debugger you can see if that's the case - you can attach Visual Studio debugger to the process and tell it to catch all exceptions (CTRL-ALT-E, select managed exceptions).
edit: maybe attaching Red Gate's support debugger would be more useful as if it's a binding exception you should get good info on the inner exception.
I suspect it's because the XtraPrinting assembly is signed with a strong-naming key and the code is not including the key in the binding. For instance, the debug dump indicates you're trying to load "DevExpress.XtraPrinting.v10.2, Version=10.2.4.0" with no public key token.
I'll see if I can reproduce this and get back to you.
giorgizek
Posts: 9
Comments
Sorry that is not enough information to track down any problem but as I recall, DevExpress components are problematic. If you have any error information at all please pass it on and I'll see if I can reproduce the problem.
DevExpress.XtraGrid.v10.2.dll
in version SmartAssembly version is 6.2 215 is working but in version SmartAssembly 6.5. 1037 is not working
I have disabled everything in project settings. just dependencies embedding. but nothing happens.
1. Is SmartAssembly embedding the DevExpress stuff (you can see this in the project settings)
2. If not, you can try this advice from DevExpress: http://devexpress.com/Support/Center/Is ... id=B195350
all dll's are included for export
edit: maybe attaching Red Gate's support debugger would be more useful as if it's a binding exception you should get good info on the inner exception.
here is ar debug result
I'll see if I can reproduce this and get back to you.