Open project error

[Nexus]

Everytime I try and open an asp.net project in visual basic .NET 2003, which was written in vb 2003 I get the error

 

Visual Studio .NET had detected that the specificed web server

is not running ASP.NET version 1.1. You will be unable to run

ASP.NET web applications or services.

 

 

I know it needs internet information services, I installed that, then re-installed the .net framework 1.1 but it still won't open, is there anything else I need?

[PlausiblyDamp]

try

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -i

 

(update to your installation of windows)

[Nexus]

that helped, but now I get a new error:

 

Visual Studio.NET cannot create or open the application.

The likliest problem is that required components are not installed on the local Web server. Run Visual Studio.NET setup and add the Web development component.

 

I ran the setup but there wasn't anything more I could add, I only have VB.NET standard, do I need something higher or can I get this component from somewhere?

[dotnet]

Framework directory missing?

 

I can't seem to find that directory?

[birbilis]

Solution to your problem

 

> Re: _830663 Visual Studio .NET cannot create the application

<application>. The likeliest problem is that required

> components are not installed on the local Web server

>

> Hi, it seems a cause for this one (shown when doing "File/New/VB.net Web

application" for example)

> is that "File and Printer Sharing" is not installed (can open a Network

connection's properties and

> at the last page install the respective service). Have to reboot then

 

This one was definitely needed to solve the problem (had to reboot before a

"Sharing" tab would be shown again [was missing!] at a File/Folder's

properties dialog, so I assume the reboot is needed after all)

 

> if then they see any "403 access forbidden" errors when trying to create

new

> ASP.net web applications, better uninstall and reinstall IIS, then try

> installing the Visual Studio.net prerequisites from the original Visual

> Studio CD installer, then use "aspnet_regiis -i" from the appropriate .NET

> framework subfolder under %windir%\Microsoft.NET\Framework. May need to

> run "regsvr32" on the "aspnet_isapi.dll" at the same folder, see

> http://www.winnetmag.net/Articles/Index.cfm?ArticleID=37942

 

The steps that solved the 403 error that I was getting after I solved the

previous problem were:

 

1) I uninstalled IIS

2) then inserted the Visual Studio 2003.net Prerequisites CD, run the

"setup.exe" (not the "autorun.exe") and at the question that I should insert

the #1 CD of VStudio.net 2003, I answered "No", so that ALL prerequisites

would be installed (needed the "FrontPage Server Extensions" which weren't

being automatically selected for installation before for some strange reason

[iIS was installed, the File and Printer Sharing wasn't, maybe that caused a

problem with your automatic prerequisites determination logic])

3) run "aspnet_regiis -i" to reregister ASP.net (at the

"%windir%\Microsoft.NET\Framework\v1.1.4322"

4) just in case I also did regsvr32 on the "aspnet_isapi.dll" at the same

folder

 

Then both Visual Studio 2002 and Visual Studio 2003 were fixed and can now

create a new Web Application from the File/New Menu

 

I also see it fixed another problem, with Microsoft Baseline Security

Analyzer, where at "Computer name" it was showing "workgroup\*** error ***"

instead of "workgroup\agrinio (this computer)" which is now correctly

showing there.

 

Also after scanning the address "127.0.0.1", it's now showing "Computer is

running Windows 2000 or greater" whereas before it was saying "Computer is

not running Windows OS" (explanation was saying I might be running NT etc.).

This last one might have been the result of some bad crash my machine had

due to an accidental rename of the HKLM\Software\Microsoft\Windows

NT\CurrentVersion registry key which was partially done by RegEdit, didn't

show the change and didn't allow me to undo it till at reboot hard resets

were happening just before the showing of the logon screen - have finally

almost manually restored the system (couldn't use last good configuration

boot option, seems it also corrupted it at reboot unfortunately)

 

greetings,

George