Asp net ошибка синтаксического анализатора

Соответствие пространств имен в Global.asax.cs и Global.asax проверьте. Должно быть GameStore.MvcApplication.

28 янв. 2023, в 16:38

2500 руб./за проект

28 янв. 2023, в 15:53

3000 руб./за проект

28 янв. 2023, в 15:40

5000 руб./за проект

I’ve finished simple asp.net web application project, compiled it, and try to test on local IIS. I’ve create virtual directory, map it with physical directory, then put all necessary files there, including bin folder with all .dll’s
In the project settings, build section, output path is bin
So when i try to browse my app i got:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Parser Error 
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. 

Parser Error Message: Could not load type 'AmeriaTestTask.Default'.

Source Error: 


Line 1:  <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="AmeriaTestTask.Default" %>
Line 2:  
Line 3:  <%@ Register assembly="AjaxControlToolkit" namespace="AjaxControlToolkit" tagprefix="ajaxToolkit" %>


Source File: /virtual/default.aspx    Line: 1 

Have read similar problem posts and solution was to set output path to bin, but it is defalut for my project.

asked Feb 10, 2013 at 17:36

answered Jun 16, 2016 at 6:39

Sometimes it happens if you either:

1. Clean solution/build or,
2. Rebuild solution/build.

If it ‘suddenly’ happens after such, and your code has build-time errors then try fixing those errors first.

What happens is that as your solution is built, DLL files are created and stored in the projects bin folder. If there is an error in your code during build-time, the DLL files aren’t created properly which brings up an error.

A ‘quick fix’ would be to fix all your errors or comment them out (if they wont affect other web pages.) then rebuild project/solution

If this doesn’t work then try changing:
CodeBehind=»blahblahblah.aspx.cs»

to:
CodeFile=»blahblahblah.aspx.cs»

Note: Change «blahblahblah» to the pages real name.

answered Sep 14, 2017 at 15:00

I have solved it this way.

Go to your project file let’s say project/name/bin and delete everything within the bin folder. (this will then give you another error which you can solve this way)

then in your visual studio right click project’s References folder, to open NuGet Package Manager.

Go to browse and install «DotNetCompilerPlatform».

answered Sep 19, 2018 at 9:15

Faced the same error when I had a programming error in one of the ASHX files: it was created by copying another file, and inherited its class name in the code behind statement. There was no error when all ASPX and ASHX files ran in IIS Express locally, but once deployed to the server they stopped working (all of them).

Once I found that one ASHX page and fixed the class name to reflect its own class name, all ASPX and ASHX files started working fine in IIS.

answered Oct 5, 2016 at 16:17

Very old question here, but I ran into the same error and none of the provided answers solved the issue.

My issue occurred because I manually changed the namespace and assembly names of the project after initial creation. Took me a little bit to notice that the namespace in the Inherits attribute didn’t match the updated namespace.

Updating that namespace in the Global.asax markup to match the apps namespace fixed the error for me.

answered Oct 16, 2019 at 20:05

IIS 7 or IIS 8 or 8.5 version — if you are migrating from 2003 to 2012/2008 make sure web service are in application type instead virtual directory

In my case, There were new code branch and old code branch was deployed locally in IIS. So it was pointing to old branch code that was not available. So i had deployed my code to IIS with new branch and it is working now.

In my case I missed the compile tag in the .csproj file

<Compile Include="Global.asax.cs">
  <DependentUpon>Global.asax</DependentUpon>
  <CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Compile>

answered Apr 30, 2018 at 10:24

Interesting all the different scenarios..

In my case…I had uploaded my site to GoDaddy and was getting the Parser Error.

I resolved it by commenting out compilers under system.codedom in web.config.
And also add a custom profile for publishing that would precompile during publishing.

  <system.codedom>
    <!--GoDaddy does not compile!-->
    <!--<compilers>
      <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:1659;1699;1701" />
      <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:41008 /define:_MYTYPE=&quot;Web&quot; /optionInfer+" />
    </compilers>-->
  </system.codedom>

