Parser Error Message Could not load type in Global asax

Question

I m working on an MVC3 project and receive the following error      Parser Error Message  Could not load type  GodsCreationTaxidermy MvcApplication     Source Error       Line 1   lt    Application Codebehind  Global asax cs  Inherits  GodsCreationTaxidermy Core MvcApplication  Language  C     gt    The error I get is cannot load GodsCreationTaxidermy Core MvcApplication but in this screen shot the Core part isn t displaying in the error     Does anyone have any ideas or a solution to this error

User · Answer

I closed and reopened visual studio and it worked

User · Answer

My app was built in an older version of VS  and didn t have a bin folder  I had upgraded it to a newer version  and had a nightmare getting it to deploy  I finally tracked this error down to the Project   Properties   Application  The Target Framework was set to 2 0  changing it on the server to match in the IIS Manager App Pool solved the issue for me

User · Answer

BUILD -  CONFIGURATION MANAGER and -- ahem -- check the box next to my project to ensure it actually gets built   That and going to the project folder in windows explorer  pressing options and unchecking the  Read only  checkbox helped

User · Answer

I also got the same error   check the name of the Application you developed properly ie  the namespace and the assembly name alloted and also try physically changing the name of the folder created for the application  all of this should be same as the name in the above namespace present in the file global asax

User · Answer

I spent literally a day trying to resolve this   The only thing that worked was deleting the  sln file  creating a new one  and adding the projects back in one by one               - Programming -

User · Answer

You can also check your site s properties in IIS   In IIS  right-click the site and choose Properties   Make sure the Physical Path setting is pointing to the correct path for your application not some other application   That fixed this error for me

User · Answer

I have same problem when I have 2 instance of Visual Studio running same project  So I closed both Visual Studio and opened only one instance and It works fine now

User · Answer

I experienced this recently in a Web Application  The problem was a nuget package brought in a dependency to   Microsoft Net Compiler and Microsoft Code Dom   They support multilevel compiler versions     That converted my application to an ASP NET website instead of the Web Application    took me forever to resolve this - 2 5 days     I deleted those from the Nuget Manager  deleted the files in obj and bin directories - closed studio - and then reopened and rebuilt the project   That fixed it but  WHAT A PAIN THAT WAS     I hope I save some others time on this one

User · Answer

Delete the  vs directory from the solution root  Clean  Rebuild   This issue drives me bonkers once in awhile and I inevitably end up here paging through answers  I suspect there are multiple causes that can produce this exception  this once works for me

User · Answer

Two ways to get this    The configuration manager shows the dll builds as a mix of  64  and  any cpu  builds   Putting them all to the same build fixes it  When switching between branches  the IIS express path is sometimes not updated  Right click  IIS Express  in the task bar   Show all applications and verifty that the path is to the correct branch

User · Answer

The problem for me is that I didn t include global asax cs in my project  And because I was copying files from a  net 4 5 to a 4 0 I didn t comment out lines that are not needed in 4 0  Because it was not included visual studio compiled it anyway without issues  But when I included it  it highlighted the lines that cause problems   using System  using System Collections Generic  using System Linq  using System Web    using System Web Http  using System Web Mvc    using System Web Optimization  using System Web Routing   namespace YourNameSpace       public class WebApiApplication   System Web HttpApplication               protected void Application Start                         AreaRegistration RegisterAllAreas                  GlobalConfiguration Configure WebApiConfig Register               FilterConfig RegisterGlobalFilters GlobalFilters Filters               RouteConfig RegisterRoutes RouteTable Routes                 BundleConfig RegisterBundles BundleTable Bundles

User · Answer

I solved the problem this way   Just fix the namespace in Global asax

User · Answer

I found that changing the Namespace on the project  without refactoring that across the whole solution was my problem    Check your project Properties and see what your namespace is  ensure that lines up  across the board

User · Answer

I tried absolutely everything here and nothing worked   My project was in VS 2013   I have since upgraded to VS 2015 and have been creating all of my new applications in 2015 but loading  compiling  building etc all of my old apps that were built in 2013 in that version   I ended up just loading the solution in 2015 and it resolved it for me

User · Answer

I encountered this error message and eventually discovered that the error message was misleading  In my case there appears to have been a routing issue in IIS which caused the global asax from another site on the web server to be read thus generating the error   In IIS  my site was bound to http  80 webservices local and contained an application called MyAPI  I received the dreaded message when calling the MyAPI application using the web server s ip address   In order to successfully call my application I had to add a host file entry for webservices local on all of the machines that called the MyAPI application  Then all of my requests had to be prefixed with http   webservices local MyAPI  in order to route correctly

User · Answer

Try modifying your global asax file  simple add a space somewhere  and re-run   this will force the built in webserver to refresh and recompile the global asax file   Also do a clean and rebuild - should fix the problem

User · Answer

I also got the same error   check the IIS Configuration of your Virtual Directory and be sure that Properties - ASP NET - ASP NET Version is the same of Project Properties - Application - Target Framework   That fixed this error for me

User · Answer

Yes  I read all the answers   However  if you are me and have been pulling out all of what s left of your hair  then try checking the  bin folder   Like most proj files might have several configurations grouped under the XML element PropertyGroup  then I changed the OutputPath value from  bin Debug  to remove the   Debug  part and Rebuild   This placed the files in the  bin folder allowing the  Express IIS to find and load the build   I am left wondering what is the correct way to manage these different builds so that a local debug deploy is able to find and load the target environment

User · Answer

cant load errors  with your project firstly Fix your errors and after rebuild project its working

User · Answer

