Home > Articles > Web Services > XML

Like this article? We recommend

The Test UI Application

The test application is a Windows application that is created in its own project and references the AuthenticationPlugin.Common namespace. Aside from that namespace, it also needs to refer to the System.Reflection namespace to access the Assembly and Activator classes which are covered later.

The application is shown in Listing 1.4. The code that we are most interested in is the btnLogin_Click method, which is executed when the btnLogin button is clicked on the form. For convenience, an OpenFileDialog control grabs a file name by using the btnBrowse button.

For this sample to work, the filename should be the name of the assembly created in the test plug-in, AuthenticationPlugin.Plugins.MyTest.dll. The full path name is required, so if the assembly is located in your C:\Temp directory, the file name should be C:\Temp\AuthenticationPlugin.Plugins.MyTest.dll.

When the btnLogin button is clicked, the string in the txtFileName textbox is used as a filename, loading the assembly (using Assembly.LoadFile) after a simple check to ensure the file exists. A very simple method, called ShowError, opens a message box with an error message if the file does not exist.

Listing 1.4.

using System;
using System.Diagnostics;
using System.Drawing;
using System.Collections;
using System.ComponentModel;
using System.Windows.Forms;
using System.Data;
using System.IO;
 
using System.Reflection;
 
using AuthenticationPlugin.Common;
 
namespace AuthenticationPlugin.UI.UITester
{
       /// <summary>
       /// Summary description for Form1.
       /// </summary>
       public class Form1 : System.Windows.Forms.Form
       {
        private System.Windows.Forms.OpenFileDialog ofdPluginFile;
        private System.Windows.Forms.TextBox txtFileName;
        private System.Windows.Forms.TextBox txtUserName;
        private System.Windows.Forms.TextBox txtPassword;
        private System.Windows.Forms.Button btnLogin;
        private System.Windows.Forms.Button btnBrowse;
              /// <summary>
              /// Required designer variable.
              /// </summary>
              private System.ComponentModel.Container
                components = null;
 
              public Form1()
              {
                     //
                     // Required for Windows Form Designer support
                     //
                     InitializeComponent();
 
                     //
                     // TODO: Add any constructor code
                     // after 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 Windows Form 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.btnLogin = new System.Windows.Forms.Button();
            this.ofdPluginFile = 
              new  System.Windows.Forms.OpenFileDialog();
            this.btnBrowse = new System.Windows.Forms.Button();
            this.txtFileName = new System.Windows.Forms.TextBox();
            this.txtUserName = new System.Windows.Forms.TextBox();
            this.txtPassword = new System.Windows.Forms.TextBox();
            this.SuspendLayout();
            //
             // btnLogin
            //
            this.btnLogin.Location =
              new System.Drawing.Point(368, 88);
            this.btnLogin.Name = "btnLogin";
            this.btnLogin.TabIndex = 0;
            this.btnLogin.Text = "Login";
            this.btnLogin.Click +=
              new System.EventHandler(this.btnLogin_Click);
            //
             // btnBrowse
            //
             this.btnBrowse.Location =
               new System.Drawing.Point(368, 56);
            this.btnBrowse.Name = "btnBrowse";
            this.btnBrowse.TabIndex = 2;
            this.btnBrowse.Text = "Browse...";
            this.btnBrowse.Click +=
               new System.EventHandler(this.btnBrowse_Click);
            //
             // txtFileName
            //
             this.txtFileName.Location =
               new System.Drawing.Point(8, 56);
            this.txtFileName.Name = "txtFileName";
            this.txtFileName.Size = new System.Drawing.Size(352, 20);
            this.txtFileName.TabIndex = 3;
            this.txtFileName.Text = "";
            //
             // txtUserName
            //
             this.txtUserName.Location =
               new System.Drawing.Point(8, 8);
            this.txtUserName.Name = "txtUserName";
            this.txtUserName.TabIndex = 4;
            this.txtUserName.Text = "Enter Username";
            //
             // txtPassword
            //
             this.txtPassword.Location =
               new System.Drawing.Point(8, 32);
            this.txtPassword.Name = "txtPassword";
            this.txtPassword.TabIndex = 5;
            this.txtPassword.Text = "Enter Password";
            //
             // Form1
            //
             this.AutoScaleBaseSize = new System.Drawing.Size(5, 13);
            this.ClientSize = new System.Drawing.Size(448, 117);
            this.Controls.Add(this.txtPassword);
            this.Controls.Add(this.txtUserName);
            this.Controls.Add(this.txtFileName);
            this.Controls.Add(this.btnBrowse);
            this.Controls.Add(this.btnLogin);
            this.Name = "Form1";
            this.Text = "Form1";
            this.ResumeLayout(false);
 
        }
              #endregion
 
