User Controls - Debug vs Release
-
:confused: I've got a solution with two projects. One project is a DLL that provides services. It contains an User Control that provides a UI to some of these services. The DLL is strong named! Strong naming both a debug and a release version seams a little odd to me. The other project is an applet on which I've placed this User Control. The reference from this project to the other is a 'project' reference. I developed everything in debug - everything worked - life was good. Then I built a release version and life has taken a change for the worse. The first symptom is that the control no longer draw in the designer. Usually I can drop another instance from the toolbox and it will draw. However, sometimes I get the following message box; --------------------------- Microsoft Development Environment --------------------------- The user control 'My.Namespace.MyFunky.UserControl' could not be loaded. Ensure that the library containing the control has been built and a project reference has been made to the library containing the control. If you have changed the name of the user control, close and re-open the control's designer to update the toolbox item. --------------------------- OK --------------------------- I've closed everything and rebuilt everything. The project reference is it to a PDB (not DLL) in \obj\... - probably because it is a 'project' reference. However, that file does NOT exist in \obj\..! It exists in \bin\..! I've removed the project reference and re-added it and no change. Local copies of all the DLL and all dependancies exist in the respective \bin directory! **** Another interesting piece of the puzzle. I've modified the control to look different in Debug and Release modes. The control is NOT display in the designer in either debug or release modes. It does display when running in either mode. Interestingly, it is always the debug version - even in release. **** Prior to this new set of symptoms, when I attempted to drop an instance of the User Control onto my test app, I often ran into the following problem. I never resolved it - just traded it for a new symptom. Perhaps they are related. I have a user control that will not instantiate when I drop it on a form at design time, however, it will create fine at runtime. I do not understand the following error messages that appears both as a message box when I drop the user control, and in the Task window both after dropping it and whenever showing the form in the des