answered Apr 4, 2019 at 23:54

answered Jul 31, 2019 at 5:32

Looking at the error message, part of the code of your Default.aspx is :

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="AmeriaTestTask.Default" %>

but AmeriaTestTask.Default does not exists, so you have to change it, most probably to the class defined in Default.aspx.cs. For example for web api aplications, the class defined in Global.asax.cs is : public class WebApiApplication : System.Web.HttpApplication and in the asax page you have :

<%@ Application Codebehind="Global.asax.cs" Inherits="MyProject.WebApiApplication" Language="C#" %>

answered Mar 22, 2020 at 15:08

I am too late but let me explain how I solved this problem.

This problem is basically because of improper folders/solution structure.

this issue may occur because
1. If you have copied project from other location and trying to run the project.

so to resolve this go to original location and crosscheck the folders and files again.

this works for me.

answered Sep 21, 2015 at 6:14

answered May 19, 2020 at 18:20

I’ve finished simple asp.net web application project, compiled it, and try to test on local IIS. I’ve create virtual directory, map it with physical directory, then put all necessary files there, including bin folder with all .dll’s
In the project settings, build section, output path is bin
So when i try to browse my app i got:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Parser Error 
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. 

Parser Error Message: Could not load type 'AmeriaTestTask.Default'.

Source Error: 


Line 1:  <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="AmeriaTestTask.Default" %>
Line 2:  
Line 3:  <%@ Register assembly="AjaxControlToolkit" namespace="AjaxControlToolkit" tagprefix="ajaxToolkit" %>


Source File: /virtual/default.aspx    Line: 1 

Have read similar problem posts and solution was to set output path to bin, but it is defalut for my project.

asked Feb 10, 2013 at 17:36

answered Jun 16, 2016 at 6:39

Sometimes it happens if you either:

1. Clean solution/build or,
2. Rebuild solution/build.

If it ‘suddenly’ happens after such, and your code has build-time errors then try fixing those errors first.

What happens is that as your solution is built, DLL files are created and stored in the projects bin folder. If there is an error in your code during build-time, the DLL files aren’t created properly which brings up an error.

A ‘quick fix’ would be to fix all your errors or comment them out (if they wont affect other web pages.) then rebuild project/solution

If this doesn’t work then try changing:
CodeBehind=»blahblahblah.aspx.cs»

to:
CodeFile=»blahblahblah.aspx.cs»

Note: Change «blahblahblah» to the pages real name.

answered Sep 14, 2017 at 15:00

I have solved it this way.

Go to your project file let’s say project/name/bin and delete everything within the bin folder. (this will then give you another error which you can solve this way)

then in your visual studio right click project’s References folder, to open NuGet Package Manager.

Go to browse and install «DotNetCompilerPlatform».

answered Sep 19, 2018 at 9:15

Faced the same error when I had a programming error in one of the ASHX files: it was created by copying another file, and inherited its class name in the code behind statement. There was no error when all ASPX and ASHX files ran in IIS Express locally, but once deployed to the server they stopped working (all of them).

Once I found that one ASHX page and fixed the class name to reflect its own class name, all ASPX and ASHX files started working fine in IIS.

answered Oct 5, 2016 at 16:17

Very old question here, but I ran into the same error and none of the provided answers solved the issue.

My issue occurred because I manually changed the namespace and assembly names of the project after initial creation. Took me a little bit to notice that the namespace in the Inherits attribute didn’t match the updated namespace.

Updating that namespace in the Global.asax markup to match the apps namespace fixed the error for me.

answered Oct 16, 2019 at 20:05

IIS 7 or IIS 8 or 8.5 version — if you are migrating from 2003 to 2012/2008 make sure web service are in application type instead virtual directory

In my case, There were new code branch and old code branch was deployed locally in IIS. So it was pointing to old branch code that was not available. So i had deployed my code to IIS with new branch and it is working now.

