How to create an ASP.NET application with IIS 6

[Sreejumon[MVP]]

Hi,

Here is the simple check list.
1. First ensure that IIS is running. Type httP://localhost
in your browser and check the result. If No, please
install IIS first.
2. Create one windows application, and ensure that your
VS.net is working properly.:)
3. Now create one ASP.Net application, then tell me what
error your are getting?
regards
Sreejumon[MVP]
www.mstechzone.com

-----Original Message-----
Could someone please point out or provide a checklist of how to starta new ASP.NET application? I have Windows Server 2003 on one machineand Visual Studio.Net 2003 on an XP pro machine. I've run
aspnet_regiis. With IIS 5.1 on XP and Visual Studio on the samemachine, it just worked! Not so with IIS 6. I've searched newsgroupsand tried what I found there - no dice. Bottom line: does this stuffwork or not? Is it broken or not? Why doesn't this get fixed? Sorry tobe so blunt, but this is frustrating! Thanks in advance.

George Morrone
.

[George Morrone]

1. IIS on the server is started and responding with a simple "hello
world" html web page.

2. Visual Studio is working otherwise with no problem.

The error message when I try to start a new VB or C# .Net web
application is:

"The default web access mode for this project is set to file share,
but the project folder at "http://servername/project" cannot be opened
with the path \\servername\wwwroot$\project. The UNC share
\\servername\wwwroot$\project does not exist or you do not have
access. What would you like to do:
(retry using a different file share path, or try to open the project
with FrontPage Server Extensions."

I followed the instructions in Knowledge Base article 320265, but it
still didn't work. I'm trying it again to duplicate the problem and
will let you know the results. What I see now that I didn't notice
before is that there is no VS Developers group on the server.
Shouldn't running aspnet_regiis -i create that, or do I have to
install the .Net Framework SDK on the server? That's what I'm
downloading now. (It'll take a while.)

Still, it seems like a lot of hoops to jump through just to create a
new project, especially for something as important to Microsoft as
ASP.Net, on the latest and greatest operating system and development
environment. (I really mean that; I'm an experienced programmer and
really like Visual Studio.Net.) But if it's not too much to ask,
please Microsoft, just fix this?

Thanks.

George Morrone

[Ken Cox [Microsoft MVP]]

Strange. I wonder if it would work if you copy the DVD contents to a folder on
the server's hard drive and then did the installation when logged onto the
server as an admin - not through remote desktop?

--
Microsoft MVPs have a question for *you*: Are you patched against the Worm?
http://www.microsoft.com/security/se...s/ms03-026.asp

"George Morrone" <ge********@hotmail.com> wrote in message
news:5d**************************@posting.google.c om...
When the SDK didn't do it, I thought to install VS.Net itself on the
server (never saw in any book that this is required. Most of the time
I suppose authors assume the reader is running with IIS 5.1 installed
on the XP Pro client.) I noticed that there is a check box for
"install server components."

However, when I try to install on the server, I get the following
error:

"At least one component has an install path set to a mapped drive.
Installing to mapped drives is not supported." I tried installing only
the server components, same message.

Now, my setup is this: the server is a minimal Dell Poweredge; no
monitor and just a CD-rom drive for removable media. I use remote
desktop connection, of course, to manage it. I was installing from a
shared DVD drive on the XP workstation. I tried copying the contents
of the VS .Net 2003 DVD to a folder on the server's hard drive and
installing from there; same message.

Thanks again.

George Morrone

[George Morrone]

Ken:

Fortunately the server and workstation are right next to each other so
it's easy to switch the monitor cable to the server. Does it make any
difference that the server is a domain controller, and the workstation
is not on the domain, just accessed through the workgroup? Shouldn't,
right?

So I verified that the logon account has administrator rights, and
tried installing VS.Net 2003 again, this time logged on locally. Same
result: "At least one component has an install path set to a mapped
drive. Installing to mapped drives is not supported."

George


"Ken Cox [Microsoft MVP]" <BA************@sympatico.ca> wrote in message news:<u#**************@TK2MSFTNGP12.phx.gbl>...

Strange. I wonder if it would work if you copy the DVD contents to a folder > On the server's hard drive and then did the installation when logged onto the
server as an admin - not through remote desktop?

--