March 3, 2021
Hot Topics:

Uh Oh, I Can't Create an ASP.NET Project

  • By Paul Kimmel
  • Send Email »
  • More Articles »

I Tried Everything and Still No Luck

Recently, I got an error indicating that a new ASP.NET Web Application would have to be made ASP.NET 1.0 compatible. I thought for sure that I had forgotten to install IIS before installing VS.NET or just had some old media. After checking and re-checking my configuration, it turned out to be neither. Here is how the problem was resolved.

I tried to create an ASP.NET application. The default location was http://localhost/WebApplication1. When I clicked OK, an error was received, indicating that the WWW server was running ASP.NET 1.0. After verifying that IIS 5.1 or greater was running and ASP.NET 1.1 was installed, I tried using the localhost address (see Figure 2). Oddly enough, this worked and created an ASP.NET application without the ASP.NET 1.0 warning message.

Figure 2: Try using the loopback IP if the localhost host name doesn't seem to work correctly.

Then, it suddenly struck me that this foreign network was using a proxy server. By using localhost as the host URL, VS.NET was seeing the proxy server, which must have ASP.NET 1.0 installed on it. The solution, or fix, was to bypass the proxy server.

Because ASP.NET uses the network configuration settings from Internet Explorer, we can change the proxy settings through Internet Explorer. (Keep in mind that this problem and fix are only relevant if you are networked and using a proxy server.)

To change the proxy settings, start Internet Explorer and follow these steps:

  • Select Tools|Internet Options.
  • In the Internet Options dialog, select the Connection tab.
  • On the Connection tab, click the LAN Settings button.
  • If Use a proxy server... is checked in the Proxy server group (see Figure 3), check Bypass proxy server for local address (see Figure 3).
  • Click OK to close the LAN Settings dialog, and close the Internet Options dialog.

Figure 3: If you are having problems creating an ASP.NET application and using a proxy server, try bypassing the proxy server.

Try creating an ASP.NET application again. If it still doesn't work, you may need to uninstall and re-install VS.NET completely. If I encounter any additional fail-receovery scenarios, I will be sure to update you, the faithful reader, in future articles.


It is amazing how easy it is to take things for granted. As software developers, we have to use a huge variety of tools, know how to configure PCs and networks, and actually write stored procedures and code that result in an application that does something useful and does it correctly. It is easy to forget how many skills are involved.

If you are a new developer, the pure number of skills is overwhelming, and if you are learning something new, any disruptions or problems seem magnified. If you find yourself having problems running demos for ASP.NET or Web Services applications, or creating a new project because someone (to remain nameless) forgot to install a necessary prerequisite, I hope this article helps you get the problem solved.


Paul Kimmel is the "VB Today" columnist, has written several books on .NET programming, and is a software architect. You may contact him at pkimmel@softconcepts.com if you need assistance.

Page 2 of 2

This article was originally published on May 24, 2004

Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

Thanks for your registration, follow us on our social networks to keep up-to-date