              /// <summary>
              /// The main entry point for the application.
              /// </summary>

              [STAThread]
              static void Main()
               {
                     Application.Run(new Form1());
              }
 
        private void btnLogin_Click(object sender, System.EventArgs e)
        {
            try
            {
                /* Initialize some standard objects
                 * that will be used to load up the
                 * assembly.
                 */
                Assembly assembly = null;
                string typeName = string.Empty;
                Type pluginType = null;
 
                if ( File.Exists( txtFileName.Text ) )
                {
                    assembly = Assembly.LoadFile( txtFileName.Text );
                }
                else
                {
                    /* The file that was specified does not exist.
                     * Checking here is much faster than waiting
                     * until the catch block to handle an
                     * FileDoesNotExist exception.  Substitute the
                     * error message code with logging code, etc.
                     */

                    ShowError( string.Format
   ( "The specified file '{0}' does not exist.", txtFileName.Text ) );
                }
 
                if ( null != assembly )
                {
                    /* Now the Assembly has been loaded.
                     *  We should look to see if we
                     * can find a type that uses the
                     * AuthenticationPlugin attribute
                     */

                    foreach ( Type type in assembly.GetTypes() )
                    {
                       if ( type.IsAbstract ) continue;
                       if
                       (type.IsDefined
                         ( typeof( AuthenticationPlugin.Common.AuthenticationPluginAttribute ),
                          true ) )
                        {
                         /* We've found the authentication plugin
                          * type, so we'll stop here.  This is the
                          * first instance.  More code could be 
                          * added to throw an exception if more
                          * than one is defined, etc.
                          */
                            pluginType = type;
                            break;
                        }
                    }
                    /* Make sure before trying to act
                     * on the object that a type
                     * was actually found.
                     */
                    if ( null != pluginType )
                    {
                        bool isValidUser =
                     ((IAuthenticationPlugin)Activator.CreateInstance (pluginType)).
                      IsLoginValid(txtUserName.Text, txtPassword.Text);
                       
                      /* Display the result */
                      MessageBox.Show( ( isValidUser ) ?
                        "Login successful!" : "Login failed!" );
                    }
                    else
                    {
                        throw new ApplicationException
                      ("The plugin does not contain the correct type.");
                    }
                }
 
            }
            catch ( System.InvalidCastException )
            {
             /* The object didn't implement the
              * IAuthenticationPlugin interface, and could
              * not be cast correctly */
                ShowError
                ("The authentication object does not implement the correct interface.");
            }
            catch ( System.BadImageFormatException )
            {
                /* The Assembly is invalid
                 * It is not a valid .NET Assembly file. */
                ShowError( string.Format
                   ( "Invalid plugin file '{0}'", txtFileName.Text));
             }
            catch ( System.Exception ex )
            {
                ShowError( ex.ToString() );
            }
        }
 
        private void ShowError( string message )
        {
            MessageBox.Show( message,
                 "Error",
                 MessageBoxButtons.OK,
                 MessageBoxIcon.Error );
        }
 
        private void btnBrowse_Click(object sender, System.EventArgs e)
        {
            ofdPluginFile.ShowDialog();
             if ( ofdPluginFile.FileName != string.Empty )
             {
                txtFileName.Text = ofdPluginFile.FileName;
            }
        }
       }
}

The code that does the file loading is:

assembly = Assembly.LoadFile( txtFileName.Text );

This method throws System.BadImageFormatException if the file specified by txtFileName.Text is not a valid .NET assembly. This exception is caught later at the end of the method.

Once the assembly is loaded, the next step is to get the types from the assembly, and iterate through them to see if the AuthenticationPluginAttribute is defined. The method stops at the first instance that it finds, and sets the pluginType variable to the type it found:

if ( type.IsDefined( typeof( AuthenticationPlugin.Common.AuthenticationPluginAttribute ), true ) )

{

  /* We've found the authentication plugin type, so we'll
   * stop here.  This is the first instance.  More code
   * could be added to throw an exception if more than one
   * is defined, etc.
  */

  pluginType = type;
  break;

}

As mentioned in the comments, this could be expanded to do stricter checking, such as making sure that no more than one type exists in the assembly that has the AuthenticationPluginAttribute defined. For brevity, the application is satisfied by the first type that it finds.

Now that the application has the type, it can use the Activator class to create an instance of the type and cast it to IAuthenticationPlugin. Casting the instance to IAuthenticationPlugin allows the code to execute IsLoginValid since it knows that if the class implemented the interface, IsLoginValid must be present. In the sample application, the values in the txtUserName and txtPassword textboxes are passed as the username and password, respectively.

Once the application has the result, it prints out a message to a message box to show if the login was successful:

MessageBox.Show( ( isValidUser ) ? "Login successful!" : "Login failed!" );

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020