I faced the problem in VS 2017 out of no where  took my whole day going through 100 of solutions any of these didnt work  I then took my whole solution and started it on different machine having VS 2017 installation    IT FINALLY WORKED  Than reinstalled VS 2017 on the original one and it started running on that too  I strongly recommend you try your solution on a different machine before wasting much time to debug it  bcz it is a BUG in VS 2017 as it seemed for me  have reported same to VS TEAM  Hope this helps any one in grief  Cheers

User · Answer

This happens sometimes if you change namespace information  project or class level  after the global asax is generated    Right click on the Global asax file and select  Open With  and then select  XML  Text  Editor with Encoding   other editors may work as well  but this is what I use     Then edit the  Inherits  section in the XML directive       lt    Application Codebehind  Global asax cs  Inherits  GodsCreationTaxidermy MvcApplication  Language  C          so that it matches the actual full name of your Application class  And that s it    Another option is to copy off all your code from Global asax cs and then delete and create another Global asax file  and then copy the code back into Global asax cs

User · Answer

For my case  the web assembly was part of GAC    so after build  it need to installed in GAC and it worked

User · Answer

I had to go to BUILD -  CONFIGURATION MANAGER and -- ahem -- check the box next to my project to ensure it actually gets built

User · Answer

I had this issue today  and it took me a while to find the cause   Basically  my main VS2015 project was including a sub-project which had been built using a higher version of  Net Framework   Bizarrely  when you have this problem  VS2015 will happily report that the solution has built okay  but when you try and run the website  it just gives you that misleading error  suggesting that your Global asax cs file is wrong   So  if you see this error  and Cleaning Rebuilding doesn t help  open your Project s References tree  and check for exclamation marks     Also  check your Output window for messages like this   The primary reference  C  Projects Business Objects 4 bin Release BusinessObjects dll   could not be resolved because it was built against  the   NETFramework Version v4 5  framework   This is a higher version than the currently targeted framework   NETFramework Version v4 0     The solution  of course  is to right-click on your main project  select the top tab   Application   and change the Target Framework version to a higher version which matches your sub-project   It s annoying that Visual Studio 2015 will let you fully build and run Solutions which quietly contain this problem   It s asking for trouble

User · Answer

Check that the project output path  project properties   Build  is set to bin and not bin Release or bin Debug  For some reason IIS  VS development Server or Local IIS  always accesses the libraries from the bin directory  and won t look up for subdirectories

User · Answer

I was working on an older  folder based  ASP NET web project  which I loathe  - and found this to be my fix   Create an App Code folder  if you didn t have one already   Move the Global asax vb file into the App Code folder  The markup in Global asax can leave out any namespaces  at least  for this style of project  afaik     lt    Application Codebehind  Global asax vb  Inherits  MyApp  Language  VB    gt       where  MyApp  is the name of the class being defined in Global asax vb

User · Answer

Empty the bin folder  Build all the dependent class libraries and refer them in the main project  and build the complete solution    Source

User · Answer

I spent multiple days on this issue  I finally got it resolved with the following combination of suggestions from this post     Change platform target to Any CPU  I did not have this configuration currently  so I had to go to the Configuration Manager and add it  I was specifically compiling for x64  This alone did not resolve the error   Change the output path to bin  instead of bin x64 Debug  I had tried this several times already before I changed the platform target  It never made a difference other than getting an error that it failed to load the assembly because of an invalid format     To be clear  I had to do both of these before it started working  I had tried them individually multiple times but it never fixed it until I did both    If I change either one of these settings back to the original  I get the same error again  despite having run Clean Solution  and manually deleting everything in the bin directory

User · Answer

Your local web server is running different code than what you re actually working on  Ensure you have stopped debugging  stop your local web server  clean and rebuild as Peter suggested  double-check your global asax and global asax cs  and try again   If this doesn t work and you are using local IIS  try removing the site in IIS Manager and recreating it manually

User · Answer

I have to report that I tried at least 4 suggestions from this post  None of them worked  Yet I am happy to report that I recovered by retrieving from back up  Only had to update my last code changes from log file  Took less then 10 minutes  Spent 3 times that reading this post and trying other suggestions  Sorry   It was a very weird error  Good luck to anyone else encountering this gremlin

User · Answer

This can also happen if you accidentally forget to set your VS solution to  Multiple Startup Projects  if you are running a Web and WebApi from the same solution   You can check this by right-clicking on Solution in the Solution Explorer and select  Properties    Then look for  Startup Projects

User · Answer

This issue I was solved by giving right permission of the folder as well as check from IIS   I was given permission to everyone  as I am testing in my local environment  But in publish mode I think we give only permission to ASP Net user

User · Answer

I too faced the same problem  Despite of following every Answer it didnt work  Then I changed the  Inherits namespace class  to  Inherits fully qualified assemble name  i e  Inherits namespace class assemblyname  Version   Culture   PublicKeyToken   Hope it helps

User · Answer

The solution for me wasn t any of the above  I had to delete  and not recreate  Global asax and Global asax cs  These files existed in the folder  even though they weren t referenced in the project  Apparently the build still saw them  Since I use OWIN with Startup cs  the Global asax file was obsolete and there was no issue with deleting it

User · Answer

I just encountered this on an MVC5 application and nothing was working for me  This happened right after I had tried to do an SVN revert to an older version of the project   I had to delete global asax cs and then added a new one by right clicking Project -  Add New Item -  Global asax and THAT finally fixed it   Just thought it might help someone

[asp.net] "Parser Error Message: Could not load type" in Global.asax

Examples related to asp.net

Examples related to asp.net-mvc-3