>But I bet you're not loading the DevExpress dll dynamically so that shouldn't be an issue. You just need to make sure that when your recompile your app and the devexpress dll you update both.

No, you're right, we aren't loading it dynamically.

>FWIW, there should be no need to recompile the DLL - I don't think you'd gain anything from that. Unless you've modified the code, just use the original .NET 1.x dlls. It won't run any different just because it's 1.x code that's recompiled in 3.5. Remember .NET is JIT compiled so all code always compiles and runs on the latest runtime the app is running under anyway and 1.x compiled assemblies will work just fine and still take advantage of all the improvements and fixes of the latest framework.

You know what? I am really an idiot sometimes! <g> For some stupid reason, I was thinking that since it was a 1.x DLL that the 1.x Framework was needed. Jeez, I don't know what the heck I was thinking (or not thinking might be a better description <g>). I feel very stupid right about now. =0( Thanks for that! <g>

Actually, I *do* know why I didn't think it through and just went down that path. I'm testing this on a plain vanilla virtual PC that didn't initially have any .NET stuff on it. So, first I loaded the 3.5 Framework (to verify what our customers would have installed if they started out with nothing). Then I installed VS2008, then a test application (which uses the DevExpress DLL). Then I realized that I didn't have the DevExpress DLL on that virtual PC, so I went to install it. Dumb move, because it obviously gave me grief because I didn't have the 1.x Framework installed. I just figured that I might as well recompile it, but now I see that that was a stupid idea.

I'll try leaving it as is and play with it some more. Thanks Rick!

~~Bonnie