In my case I missed the compile tag in the .csproj file

<Compile Include="Global.asax.cs">
  <DependentUpon>Global.asax</DependentUpon>
  <CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Compile>

answered Apr 30, 2018 at 10:24

Interesting all the different scenarios..

In my case…I had uploaded my site to GoDaddy and was getting the Parser Error.

I resolved it by commenting out compilers under system.codedom in web.config.
And also add a custom profile for publishing that would precompile during publishing.

  <system.codedom>
    <!--GoDaddy does not compile!-->
    <!--<compilers>
      <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:1659;1699;1701" />
      <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:41008 /define:_MYTYPE=&quot;Web&quot; /optionInfer+" />
    </compilers>-->
  </system.codedom>

answered Apr 4, 2019 at 23:54

answered Jul 31, 2019 at 5:32

Looking at the error message, part of the code of your Default.aspx is :

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="AmeriaTestTask.Default" %>

but AmeriaTestTask.Default does not exists, so you have to change it, most probably to the class defined in Default.aspx.cs. For example for web api aplications, the class defined in Global.asax.cs is : public class WebApiApplication : System.Web.HttpApplication and in the asax page you have :

<%@ Application Codebehind="Global.asax.cs" Inherits="MyProject.WebApiApplication" Language="C#" %>

answered Mar 22, 2020 at 15:08

I am too late but let me explain how I solved this problem.

This problem is basically because of improper folders/solution structure.

this issue may occur because
1. If you have copied project from other location and trying to run the project.

so to resolve this go to original location and crosscheck the folders and files again.

this works for me.

answered Sep 21, 2015 at 6:14

answered May 19, 2020 at 18:20

I am getting the following error on one of our production servers. Not sure why it is working on the DEV server?

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type ‘TestMvcApplication.MvcApplication’.

Source Error:

Line 1: <%@ Application Codebehind=»Global.asax.cs» Inherits=»TestMvcApplication.MvcApplication» Language=»C#» %>

Source File: /global.asax Line: 1

Not sure if anybody came across this error before and how it was solved, but I have reached the end.
Any help would be appreciated.

I also need to mention that this is the published code, so all is compiled.
Can there be something wrong with my compiler settings?

None of the other answers worked for me. I fixed my error by changing the web project’s output path. I had had it set to bindebug but the web project doesn’t work unless the output path is set to simply «bin»

I tried all above solutions but no luck. Adding line <add assembly="*" /> to web.config fixed it for me. (You can also add to machine.config or root web.config file of the appropriate .NET framework version, I didn’t try it) Thanks to MS Support for solution.

I had what looked like the same error. I tried many suggestions from many pages only to find out the problem was that I had the website set to the wrong version of .Net

No matter how many re-compiles or people saying ‘configuration problem’, nobody made the point that the .net version needed to be checked.

answered Aug 9, 2011 at 16:27

IT happens with me when I rename my project/solution.
Go to the folder of project in windows explorer (get out of VS).
Find and open the file Global (maybe you’ll find 2 files, open that dont have «.asax.cs» extension), and edit the line of error with correct path.
Good luck!

answered Dec 3, 2009 at 14:05

Make sure your default namespace in the web project properties is the same as the namespace in the Global.asax.cs. I had modified the default namespace to make it a subnamespace, changing it back fixed this issue for me.

I had the same error and none of your solutions helped. I think my problem was simply the name that I had chosen for the project. I had named my project ‘interface’ which when I got the parse error it said that it couldn’t load:

Line 1: <%@ Application Codebehind=»Global.asax.cs» Inherits=»@interface.MvcApplication» Language=»C#» %>

Where there was an ‘@’ sign for some reason. I am guessing the word ‘interface’ is reserved for something else and it added the @ symbol but that obviously broke something. I deleted the project and made a new one with a different name with no problems.

