IIS no longer displays ASP.NET

Patching my server appears to have broken it

[garann]

A few weeks ago, my server was fine. I installed the new round of patches (post-Blaster, can't recall what it was) and didn't bother to check that the server was still working (it's a development server). Last week, I attempted to pull up the few ASP.NET pages that constitute the site, and I got this:

A dynamic link library (DLL) initialization routine failed.

HTML and classic ASP pages still work, but all my ASPX pages produce that same error message. I tried re-installing both IIS and the .NET framework, but I get the same result. Has anyone had this problem, or heard anything about how those most recent critical patches might impact .NET/IIS?

[duckhunter]

Sounds like the Project's bin/<site>.dll on the box is compiled against another version of some DLL that what is running on the server.

Look at the Framework and Service Pack versions if you compile on one box and run on another or try Re-Building the Project.

[garann]

duckhunter, thanks for your response, but I don't think I follow you. These are just a few loose pages, not a project. There is no bin folder in the root of the site (there are all those _vti_*** folders, which I believe is a classic ASP thing?). I'll try adding an empty bin folder to the root and see if that helps.

In the meantime, any other suggestions?

<added>Here's something kind of funny: When I go into the website's properties and click the Server Extensions tab, it shows this message: "This web is running an old version of the server extensions. To update the server extensions, choose Upgrade Extensions from the Task Menu for this server." When I follow those directions, I get an alert saying "There is no web named ''."</added>

[duckhunter]

Try deleting and re-creating the Web. On the Directory Tab inside of the site properties. Under Application Settings, click REMOVE, Then CREATE, then click OK.

If you are running true .NET (.aspx/.vb/.resx) pages you should have a compiled DLL for the .NET project in a bin folder. I believe this is the preferred way to run .NET

[garann]

Deleting and recreating it doesn't fix the error. Guess I'll have to reinstall Windows.

Doing the whole .aspx/.vb/.resx may be Microsoft's recommendation, but it wouldn't be mine. Complex functions don't belong on a page, whether or not the code for that page is in a seperate file, and there is just no good reason to write HTML that needs to be compiled (i.e., the "server controls"). I use .aspx pages and, when I need to do something that isn't a display function, specialized classes. I've yet to have any problems as a result.

Thanks for your help!