You are correct that it would create a .dll. You dont have to register it, however, unless you want to, but is usually unnecessary unless you plan on a lot of apps accessing it. Just compile the dll and add a reference to it in your projects. It will be copied and distributed with your app (in the app folder) without registering. If you do decide to register your dll, just create a strong name with the sn.exe utility (from the .NET SDK command prompt) to create a key pair, then assign that to your [assembly:KeyName] attribute of the .dll (assemblyInfo.cs/vb). Then recompile and use gacutil.exe (.NET SDK command prompt) to register the dll in the GAC. Only do this if it is absolutely necessary, however. HTH. Aaron Dilliard

I agree that there are no major changes that would break an app, but even subtle changes in the way the control is drawn could have an effect on 1.1 code. IE, if a WM_PRINT message is sent with the ERASEBACKGROUND flag or something like that, that could be the culprit. I know Microsoft changed the control some in 2.0, and Ill bet that is what is going on. I will just have to rework the code. Thanks for the input. Aaron

Thanks. All I had to go by was the struct definition on MSDN's website, and it was for c++. I wasnt sure exactly what the exact conversions were for each of the elements, but I knew it had to be something like that. It definately makes sense though. I appreciate your help! Thanks!