I had a lot of problems and errors to solve, some of the above answers helped, but what the final trick that made it work for me was: Go to your project, click properties.

Go to the Package/Publish Web tab and make sure the configuration is set to Release and Platform to All Platforms.

Last make sure that the «Items to deploy (applies to all deployment methods)» is set to «All files in this project folder»

It then worked fine for me.

answered Jul 13, 2011 at 14:20

This issue is complicated because it’s easy to confuse the root cause with whatever the immediate cause happens to be.

In my case, the immediate cause was that the solution is configured to use NuGet Package Restore, but the server was not connected to the internet, so NuGet was unable to download the dependencies when building for the first time.

I believe the root cause is simply that the solution is unable to resolve dependencies correctly. It may be an incorrect path configuration, or the wrong version of an assembly, or conflicting assemblies, or a partial deployment. But in all cases, the error is simply saying that it can’t find the type specified in global.asax because it can’t build it.

answered Mar 4, 2013 at 19:47

Make sure that the Namespace in the Global.asax file matches that in the Global.cs file i.e.

Global.asax: Some.Website.Webapplication

Global.cs: Some.Website (minus the ‘WebApplication’)

answered Feb 4, 2016 at 20:43

For me, it was because I had temporarily excluded the file from the project. I merely included it in back in the project and then it worked.

answered Nov 20, 2013 at 10:42

answered Mar 5, 2014 at 22:08

answered Oct 14, 2011 at 14:57

Follow these steps:

1. Build
2. Configuration Manager
3. Put the AnyCPU project
4. Back to generate
5. Ready, after this just follow the same steps to pass it to x86 or x64

For me, I had a DLL included with my project that had to be run in a 32-bit environment.

The server was configured to run the website in 32-bit mode, but I was not able to run the application on my 64-bit machine because the localhost folder had not been specified to run in 32-bit mode.

answered May 24, 2013 at 18:47

I just had a similar problem.

The reason was that I was changing a file.aspx.c and had to do a clean rebuild. After that everything worked.

answered Oct 10, 2013 at 11:13

My problem was that I was trying to create a ASPX web application in a subfolder of a folder that already had a web.config file, and

So I opened up the parent folder in Visual Studio as a Web Site (Open > Web Site) I was able to add a new item ASPX page that had no issue parsing/loading.

answered Dec 5, 2013 at 19:55

answered Dec 17, 2013 at 23:58

I’ve had the same issue.
Try to:

Right click on the project and select Clean, then right click on it again and select Rebuild and run the project to see if it worked.

answered Jan 2, 2014 at 12:54

I am getting the following error on one of our production servers. Not sure why it is working on the DEV server?

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type ‘TestMvcApplication.MvcApplication’.

Source Error:

Line 1: <%@ Application Codebehind=»Global.asax.cs» Inherits=»TestMvcApplication.MvcApplication» Language=»C#» %>

Source File: /global.asax Line: 1

Not sure if anybody came across this error before and how it was solved, but I have reached the end.
Any help would be appreciated.

I also need to mention that this is the published code, so all is compiled.
Can there be something wrong with my compiler settings?

None of the other answers worked for me. I fixed my error by changing the web project’s output path. I had had it set to bindebug but the web project doesn’t work unless the output path is set to simply «bin»

I tried all above solutions but no luck. Adding line <add assembly="*" /> to web.config fixed it for me. (You can also add to machine.config or root web.config file of the appropriate .NET framework version, I didn’t try it) Thanks to MS Support for solution.

I had what looked like the same error. I tried many suggestions from many pages only to find out the problem was that I had the website set to the wrong version of .Net

No matter how many re-compiles or people saying ‘configuration problem’, nobody made the point that the .net version needed to be checked.

answered Aug 9, 2011 at 16:27

IT happens with me when I rename my project/solution.
Go to the folder of project in windows explorer (get out of VS).
Find and open the file Global (maybe you’ll find 2 files, open that dont have «.asax.cs» extension), and edit the line of error with correct path.
Good luck!

