Since the "security" update on Feb. 28 due to the EOLAS patent dispute,
IE is now crashing when embedding a very simple winform control in a
web page but only if the page has a SELECT drop down list box on it!

Details of the update
http://msdn.microsoft.com/ieupdate/

If the temporary roll back patch that gives 60 days grace is applied,
IE does not crash.

Has anyone else experienced this and found a work around? Even if you
found no other option than to get rid of the drop down lists I would be
interested to hear that. Only a few more days left for me to fix this
Here is the event log error:
Faulting application IEXPLORE.EXE, version 6.0.2900.2180, faulting
module user32.dll, version 5.1.2600.2622, fault address 0x00010129.

Here is some sample code to reproduce the problem (remove the select
tags and it works otherwise IE crashes):
TEST.HTM
----------------
<OBJECT id="testcontrol" name="testcontrol" height="40%" width="40%"
classid="TestControl.dll#TestControl.BasicControl"></OBJECT>
<SELECT id="h">
    <OPTION>1</OPTION>
    <OPTION>2</OPTION>
</SELECT>

BasicControl.cs (in TestControl.dll) - new user control with just one
button
----------------------
using System;
using System.Collections;
using System.ComponentModel;
using System.Drawing;
using System.Data;
using System.Windows.Forms;

namespace TestControl
{
    /// <summary>
    /// Summary description for BasicControl.
    /// </summary>
    public class BasicControl : System.Windows.Forms.UserControl
    {
        private System.Windows.Forms.Button button1;
        /// <summary>
        /// Required designer variable.
        /// </summary>
        private System.ComponentModel.Container components = null;

        public BasicControl()
        {
            // This call is required by the Windows.Forms Form Designer.
            InitializeComponent();

            // TODO: Add any initialization after the InitializeComponent call

        }

        /// <summary>
        /// Clean up any resources being used.
        /// </summary>
        protected override void Dispose( bool disposing )
        {
            if( disposing )
            {
                if(components != null)
                {
                    components.Dispose();
                }
            }
            base.Dispose( disposing );
        }

        #region Component Designer generated code
        /// <summary>
        /// Required method for Designer support - do not modify
        /// the contents of this method with the code editor.
        /// </summary>
        private void InitializeComponent()
        {
            this.button1 = new System.Windows.Forms.Button();
            this.SuspendLayout();
            //
            // button1
            //
            this.button1.Location = new System.Drawing.Point(40, 64);
            this.button1.Name = "button1";
            this.button1.TabIndex = 0;
            this.button1.Text = "button1";
            //
            // BasicControl
            //
            this.Controls.Add(this.button1);
            this.Name = "BasicControl";
            this.ResumeLayout(false);

        }
        #endregion
    }
}

Colin wrote:
Show quoteHide quoteYes, I found this with our user control last month (April 12th). I
reported it as a bug to the product feedback center and have had very
little joy since.

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=edcd7c5a-983d-4a1a-b37c-72a1c0bb71bd

Validate this bug and vote on it and Microsoft may actually do something
about it.

I'm glad I'm not the only one to be affected by this (sorry for you of
course).

Microsoft have really dropped the ball here I believe. There are basic
faults in the interaction between .NET user controls and this update.

Peter Bromley
ADInstruments Ltd

Thanks for the reply, good to know the bug has been raised and I'm not
alone - I've added my "I can validate this" vote using the product
feedback centre link and encourage anyone else experiencing the problem
to do the same.

Thanks again

Plugin System Recommendations
UDP socket with multiple ports
DataGridViewComboBoxes for numeric fields
Bad Design to Throw Exceptions in Constructor?
Byte Array Comparison Not Accurate - MD5CryptoServiceProvider