Modify application after Deployment

[Frinavale]

I didn't realize you had classic asp in the mix.
How did you include the classic asp into the application???

[stefbek97]

The application was written in classic by a different programmer. Any new nodes to the application I write in .net for many reasons. I just publish my web site/project to the same folder on the server with the classic asp pages. In the classic asp pages I modify the code to point to my new pages and include any query strings needed. That is about it

[Frinavale]

Ok, I have a feeling this has something to do with ASP classic.
You're probably running 2 different applications pools (but I'm not sure how ASP classic works). It's probably not the ASP.NET compiler crashing because you are able to build your solution to create a pre-compiled version of your .NET web application. This problem probably has to do with the way your ASP classic code is working.

I'm going to move your question to the ASP classic forum and hopefully you can get more help on the issue there.

-Frinny

[stefbek97]

Thank you for your help.

[CroCrew]

Hello stefbek97,

Isolate the problem and future problems by placing all your websites within their own application pool.

Under IIS you will see a folder called “ApplicationPoo l” there you can create a new pool for your Virtuals/Web sites.

Then in IIS right click on the virtual/website that is having the problems and select properties. Then look under the “Virtual Directory” tab and you will see where you can change it to the new application pool you have created.

When you start creating more and more DotNet application under different Frameworks you will see the need for creating more application pools. I Have create a pool for every version of DotNet Frameworks there are and what ever Framework I build a site under I place it in that Application Pools Framework.

Hope this helps,
CroCrew~

[CroCrew]

Hello stefbek97,

It has been a few days. Has this problem been resolved?

CroCrew~

[stefbek97]

Not really. I am not sure what to do at this point.

[CroCrew]

Did you try creating a new application pool?

[stefbek97]

I did and I cant get the app to work in the new pool.

[CroCrew]

You cant get it to work at all?

[JamieHowarth0]

Hi guys,

1) Thread moved, this is not related to classic ASP.
2) The problem you're having is that when a website is run in ASP.NET, ASP.NET caches the compiled code into C:\WINDOWS\Micr osoft.NET\Frame work\(version you are using)\Temporar y ASP.NET Files. When you change the codebase on the webserver, ASP.NET tries to see what file you are accessing, and then tries to run the cached code if applicable. If the cached file is not equal to the file being requested, this error springs up.
Every time you make live code changes you will either need to:
a) recycle the app pool, or;
b) clear the Temporary ASP.NET Files directory.

It's easier and more sensible to do a) because b) is a side-effect of a).

BTW check which version of ASP.NET your website is configured to use and ensure that any other applications sharing the same AppPool are using the same version (as per CroCrew's recommendations ). You cannot run two versions of ASP.NET inside a single application pool - this is by design.

Hope this helps.

codegecko

[Frinavale]

CG I don't know if this is really related to the issue.

I just tested this and every time I make a change to my ASP.NET code (and compiled it) the files in the "Temporary ASP.NET Files" directory are automatically changed to the newest version (old ones are replaced with the new ones) the first time the website is accessed.

I still think it has to do with the ASP classic.

What happens when you have ASP.NET code and ASP classic code running in the same virtual directory/website?

I would assume it would go something like:

• User accesses classic ASP page
• Classic ASP compiler compiles the ASP page
• User clicks link in Classic ASP page
• Classic ASP compiler compiles the ASP page and executes the ASP code associated with the link that results in redirecting user to ASP.NET page
• ASP.NET finds cached version of aspx page and uses that to do stuff and return the page to the user

The problem is that the compiler's crashing.
I'm assuming it's the ASP classic compiler because the ASP.NET compiler isn't required since there's a cached version website.

I don't understand why the OP has to delete the files in the temporary ASP.NET files directory when this is automatically done.

What I really don't understand is how the ASP classic code is sharing an application pool with the ASP.NET code....I've never done this before so I have no clue.

[Frinavale]

@Stefbek97: I'm just wonder, what version of IIS are you using?

[JamieHowarth0]

@Frinny, the Classic ASP compiler and the .NET compiler are two separate ISAPIs which are only executed when a matching request is made to the web server (.asp for ClASP, .aspx for .NET), so it can't be a compiler mis-match.

@Stefbek97, what's the error when you move the site to it's own application pool?
If you could reply with the following info:
* IIS version
* ASP.NET version of the site
* Application pool identity
* Error message

then hopefully we can try and isolate the issue.

codegecko

[Frinavale]

@Frinny, the Classic ASP compiler and the .NET compiler are two separate ISAPIs which are only executed when a matching request is made to the web server (.asp for ClASP, .aspx for .NET)

Thanks for the clarification :)

so it can't be a compiler mis-match.

I didn't think it was a compiler mismatch.
I think that it's the ASP classic compiler that's failing when the following error happens:

Compiler Error Message: The compiler failed with error code -1073741502.

Is there a way to cache ASP classic pages? (eg precompile them the same way you can precompile an ASP.NET application)

If so, it could be that the cached version of the ASP classic page is still referencing the old ASP.NET application, which it can't find any more because it's been updated. If so, all you'd have to update the ASP classic whenever you update the ASP.NET application.