answered Dec 3, 2009 at 14:05

Make sure your default namespace in the web project properties is the same as the namespace in the Global.asax.cs. I had modified the default namespace to make it a subnamespace, changing it back fixed this issue for me.

I had the same error and none of your solutions helped. I think my problem was simply the name that I had chosen for the project. I had named my project ‘interface’ which when I got the parse error it said that it couldn’t load:

Line 1: <%@ Application Codebehind=»Global.asax.cs» Inherits=»@interface.MvcApplication» Language=»C#» %>

Where there was an ‘@’ sign for some reason. I am guessing the word ‘interface’ is reserved for something else and it added the @ symbol but that obviously broke something. I deleted the project and made a new one with a different name with no problems.

I had a lot of problems and errors to solve, some of the above answers helped, but what the final trick that made it work for me was: Go to your project, click properties.

Go to the Package/Publish Web tab and make sure the configuration is set to Release and Platform to All Platforms.

Last make sure that the «Items to deploy (applies to all deployment methods)» is set to «All files in this project folder»

It then worked fine for me.

answered Jul 13, 2011 at 14:20

This issue is complicated because it’s easy to confuse the root cause with whatever the immediate cause happens to be.

In my case, the immediate cause was that the solution is configured to use NuGet Package Restore, but the server was not connected to the internet, so NuGet was unable to download the dependencies when building for the first time.

I believe the root cause is simply that the solution is unable to resolve dependencies correctly. It may be an incorrect path configuration, or the wrong version of an assembly, or conflicting assemblies, or a partial deployment. But in all cases, the error is simply saying that it can’t find the type specified in global.asax because it can’t build it.

answered Mar 4, 2013 at 19:47

Make sure that the Namespace in the Global.asax file matches that in the Global.cs file i.e.

Global.asax: Some.Website.Webapplication

Global.cs: Some.Website (minus the ‘WebApplication’)

answered Feb 4, 2016 at 20:43

For me, it was because I had temporarily excluded the file from the project. I merely included it in back in the project and then it worked.

answered Nov 20, 2013 at 10:42

answered Mar 5, 2014 at 22:08

answered Oct 14, 2011 at 14:57

Follow these steps:

1. Build
2. Configuration Manager
3. Put the AnyCPU project
4. Back to generate
5. Ready, after this just follow the same steps to pass it to x86 or x64

For me, I had a DLL included with my project that had to be run in a 32-bit environment.

The server was configured to run the website in 32-bit mode, but I was not able to run the application on my 64-bit machine because the localhost folder had not been specified to run in 32-bit mode.

answered May 24, 2013 at 18:47

I just had a similar problem.

The reason was that I was changing a file.aspx.c and had to do a clean rebuild. After that everything worked.

answered Oct 10, 2013 at 11:13

My problem was that I was trying to create a ASPX web application in a subfolder of a folder that already had a web.config file, and

So I opened up the parent folder in Visual Studio as a Web Site (Open > Web Site) I was able to add a new item ASPX page that had no issue parsing/loading.

answered Dec 5, 2013 at 19:55

answered Dec 17, 2013 at 23:58

I’ve had the same issue.
Try to:

Right click on the project and select Clean, then right click on it again and select Rebuild and run the project to see if it worked.

answered Jan 2, 2014 at 12:54

Я закончил простой проект веб-приложения asp.net, скомпилировал его и попытался протестировать на локальном IIS. Я создал виртуальный каталог, сопоставил его с физическим каталогом, затем поместил туда все необходимые файлы, включая папку bin со всеми .dll. В настройках проекта, раздел сборки, выходной путь — bin Итак, когда я пытаюсь просмотреть свое приложение, я получил :

Server Error in '/' Application.
--------------------------------------------------------------------------------

Parser Error 
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. 

Parser Error Message: Could not load type 'AmeriaTestTask.Default'.

Source Error: 


