Member Avatar for morris2k2

It all started like this I created a sub directory in my hosting account, for blog engine 1.5. I then copied all the file from the source to the target sub directory folder which is under my root application. when I lauched this is the error I was getting

To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

I replaced the "RemoteOnly" with "Off"

this is the new error am having now

Server Error in '/Mayflowerblog' Application.
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: CS0103: The name 'ExtensionManager' does not exist in the current context

Source Error:


Line 53: for each (SortedExtension x in sortedExtensions)
Line 54: {
Line 55: if (ExtensionManager.ExtensionEnabled(x.Name))
Line 56: {
Line 57: a.CreateInstance(x.Type);


Source File: e:\web\mayflowerpo\htdocs\Mayflowerblog\Global.asax Line: 55

Please what do I do?

  • 2 Contributors
  • 1 Reply
  • 113 Views
  • 6 Hours Discussion Span
  • Latest Post Latest Post by kvprajapati

Dani AI

Generated

Short answer: the blog must run as its own ASP.NET application. What happened here is a deployment/layout issue — placing BlogEngine 1.5 under an existing web application (a plain subfolder) prevents the site from being compiled/isolated the way BlogEngine expects, which produces the compilation errors seen in Global.asax. As described, the files were copied into a subdirectory; as suggested, the correct fixes are to make that folder a separate application or host it as its own site/subdomain.

What to do (practical fixes)

  • If you control IIS: use IIS Manager, right‑click the blog folder and convert it to an Application. Assign an app pool that targets the correct .NET version for BlogEngine 1.5. This creates the application boundary so App_Code, bin and web.config are compiled/isolated correctly.
  • On shared hosting: either create a subdomain that points to the blog folder, or ask support to mark that folder as an application for you. Many control panels expose an “Add Application” or “Create Application” action.
  • If neither is possible, precompile the site locally and deploy the compiled output (so it does not rely on dynamic App_Code compilation). Example using the ASP.NET compiler:
aspnet_compiler -p "C:\Projects\BlogEngine" -v / "C:\Publish\BlogEngine"

Copy the published content and the generated assemblies in the bin folder to your host.

Quick troubleshooting checklist

  • Confirm the blog folder is an IIS application (or hosted as its own site/subdomain).
  • Ensure the app pool .NET version matches BlogEngine 1.5 requirements (check host docs).
  • Verify the blog’s bin contains the BlogEngine DLLs (and that App_Code has been precompiled or is being compiled).
  • If problems remain, recycle the app pool or ask the host to clear Temporary ASP.NET Files so the site recompiles cleanly.

References

  • IIS: creating a virtual directory / application:
  • aspnet_compiler tool (precompile):
  • BlogEngine.NET repo: https://github.com/rxtur/BlogEngine.NET
Member Avatar for kvprajapati

>Please what do I do?

You can't deploy your web app in sub-folder. Create/configure sub-domain.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.