SharePoint 2010 Email Event Handler produces error "Could not load file or assembly...", list stops working -

In the pursuit of many blogs, I have the code below. However, once I am registered with the event handler and the SharePoint Timer Service I resume, when I send an email to the list, it no longer displays emails and I get an error below.

I tried:

Restarting the IIS, SharePoint Timer Service.

Did my IT department give "user" account rights to my assembly? In GAC (other blog's suggestion)

Code :

  Public category EventReceiver1: SPEmailEventReceiver {/// & lt; Summary & gt; An email message has been received in the /// list. /// & lt; / Summary & gt; Public override receives zero email (SPList oList, SPEmailMessage, string strReceiverData) {SPListItem oListItem = oList.Items.Add (); Oliver's item ["Facsimber"] = Omease. Header ["subject"]; // OliveItem ["Body"] = Omease Html bd; Oliver's item ["messbie"] = Omease Header ["subject"]; OListItem.Update (); }}   
  error :  
 
 file or assembly could not be loaded 'TestEventReceiverProject, version = 1.0.0.0, culture = Neutral, public key token = Defend 4 CAB 73 dcb 'or its dependency can not specify a system file.   
 In addition, when I restarted the SP service, I get an error "OSTMER has an unwanted exception (system security cryptography .crographical expression ') .exe [ 6760] "  
 
 
 Open project property window. Select the Create tab, change it to any CPU. Save your changes Compile and deploy your project  
 If the conference is in GAC and the Visual Studio Debugger can not see debugging symbols (aka: * .pdb). Unless you run through the trouble of setting up a symbol store, where all your PDBs are running, you have to keep debugging symbols in the same place as assembly. This trick is finding the folder in which your DLL is in GAC.  
 C: \ Windows assembly folder is not a real folder, it's a virtual folder. To get into the real folder, do the following:  
 Start »Run% systemroot% \ assembly \ gac [ENTER] Now it will open the GAC folder, as long as you find a folder that looks like this Hold around (you may need to raise a folder and dive into the MSIL folder): [assembly file name-DLL extension] [Format # # in the assembly version. #.] # [__ [assembly public key token].  
 When you search for that folder, open it and you will see your assembly and you will confirm that your assembly has been properly deployed. You can easily drag the montage and drop it  
 Display and IISreset, reset the timer job and it's good to check again