Line 1:  <%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="AmeriaTestTask.Default" %>
Line 2:  
Line 3:  <%@ Register assembly="AjaxControlToolkit" namespace="AjaxControlToolkit" tagprefix="ajaxToolkit" %>


Source File: /virtual/default.aspx    Line: 1 

Прочитал похожие сообщения о проблемах, и решение состояло в том, чтобы установить выходной путь в bin, но это по умолчанию для моего проекта.

Я знаю, что слишком поздно, чтобы ответить, но это может помочь другим и сэкономить время.

Ниже могут быть другие решения.

Solution 1: Подробные инструкции по созданию виртуального каталога для вашего приложения см. в разделе Создание виртуального каталога для вашего приложения.

Solution 2: Папка Bin вашего приложения отсутствует или отсутствует DLL-файл приложения. Подробные инструкции см. в разделе Копирование файлов приложения на рабочий сервер.

Solution 3: Возможно, вы выполнили развертывание в корневой веб-папке, но не изменили некоторые параметры в файле Web.config. Подробные инструкции см. в разделе Развертывание в корневом каталоге.

В моем случае Solution 2 работает, при развертывании на сервере некоторых DLL's от bin каталог не был успешно загружен на сервер. У меня есть заново закачать все DLL и это работает !!

Вот реферальная ссылка на решить ошибку парсера asp.net.

Создан 18 сен.

Я была такая же проблема. Провел 5 или 6 часов исследований. Кажется, простое решение работает. Мне просто нужно было преобразовать мою папку в приложение из iis. Это работало нормально. (это был сценарий, когда я выполнил миграцию с сервера 2003 на сервер 2008 R2)

(1) Откройте IIS и выберите веб-сайт и соответствующую папку, которую необходимо преобразовать. Щелкните правой кнопкой мыши и выберите «Преобразовать в приложение».

ответ дан 20 авг.

Создан 16 июн.

Иногда это происходит, если вы либо:

1. Чистое решение/сборка или,
2. Перестроить решение/сборка.

Если это «внезапно» произойдет после этого, и ваш код строить-time, попробуйте сначала исправить эти ошибки.

Что происходит, так это то, что по мере создания вашего решения файлы DLL создаются и сохраняются в папке bin проектов. Если во время сборки в вашем коде возникает ошибка, файлы DLL создаются неправильно, что приводит к ошибке.

«Быстрое исправление» будет заключаться в том, чтобы исправить все ваши ошибки или закомментировать их (если они не повлияют на другие веб-страницы), а затем перестроить проект/решение.

Если это не работает, попробуйте изменить:
CodeBehind=»blahblahblah.aspx.cs»

чтобы:
CodeFile=»blahblahblah.aspx.cs»

Примечание. Измените «blahblahblah» на настоящее имя страницы.

Создан 23 фев.

Я решил это так.

Перейдите к файлу проекта, скажем, project/name/bin и удалите все в папке bin. (это даст вам еще одну ошибку, которую вы можете решить таким образом)

затем в вашей визуальной студии щелкните правой кнопкой мыши папку проекта «Ссылки», чтобы открыть диспетчер пакетов NuGet.

Перейдите к просмотру и установке «DotNetCompilerPlatform».

Создан 19 сен.

Столкнулся с той же ошибкой, когда у меня была ошибка программирования в одном из файлов ASHX: он был создан путем копирования другого файла и унаследовал имя своего класса в операторе кода позади. Не было ошибки, когда все файлы ASPX и ASHX запускались в IIS Express локально, но после развертывания на сервере они перестали работать (все).

Как только я нашел эту страницу ASHX и исправил имя класса, чтобы оно отражало его собственное имя класса, все файлы ASPX и ASHX начали нормально работать в IIS.

ответ дан 05 окт ’16, 17:10

Здесь очень старый вопрос, но я столкнулся с той же ошибкой, и ни один из предоставленных ответов не решил проблему.

