Home > Articles > Programming > Windows Programming

Like this article? We recommend

Like this article? We recommend

Repairing the Errors

Let's look at a few of the issues that FxCop found. The sample application uses frmMain for the name of the form. FxCop marked this usage as an error because standard convention is to use Pascal case for class names. In addition, frm isn't a word, so FxCop suggests correcting the spelling of the word. Simply changing the name of the class to FormMain (initial capital letter and recognizable name) clears up this problem. More importantly, this change makes the class name easier to read and understand. However, the code executes much as it did before—nothing has really changed.

The next error concerns Common Language Specification (CLS) compliance. The application doesn't indicate whether it's compliant with CLS. A CLS-compliant application only uses features that are available as part of CLS. For example, if your C# application uses a UInt32 variable, it's not CLS compliant because the UInt32 type is a language-specific feature. The purpose in marking an application as CLS compliant is to indicate that it can run in any environment that completely emulates CLS. Using a UInt32 datatype would mean that you could run the application only on a Windows system that allows access to unsigned integers. Here's how you would indicate that an entire assembly is CLS compliant:

// Define the assembly as CLS compliant.
namespace SimpleApp
  ... Other Code ...

You can mark sections of an application as noncompliant using the same attribute. For example, if the whole application is CLS compliant except for one method that uses a UInt32, you could mark the method like this:

private void btnTest_Click(object sender, System.EventArgs e)
  UInt32 NonCLSVariable; // UInt32 is not CLS compliant.

  // Initialize the variable.
  NonCLSVariable = 3;

  // Display a message.
  MessageBox.Show("The value is: " + NonCLSVariable.ToString());

Marking an assembly might not seem like a very big deal, but consider the changes that are happening with computing as a whole. The application you build today on a 32-bit machine might have to execute on a 64-bit machine tomorrow. Considering CLS issues today means you'll have less work to do to update the application tomorrow.

The next issue is the first security consideration. I don't know of any application authors who mark their assembly's security needs today—and that's a problem. FxCop marks out minimal essential security requirements. The first is to tell the Common Language Runtime (CLR) what resources your application actually needs. In this case, the application only needs to display a message, and should be marked as such. More importantly, the application should contain information about resources that it doesn't need. For example, this application doesn't need to access the hard drive, so you can deny hard drive access. Adding this information prevents a virus from gaining access to those resources even if it infiltrates the application. Here are some typical assembly-level security descriptions:

// Define the security needs for the assembly.

These three assembly-level permissions tell CLR that it shouldn't allow the application to do anything with environmental variables, access the disk drive, or change the registry. If a virus infects this application, it won't be able to do many of the things that viruses commonly do, such as infecting disk files with virus information. The virus can't move data around, or make itself permanent, for that matter. The .NET Framework provides a wealth of permissions that you can use to control your application. Here are some of the common permissions you should consider:

  • EnvironmentPermissionAttribute

  • FileDialogPermissionAttribute

  • FileIOPermissionAttribute

  • IsolatedStoragePermissionAttribute

  • PermissionSetAttribute

  • PrincipalPermissionAttribute

  • PublisherIdentityPermissionAttribute

  • ReflectionPermissionAttribute

  • RegistryPermissionAttribute

  • SecurityPermissionAttribute

  • SiteIdentityPermissionAttribute

  • StrongNameIdentityPermissionAttribute

  • UIPermissionAttribute

  • UrlIdentityPermissionAttribute

  • ZoneIdentityPermissionAttribute

A second security error is that this assembly isn't signed. An assembly with a strong name is harder to tamper with and therefore harder to corrupt. The strong name doesn't protect the assembly from prying eyes—you need a product such as Dotfuscator to modify the code in such a way that others can't really understand what you're doing. To add a strong name to your assembly, use the SN (strong name) utility to create a key pair like this:

sn -k MyKey

It's important to protect this key because someone else could use it to modify your code.

In addition, you should sign all of your code using the same key or designate a specific key for each purpose. Once you generate a key, you add it to your code using a special attribute, like this:

[assembly: AssemblyKeyFile("MyKey")]

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.


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.


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.


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.


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


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


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.


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.


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