Skip to main content

Hosting an ASP.NET 3.5 website on IIS 7

Although using IIS is not that hard, I had some issues to get my website deployed. As I didn't install the webserver, it took me a while to find out which features were missing. The following steps can help you checking if your server is ASP.NET 3.5 ready:

Install the Web Server Role

  • In Role Services, select ASP.NET and continue.

Install the .NET 3.5 Framework

Publish Your Application

  • In Visual Studio, publish your web project to a local folder, like on the desktop.

  • Copy that folder to a local folder on the webserver, maybe somewhere like c:\apps.

  • From the IIS Manager, right click your Default Web Site and "Add Application".

Enable ASP.NET Impersonation on your Website

  • IIS -> Your website -> Authentication -> Enable ASP.NET Impersonation.

Test your Application

  • Open a browser, and try http://localhost, verify that the IIS 7 page comes up and you know IIS 7 is installed correctly.

  • Then test your application by browsing to http://localhost/your_application.

Troubleshooting

  • If you receive .NET 3.5.0.0 reference errors or csc.exe not found, make sure you've installed the .NET 3.5 framework.

  • If your web page does not display correctly, or images are missing, check all of your url links.  For all of your url links, use an absolute path like "~/Images/".

  • If you receive an error connecting to a local database, "Invalid login for NT AUTHORITY/NETWORK SERVICE"... open SQL Management Studio, add a new login, find the NETWORK SERVICE credential and grant that login db_owner permissions for your database(or use a dedicated user for your application pool).

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more