Моя проблема возникла из-за того, что я вручную изменил пространство имен и имена сборок проекта после первоначального создания. Мне потребовалось немного времени, чтобы заметить, что пространство имен в Inherits атрибут не соответствует обновленному пространству имен.

Обновление этого пространства имен в разметке Global.asax для соответствия пространству имен приложений исправило ошибку для меня.

ответ дан 16 окт ’19, 21:10

Создан 31 июля ’15, 10:07

ответ дан 27 дек ’17, 14:12

В моем случае я пропустил тег компиляции в файле .csproj.

<Compile Include="Global.asax.cs">
  <DependentUpon>Global.asax</DependentUpon>
  <CopyToOutputDirectory>Always</CopyToOutputDirectory>
</Compile>

ответ дан 30 апр.

Интересны разные сценарии..

В моем случае… я загрузил свой сайт в GoDaddy и получил ошибку парсера.

Я решил это, закомментировав compilers под system.codedom в веб.конфигурации. А также добавить настраиваемый профиль для публикации, который бы прекомпилировался во время публикации.

  <system.codedom>
    <!--GoDaddy does not compile!-->
    <!--<compilers>
      <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:1659;1699;1701" />
      <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" type="Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" warningLevel="4" compilerOptions="/langversion:default /nowarn:41008 /define:_MYTYPE=&quot;Web&quot; /optionInfer+" />
    </compilers>-->
  </system.codedom>

ответ дан 05 апр.

Создан 31 июля ’19, 06:07

Глядя на сообщение об ошибке, часть кода вашего Default.aspx является :

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="AmeriaTestTask.Default" %>

но AmeriaTestTask.Default не существует, поэтому его необходимо изменить, скорее всего, на класс, определенный в Default.aspx.cs. Например, для приложений веб-API класс, определенный в Global.asax.cs: public class WebApiApplication : System.Web.HttpApplication и на странице asax у вас есть:

<%@ Application Codebehind="Global.asax.cs" Inherits="MyProject.WebApiApplication" Language="C#" %>

ответ дан 22 мар ’20, в 15:03

Я слишком поздно, но позвольте мне объяснить, как я решил эту проблему.

Эта проблема в основном из-за неправильной структуры папок/решений.

эта проблема может возникнуть из-за того, что 1. Если вы скопировали проект из другого места и пытаетесь запустить проект.

поэтому, чтобы решить эту проблему, перейдите в исходное местоположение и снова проверьте папки и файлы.

это работает для меня.

Создан 21 сен.

ответ дан 19 мая ’20, 19:05

Это происходит, когда файлы в папке «Отладка и выпуск» не созданы должным образом (либо они имеют неправильную ссылку, либо перезаписываются много раз). Я столкнулся с той же проблемой, когда все работает нормально, когда мы создаем решение, но когда я публикую веб-сайт, он дает мне ту же ошибку. Я решил это следующим образом:

1. Перейдите в обозреватель решений в Visual Studio и нажмите «Показать скрытые файлы» (если они не отображаются!)
2. вы найдете папку с именем obj, откройте ее.
3. Здесь снова есть 2 папки с именами соответственно Debug и Release. Теперь удалите содержимое из этих двух папок. Убедитесь, что вы не удалили папки Debug и Release. Удаляйте только файлы и папки внутри папки Debug and Release.
4. Теперь создайте и опубликуйте свое решение, и все будет работать как часы.

Создан 20 сен.

Hey I am getting the following error

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type ‘_AddToCart’.

Source Error:

Line 1:  <%@ Page Language="C#" AutoEventWireup="true" Codebehind="AddToCart.aspx.cs" Inherits="_AddToCart" Title="Untitled Page" %>
Line 2:  
Line 3:  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


Source File: /FSAICart/AddToCart.aspx    Line: 1 

Where I do have the matching code behind file which is defined as follows

    using System;
  public partial class _AddToCart : System.Web.UI.Page {

Any Ideas ?