473,696 Members | 2,045 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

Deploying ASP.NET projects

Hi there, hope someone can help me on this:

I'm planning to deploy several ASP.NET projects to a production server.
Normally I used the "Project / Copy project" option in VS.NET, but to this
production server I only have FTP access. I tried copying the files with a
FTP tool, but it seems that every application needs to have an own virtual
directory, is this true? Or is it possible to just make 1 virtual directory
and put al the projects in there?

So is there a possibility to deploy with ftp access only, or do I need to
ask the system administrator to set up frontpage server extensions?

Greets,

Gerben.
Nov 18 '05 #1
10 2072
Let me see if I can help you to understand these entities better. An ASP.Net
web application is an executable application. Therefore, it must run under
some process. This process is defined by the web server configuration of an
"applicatio n". Because it is a .Net application, directly under the root
folder of the web server application, there must be a bin folder where the
DLLs can be located. Location is almost everything in .Net. The web.config
file containing the "Machine to application" settings for the app must
reside in the root folder of the application. The various ASPX pages and
other files can be located anywhere at or under the root folder of the
application. However, this has nothing whatsoever to do with FrontPage
server extensions. Those are used by Visual Studio.Net for working with the
web server, getting documents, setting up a Web Application, etc. They are
completely unnecessary at run-time.

It is therefore possible to FTP your files to the web server, or to put them
where they belong in any way you like. Setting up the web application in IIS
is something which must be done by the network admin of the web server.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news4.tilbu1 .nb.home.nl...
Hi there, hope someone can help me on this:

I'm planning to deploy several ASP.NET projects to a production server.
Normally I used the "Project / Copy project" option in VS.NET, but to this
production server I only have FTP access. I tried copying the files with a
FTP tool, but it seems that every application needs to have an own virtual
directory, is this true? Or is it possible to just make 1 virtual directory and put al the projects in there?

So is there a possibility to deploy with ftp access only, or do I need to
ask the system administrator to set up frontpage server extensions?

Greets,

Gerben.

Nov 18 '05 #2
Hi Kevin,

First of all thanks for your reply. I'm not understanding you 100%, but
let's see if I'm right:

- An ASP.NET project is an application and not just a couple of webpages. By
making a virtual directory for a project IIS knows that hat virtual
directory is an application. So every project needs an own virtual directory
to run, you cannot have multiple projects in 1 virtual directory since every
virtual directory represents an application.

- Frontpage server extensions can automaticly create a virtual directory on
a remote server so that a ASP.NET can directly be run.

So this would conclude that when you only have FTP access to a webserver it
isn't posible the deploy ASP.NET projects?

greets,

Gerben.

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:eZ******** ********@TK2MSF TNGP11.phx.gbl. ..
Let me see if I can help you to understand these entities better. An ASP.Net web application is an executable application. Therefore, it must run under
some process. This process is defined by the web server configuration of an "applicatio n". Because it is a .Net application, directly under the root
folder of the web server application, there must be a bin folder where the
DLLs can be located. Location is almost everything in .Net. The web.config
file containing the "Machine to application" settings for the app must
reside in the root folder of the application. The various ASPX pages and
other files can be located anywhere at or under the root folder of the
application. However, this has nothing whatsoever to do with FrontPage
server extensions. Those are used by Visual Studio.Net for working with the web server, getting documents, setting up a Web Application, etc. They are
completely unnecessary at run-time.

It is therefore possible to FTP your files to the web server, or to put them where they belong in any way you like. Setting up the web application in IIS is something which must be done by the network admin of the web server.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news4.tilbu1 .nb.home.nl...
Hi there, hope someone can help me on this:

I'm planning to deploy several ASP.NET projects to a production server.
Normally I used the "Project / Copy project" option in VS.NET, but to this production server I only have FTP access. I tried copying the files with a FTP tool, but it seems that every application needs to have an own virtual directory, is this true? Or is it possible to just make 1 virtual

directory
and put al the projects in there?

So is there a possibility to deploy with ftp access only, or do I need to ask the system administrator to set up frontpage server extensions?

Greets,

Gerben.


Nov 18 '05 #3
Hi Gerben,

You are nearly 100% correct, and in fact, I may just be misunderstandin g
your last remark, and you may be 100% correct. It is certainly possible to
deploy ASP.Net projects using only FTP, as long as the web site is already
configured as an application.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news3.tilbu1 .nb.home.nl...
Hi Kevin,

First of all thanks for your reply. I'm not understanding you 100%, but
let's see if I'm right:

- An ASP.NET project is an application and not just a couple of webpages. By making a virtual directory for a project IIS knows that hat virtual
directory is an application. So every project needs an own virtual directory to run, you cannot have multiple projects in 1 virtual directory since every virtual directory represents an application.

- Frontpage server extensions can automaticly create a virtual directory on a remote server so that a ASP.NET can directly be run.

So this would conclude that when you only have FTP access to a webserver it isn't posible the deploy ASP.NET projects?

greets,

Gerben.

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:eZ******** ********@TK2MSF TNGP11.phx.gbl. ..
Let me see if I can help you to understand these entities better. An ASP.Net
web application is an executable application. Therefore, it must run under
some process. This process is defined by the web server configuration of

an
"applicatio n". Because it is a .Net application, directly under the root
folder of the web server application, there must be a bin folder where the DLLs can be located. Location is almost everything in .Net. The web.config file containing the "Machine to application" settings for the app must
reside in the root folder of the application. The various ASPX pages and
other files can be located anywhere at or under the root folder of the
application. However, this has nothing whatsoever to do with FrontPage
server extensions. Those are used by Visual Studio.Net for working with

the
web server, getting documents, setting up a Web Application, etc. They are completely unnecessary at run-time.

It is therefore possible to FTP your files to the web server, or to put

them
where they belong in any way you like. Setting up the web application in

IIS
is something which must be done by the network admin of the web server.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news4.tilbu1 .nb.home.nl...
Hi there, hope someone can help me on this:

I'm planning to deploy several ASP.NET projects to a production server. Normally I used the "Project / Copy project" option in VS.NET, but to

this production server I only have FTP access. I tried copying the files
with a FTP tool, but it seems that every application needs to have an own virtual directory, is this true? Or is it possible to just make 1 virtual

directory
and put al the projects in there?

So is there a possibility to deploy with ftp access only, or do I need to ask the system administrator to set up frontpage server extensions?

Greets,

Gerben.



Nov 18 '05 #4
Hi again kevin,

Yeah ok, when the virtual directory is already setup it is posible to deploy
with FTP. I will ask the server administrator to setup frontpage server
extensions then. I suppose creating virtual directory's isn't an exciting
task for a server administrator :). Kinda unhandy deploying asp.net compared
to asp where you could just drop the files anywhere you want.

Thanks again for your help Kevin.

Greets,

Gerben.

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:u1******** ******@TK2MSFTN GP10.phx.gbl...
Hi Gerben,

You are nearly 100% correct, and in fact, I may just be misunderstandin g
your last remark, and you may be 100% correct. It is certainly possible to
deploy ASP.Net projects using only FTP, as long as the web site is already
configured as an application.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news3.tilbu1 .nb.home.nl...
Hi Kevin,

First of all thanks for your reply. I'm not understanding you 100%, but
let's see if I'm right:

- An ASP.NET project is an application and not just a couple of webpages.
By
making a virtual directory for a project IIS knows that hat virtual
directory is an application. So every project needs an own virtual

directory
to run, you cannot have multiple projects in 1 virtual directory since

every
virtual directory represents an application.

- Frontpage server extensions can automaticly create a virtual directory

on
a remote server so that a ASP.NET can directly be run.

So this would conclude that when you only have FTP access to a webserver

it
isn't posible the deploy ASP.NET projects?

greets,

Gerben.

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:eZ******** ********@TK2MSF TNGP11.phx.gbl. ..
Let me see if I can help you to understand these entities better. An

ASP.Net
web application is an executable application. Therefore, it must run under some process. This process is defined by the web server configuration of an
"applicatio n". Because it is a .Net application, directly under the
root folder of the web server application, there must be a bin folder where the DLLs can be located. Location is almost everything in .Net. The web.config file containing the "Machine to application" settings for the app must
reside in the root folder of the application. The various ASPX pages and other files can be located anywhere at or under the root folder of the
application. However, this has nothing whatsoever to do with FrontPage
server extensions. Those are used by Visual Studio.Net for working with the
web server, getting documents, setting up a Web Application, etc. They are completely unnecessary at run-time.

It is therefore possible to FTP your files to the web server, or to
put
them
where they belong in any way you like. Setting up the web application
in IIS
is something which must be done by the network admin of the web
server.
--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news4.tilbu1 .nb.home.nl...
> Hi there, hope someone can help me on this:
>
> I'm planning to deploy several ASP.NET projects to a production

server. > Normally I used the "Project / Copy project" option in VS.NET, but

to this
> production server I only have FTP access. I tried copying the files with
a
> FTP tool, but it seems that every application needs to have an own

virtual
> directory, is this true? Or is it possible to just make 1 virtual
directory
> and put al the projects in there?
>
> So is there a possibility to deploy with ftp access only, or do I

need to
> ask the system administrator to set up frontpage server extensions?
>
> Greets,
>
> Gerben.
>
>



Nov 18 '05 #5
Actually, Gerben, ASP required an IIS Application as well, and "execute
scripts" permission.. ;-)

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news4.tilbu1 .nb.home.nl...
Hi again kevin,

Yeah ok, when the virtual directory is already setup it is posible to deploy with FTP. I will ask the server administrator to setup frontpage server
extensions then. I suppose creating virtual directory's isn't an exciting
task for a server administrator :). Kinda unhandy deploying asp.net compared to asp where you could just drop the files anywhere you want.

Thanks again for your help Kevin.

Greets,

Gerben.

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:u1******** ******@TK2MSFTN GP10.phx.gbl...
Hi Gerben,

You are nearly 100% correct, and in fact, I may just be misunderstandin g
your last remark, and you may be 100% correct. It is certainly possible to
deploy ASP.Net projects using only FTP, as long as the web site is already configured as an application.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news3.tilbu1 .nb.home.nl...
Hi Kevin,

First of all thanks for your reply. I'm not understanding you 100%, but let's see if I'm right:

- An ASP.NET project is an application and not just a couple of webpages.
By
making a virtual directory for a project IIS knows that hat virtual
directory is an application. So every project needs an own virtual directory
to run, you cannot have multiple projects in 1 virtual directory since

every
virtual directory represents an application.

- Frontpage server extensions can automaticly create a virtual directory on
a remote server so that a ASP.NET can directly be run.

So this would conclude that when you only have FTP access to a
webserver it
isn't posible the deploy ASP.NET projects?

greets,

Gerben.

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:eZ******** ********@TK2MSF TNGP11.phx.gbl. ..
> Let me see if I can help you to understand these entities better. An
ASP.Net
> web application is an executable application. Therefore, it must run

under
> some process. This process is defined by the web server
configuration of an
> "applicatio n". Because it is a .Net application, directly under the root > folder of the web server application, there must be a bin folder
where the
> DLLs can be located. Location is almost everything in .Net. The web.config
> file containing the "Machine to application" settings for the app
must > reside in the root folder of the application. The various ASPX pages

and > other files can be located anywhere at or under the root folder of the > application. However, this has nothing whatsoever to do with FrontPage > server extensions. Those are used by Visual Studio.Net for working with the
> web server, getting documents, setting up a Web Application, etc. They are
> completely unnecessary at run-time.
>
> It is therefore possible to FTP your files to the web server, or to put them
> where they belong in any way you like. Setting up the web
application in IIS
> is something which must be done by the network admin of the web server. >
> --
> HTH,
> Kevin Spencer
> .Net Developer
> Microsoft MVP
> Big things are made up
> of lots of little things.
>
> "Gerben van Loon" <no************ *@home.nl> wrote in message
> news:bu******** **@news4.tilbu1 .nb.home.nl...
> > Hi there, hope someone can help me on this:
> >
> > I'm planning to deploy several ASP.NET projects to a production

server.
> > Normally I used the "Project / Copy project" option in VS.NET, but to this
> > production server I only have FTP access. I tried copying the
files
with
a
> > FTP tool, but it seems that every application needs to have an own
virtual
> > directory, is this true? Or is it possible to just make 1 virtual
> directory
> > and put al the projects in there?
> >
> > So is there a possibility to deploy with ftp access only, or do I

need to
> > ask the system administrator to set up frontpage server

extensions? > >
> > Greets,
> >
> > Gerben.
> >
> >
>
>



Nov 18 '05 #6
hmm....?

But I never made a virtual directory for an asp application. Just made a new
map in the inetpub/wwwroot and dropped my scripts in there. Always worked
fine, no messing arround with virtual directory's.... .

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..
Actually, Gerben, ASP required an IIS Application as well, and "execute
scripts" permission.. ;-)

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news4.tilbu1 .nb.home.nl...
Hi again kevin,

Yeah ok, when the virtual directory is already setup it is posible to deploy
with FTP. I will ask the server administrator to setup frontpage server
extensions then. I suppose creating virtual directory's isn't an exciting
task for a server administrator :). Kinda unhandy deploying asp.net

compared
to asp where you could just drop the files anywhere you want.

Thanks again for your help Kevin.

Greets,

Gerben.

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:u1******** ******@TK2MSFTN GP10.phx.gbl...
Hi Gerben,

You are nearly 100% correct, and in fact, I may just be misunderstandin g your last remark, and you may be 100% correct. It is certainly possible to deploy ASP.Net projects using only FTP, as long as the web site is already configured as an application.

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news3.tilbu1 .nb.home.nl...
> Hi Kevin,
>
> First of all thanks for your reply. I'm not understanding you 100%, but > let's see if I'm right:
>
> - An ASP.NET project is an application and not just a couple of

webpages.
By
> making a virtual directory for a project IIS knows that hat virtual
> directory is an application. So every project needs an own virtual
directory
> to run, you cannot have multiple projects in 1 virtual directory
since every
> virtual directory represents an application.
>
> - Frontpage server extensions can automaticly create a virtual directory on
> a remote server so that a ASP.NET can directly be run.
>
> So this would conclude that when you only have FTP access to a webserver it
> isn't posible the deploy ASP.NET projects?
>
> greets,
>
> Gerben.
>
> "Kevin Spencer" <ke***@takempis .com> wrote in message
> news:eZ******** ********@TK2MSF TNGP11.phx.gbl. ..
> > Let me see if I can help you to understand these entities better. An > ASP.Net
> > web application is an executable application. Therefore, it must run under
> > some process. This process is defined by the web server configuration
of
> an
> > "applicatio n". Because it is a .Net application, directly under the root
> > folder of the web server application, there must be a bin folder where the
> > DLLs can be located. Location is almost everything in .Net. The
web.config
> > file containing the "Machine to application" settings for the app must > > reside in the root folder of the application. The various ASPX
pages and
> > other files can be located anywhere at or under the root folder of the > > application. However, this has nothing whatsoever to do with FrontPage > > server extensions. Those are used by Visual Studio.Net for working

with
> the
> > web server, getting documents, setting up a Web Application, etc. They are
> > completely unnecessary at run-time.
> >
> > It is therefore possible to FTP your files to the web server, or
to put
> them
> > where they belong in any way you like. Setting up the web application
in
> IIS
> > is something which must be done by the network admin of the web

server.
> >
> > --
> > HTH,
> > Kevin Spencer
> > .Net Developer
> > Microsoft MVP
> > Big things are made up
> > of lots of little things.
> >
> > "Gerben van Loon" <no************ *@home.nl> wrote in message
> > news:bu******** **@news4.tilbu1 .nb.home.nl...
> > > Hi there, hope someone can help me on this:
> > >
> > > I'm planning to deploy several ASP.NET projects to a production
server.
> > > Normally I used the "Project / Copy project" option in VS.NET,

but to
> this
> > > production server I only have FTP access. I tried copying the files with
> a
> > > FTP tool, but it seems that every application needs to have an
own > virtual
> > > directory, is this true? Or is it possible to just make 1 virtual > > directory
> > > and put al the projects in there?
> > >
> > > So is there a possibility to deploy with ftp access only, or do

I need
> to
> > > ask the system administrator to set up frontpage server

extensions? > > >
> > > Greets,
> > >
> > > Gerben.
> > >
> > >
> >
> >
>
>



Nov 18 '05 #7
There seems to be some confusion as to what an "applicatio n" is. In web
server lingo the word application defines an execution context and often a
machine process. An application is defined by a folder hierarchy, with all
files under the application folder/subfolders belonging to that application.
The "main" IIS application is set up under inetpub\wwwroot . If you drop in
files under that folder (or subfolders) then you run in the main application
context, and you will share the Application object with all other pages in
that context.

Most non-trivial applications are set up as isolated applications and thus
require a special IIS designation (virtual directory). This is not
mandatory, however. Nor is it mandatory, I believe, in asp.net.

There is no mapping between IIS applications and .NET projects. A single
application may be spread over multiple folders each consisting of one or
more projects (solutions). If you want to drop your application that way
under wwwroot then I believe you'd be fine, although I'm not sure this is
the best way to go. Perhaps better to define a (single!) virtual directory
in IIS and dump it all in there. The crucial point is you don't need a
separate application for each folder/project.

Eran

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news3.tilbu1 .nb.home.nl...
hmm....?

But I never made a virtual directory for an asp application. Just made a new map in the inetpub/wwwroot and dropped my scripts in there. Always worked
fine, no messing arround with virtual directory's.... .

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..
Actually, Gerben, ASP required an IIS Application as well, and "execute
scripts" permission.. ;-)

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news4.tilbu1 .nb.home.nl...
Hi again kevin,

Yeah ok, when the virtual directory is already setup it is posible to deploy
with FTP. I will ask the server administrator to setup frontpage server extensions then. I suppose creating virtual directory's isn't an exciting task for a server administrator :). Kinda unhandy deploying asp.net

compared
to asp where you could just drop the files anywhere you want.

Thanks again for your help Kevin.

Greets,

Gerben.

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:u1******** ******@TK2MSFTN GP10.phx.gbl...
> Hi Gerben,
>
> You are nearly 100% correct, and in fact, I may just be misunderstandin g > your last remark, and you may be 100% correct. It is certainly possible
to
> deploy ASP.Net projects using only FTP, as long as the web site is

already
> configured as an application.
>
> --
> HTH,
> Kevin Spencer
> .Net Developer
> Microsoft MVP
> Big things are made up
> of lots of little things.
>
> "Gerben van Loon" <no************ *@home.nl> wrote in message
> news:bu******** **@news3.tilbu1 .nb.home.nl...
> > Hi Kevin,
> >
> > First of all thanks for your reply. I'm not understanding you 100%,
but
> > let's see if I'm right:
> >
> > - An ASP.NET project is an application and not just a couple of
webpages.
> By
> > making a virtual directory for a project IIS knows that hat
virtual > > directory is an application. So every project needs an own virtual
> directory
> > to run, you cannot have multiple projects in 1 virtual directory

since > every
> > virtual directory represents an application.
> >
> > - Frontpage server extensions can automaticly create a virtual

directory
> on
> > a remote server so that a ASP.NET can directly be run.
> >
> > So this would conclude that when you only have FTP access to a

webserver
> it
> > isn't posible the deploy ASP.NET projects?
> >
> > greets,
> >
> > Gerben.
> >
> > "Kevin Spencer" <ke***@takempis .com> wrote in message
> > news:eZ******** ********@TK2MSF TNGP11.phx.gbl. ..
> > > Let me see if I can help you to understand these entities better. An
> > ASP.Net
> > > web application is an executable application. Therefore, it must run > under
> > > some process. This process is defined by the web server configuration
of
> > an
> > > "applicatio n". Because it is a .Net application, directly under the root
> > > folder of the web server application, there must be a bin folder

where
> the
> > > DLLs can be located. Location is almost everything in .Net. The
> web.config
> > > file containing the "Machine to application" settings for the
app must
> > > reside in the root folder of the application. The various ASPX pages and
> > > other files can be located anywhere at or under the root folder
of the
> > > application. However, this has nothing whatsoever to do with

FrontPage
> > > server extensions. Those are used by Visual Studio.Net for
working with
> > the
> > > web server, getting documents, setting up a Web Application, etc. They
> are
> > > completely unnecessary at run-time.
> > >
> > > It is therefore possible to FTP your files to the web server, or

to put
> > them
> > > where they belong in any way you like. Setting up the web

application
in
> > IIS
> > > is something which must be done by the network admin of the web
server.
> > >
> > > --
> > > HTH,
> > > Kevin Spencer
> > > .Net Developer
> > > Microsoft MVP
> > > Big things are made up
> > > of lots of little things.
> > >
> > > "Gerben van Loon" <no************ *@home.nl> wrote in message
> > > news:bu******** **@news4.tilbu1 .nb.home.nl...
> > > > Hi there, hope someone can help me on this:
> > > >
> > > > I'm planning to deploy several ASP.NET projects to a
production > server.
> > > > Normally I used the "Project / Copy project" option in VS.NET,

but to
> > this
> > > > production server I only have FTP access. I tried copying the

files
> with
> > a
> > > > FTP tool, but it seems that every application needs to have an own > > virtual
> > > > directory, is this true? Or is it possible to just make 1 virtual > > > directory
> > > > and put al the projects in there?
> > > >
> > > > So is there a possibility to deploy with ftp access only, or
do I need
> > to
> > > > ask the system administrator to set up frontpage server

extensions?
> > > >
> > > > Greets,
> > > >
> > > > Gerben.
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Nov 18 '05 #8
Thank you for your reply Eran,

The theory is now clear to me, but in practice it isn't working. Let me use
an example to be more specific:

I have 2 VS.NET projects which I made on my development machine, let's say
Project1 and Project2. On my develop machine they both reside in the wwwroot
of IIS. These project each have an own virtual directory since VS.NET makes
a new application for every project.

Now I like to deploy these projects to my production server. I could drop
them in the wwwroot of the production server, but I want an own application
(1) for these 2 applications. So let's make 1 virtual dir in the wwwroot of
the production server, let's say "MyProjects ". Then I copy the contents of
the Project1 and the Project2 map to this MyProject map on the production
server.

When I surf to the application the form is displayed, but no controls are
displayed. I'm only seeing some labels, the buttons which are on the page
disappeared.

Tried the same trick on my local machine, so made a new virt dir in the www
root named "MyProjects " and also copied the folders Project1 and Project2 in
there. But then I'm also getting some errors. Project2 has got a web.config
file and project1 doesn't.

http://members.home.nl/gerbenvl/Project1_error.gif
http://members.home.nl/gerbenvl/Project2_error.gif

Hope someone can help, thanks in advance.

Greets,

Gerben van Loon

"Eran Amitai" <er********@hot mail.com> wrote in message
news:ed******** *****@TK2MSFTNG P12.phx.gbl...
There seems to be some confusion as to what an "applicatio n" is. In web
server lingo the word application defines an execution context and often a
machine process. An application is defined by a folder hierarchy, with all
files under the application folder/subfolders belonging to that application. The "main" IIS application is set up under inetpub\wwwroot . If you drop in
files under that folder (or subfolders) then you run in the main application context, and you will share the Application object with all other pages in
that context.

Most non-trivial applications are set up as isolated applications and thus
require a special IIS designation (virtual directory). This is not
mandatory, however. Nor is it mandatory, I believe, in asp.net.

There is no mapping between IIS applications and .NET projects. A single
application may be spread over multiple folders each consisting of one or
more projects (solutions). If you want to drop your application that way
under wwwroot then I believe you'd be fine, although I'm not sure this is
the best way to go. Perhaps better to define a (single!) virtual directory
in IIS and dump it all in there. The crucial point is you don't need a
separate application for each folder/project.

Eran

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news3.tilbu1 .nb.home.nl...
hmm....?

But I never made a virtual directory for an asp application. Just made a new
map in the inetpub/wwwroot and dropped my scripts in there. Always worked
fine, no messing arround with virtual directory's.... .

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..
Actually, Gerben, ASP required an IIS Application as well, and "execute scripts" permission.. ;-)

--
HTH,
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news4.tilbu1 .nb.home.nl...
> Hi again kevin,
>
> Yeah ok, when the virtual directory is already setup it is posible to deploy
> with FTP. I will ask the server administrator to setup frontpage server > extensions then. I suppose creating virtual directory's isn't an

exciting
> task for a server administrator :). Kinda unhandy deploying asp.net
compared
> to asp where you could just drop the files anywhere you want.
>
> Thanks again for your help Kevin.
>
> Greets,
>
> Gerben.
>
> "Kevin Spencer" <ke***@takempis .com> wrote in message
> news:u1******** ******@TK2MSFTN GP10.phx.gbl...
> > Hi Gerben,
> >
> > You are nearly 100% correct, and in fact, I may just be

misunderstandin g
> > your last remark, and you may be 100% correct. It is certainly

possible
to
> > deploy ASP.Net projects using only FTP, as long as the web site is
already
> > configured as an application.
> >
> > --
> > HTH,
> > Kevin Spencer
> > .Net Developer
> > Microsoft MVP
> > Big things are made up
> > of lots of little things.
> >
> > "Gerben van Loon" <no************ *@home.nl> wrote in message
> > news:bu******** **@news3.tilbu1 .nb.home.nl...
> > > Hi Kevin,
> > >
> > > First of all thanks for your reply. I'm not understanding you 100%, but
> > > let's see if I'm right:
> > >
> > > - An ASP.NET project is an application and not just a couple of
> webpages.
> > By
> > > making a virtual directory for a project IIS knows that hat virtual > > > directory is an application. So every project needs an own virtual > > directory
> > > to run, you cannot have multiple projects in 1 virtual directory

since
> > every
> > > virtual directory represents an application.
> > >
> > > - Frontpage server extensions can automaticly create a virtual
directory
> > on
> > > a remote server so that a ASP.NET can directly be run.
> > >
> > > So this would conclude that when you only have FTP access to a
webserver
> > it
> > > isn't posible the deploy ASP.NET projects?
> > >
> > > greets,
> > >
> > > Gerben.
> > >
> > > "Kevin Spencer" <ke***@takempis .com> wrote in message
> > > news:eZ******** ********@TK2MSF TNGP11.phx.gbl. ..
> > > > Let me see if I can help you to understand these entities better.
An
> > > ASP.Net
> > > > web application is an executable application. Therefore, it must run
> > under
> > > > some process. This process is defined by the web server
configuration
> of
> > > an
> > > > "applicatio n". Because it is a .Net application, directly
under the
> root
> > > > folder of the web server application, there must be a bin
folder where
> > the
> > > > DLLs can be located. Location is almost everything in .Net. The > > web.config
> > > > file containing the "Machine to application" settings for the

app must
> > > > reside in the root folder of the application. The various ASPX

pages
> and
> > > > other files can be located anywhere at or under the root folder of
the
> > > > application. However, this has nothing whatsoever to do with
FrontPage
> > > > server extensions. Those are used by Visual Studio.Net for working > with
> > > the
> > > > web server, getting documents, setting up a Web Application, etc. They
> > are
> > > > completely unnecessary at run-time.
> > > >
> > > > It is therefore possible to FTP your files to the web server,
or to
> put
> > > them
> > > > where they belong in any way you like. Setting up the web
application
> in
> > > IIS
> > > > is something which must be done by the network admin of the
web > server.
> > > >
> > > > --
> > > > HTH,
> > > > Kevin Spencer
> > > > .Net Developer
> > > > Microsoft MVP
> > > > Big things are made up
> > > > of lots of little things.
> > > >
> > > > "Gerben van Loon" <no************ *@home.nl> wrote in message
> > > > news:bu******** **@news4.tilbu1 .nb.home.nl...
> > > > > Hi there, hope someone can help me on this:
> > > > >
> > > > > I'm planning to deploy several ASP.NET projects to a

production > > server.
> > > > > Normally I used the "Project / Copy project" option in VS.NET, but
> to
> > > this
> > > > > production server I only have FTP access. I tried copying
the files
> > with
> > > a
> > > > > FTP tool, but it seems that every application needs to have

an own
> > > virtual
> > > > > directory, is this true? Or is it possible to just make 1

virtual
> > > > directory
> > > > > and put al the projects in there?
> > > > >
> > > > > So is there a possibility to deploy with ftp access only, or

do
I
> need
> > > to
> > > > > ask the system administrator to set up frontpage server
extensions?
> > > > >
> > > > > Greets,
> > > > >
> > > > > Gerben.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>




Nov 18 '05 #9
Gerben,

I am not an expert on how to set up an aspx application under IIS and I hope
I'm not misleading you in the specifics. It seems you can have multiple
web.config files in different folders of the same application but some
settings are only applicable at the root level of the application. I'm not
sure why you need the config file to begin with but you can probably modify
the files to get it right. (Perhaps as a first step just move the config
file to your application's root.

If I understand your setup correctly, you set up a virtual directory under
wwwroot. This folder is empty, except for two subfolders - project1 and
project2, to which you copied the application files. First, note that each
of the subfolders has to have a bin subfolder with the compiled executables.
I suspect the absence of this folder is what caused the proj1 failure.

Another option is the virtual directory is not set up properly. I would try
setting it to someplace other than wwwroot. Set up a folder directly under
c:\ and create a virtual directory pointing there. By putting there a simple
html file and accessing it correctly from a browser you know for sure the
virtual directory is set up properly. Then you know you are not confused
with the main application.

Hope this helps,
Eran

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news4.tilbu1 .nb.home.nl...
Thank you for your reply Eran,

The theory is now clear to me, but in practice it isn't working. Let me use an example to be more specific:

I have 2 VS.NET projects which I made on my development machine, let's say
Project1 and Project2. On my develop machine they both reside in the wwwroot of IIS. These project each have an own virtual directory since VS.NET makes a new application for every project.

Now I like to deploy these projects to my production server. I could drop
them in the wwwroot of the production server, but I want an own application (1) for these 2 applications. So let's make 1 virtual dir in the wwwroot of the production server, let's say "MyProjects ". Then I copy the contents of
the Project1 and the Project2 map to this MyProject map on the production
server.

When I surf to the application the form is displayed, but no controls are
displayed. I'm only seeing some labels, the buttons which are on the page
disappeared.

Tried the same trick on my local machine, so made a new virt dir in the www root named "MyProjects " and also copied the folders Project1 and Project2 in there. But then I'm also getting some errors. Project2 has got a web.config file and project1 doesn't.

http://members.home.nl/gerbenvl/Project1_error.gif
http://members.home.nl/gerbenvl/Project2_error.gif

Hope someone can help, thanks in advance.

Greets,

Gerben van Loon

"Eran Amitai" <er********@hot mail.com> wrote in message
news:ed******** *****@TK2MSFTNG P12.phx.gbl...
There seems to be some confusion as to what an "applicatio n" is. In web
server lingo the word application defines an execution context and often a
machine process. An application is defined by a folder hierarchy, with all files under the application folder/subfolders belonging to that application.
The "main" IIS application is set up under inetpub\wwwroot . If you drop in files under that folder (or subfolders) then you run in the main

application
context, and you will share the Application object with all other pages in that context.

Most non-trivial applications are set up as isolated applications and thus require a special IIS designation (virtual directory). This is not
mandatory, however. Nor is it mandatory, I believe, in asp.net.

There is no mapping between IIS applications and .NET projects. A single
application may be spread over multiple folders each consisting of one or more projects (solutions). If you want to drop your application that way
under wwwroot then I believe you'd be fine, although I'm not sure this is the best way to go. Perhaps better to define a (single!) virtual directory in IIS and dump it all in there. The crucial point is you don't need a
separate application for each folder/project.

Eran

"Gerben van Loon" <no************ *@home.nl> wrote in message
news:bu******** **@news3.tilbu1 .nb.home.nl...
hmm....?

But I never made a virtual directory for an asp application. Just made a
new
map in the inetpub/wwwroot and dropped my scripts in there. Always worked fine, no messing arround with virtual directory's.... .

"Kevin Spencer" <ke***@takempis .com> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..
> Actually, Gerben, ASP required an IIS Application as well, and "execute > scripts" permission.. ;-)
>
> --
> HTH,
> Kevin Spencer
> .Net Developer
> Microsoft MVP
> Big things are made up
> of lots of little things.
>
> "Gerben van Loon" <no************ *@home.nl> wrote in message
> news:bu******** **@news4.tilbu1 .nb.home.nl...
> > Hi again kevin,
> >
> > Yeah ok, when the virtual directory is already setup it is posible to > deploy
> > with FTP. I will ask the server administrator to setup frontpage

server
> > extensions then. I suppose creating virtual directory's isn't an
exciting
> > task for a server administrator :). Kinda unhandy deploying
asp.net > compared
> > to asp where you could just drop the files anywhere you want.
> >
> > Thanks again for your help Kevin.
> >
> > Greets,
> >
> > Gerben.
> >
> > "Kevin Spencer" <ke***@takempis .com> wrote in message
> > news:u1******** ******@TK2MSFTN GP10.phx.gbl...
> > > Hi Gerben,
> > >
> > > You are nearly 100% correct, and in fact, I may just be
misunderstandin g
> > > your last remark, and you may be 100% correct. It is certainly
possible
> to
> > > deploy ASP.Net projects using only FTP, as long as the web site is > already
> > > configured as an application.
> > >
> > > --
> > > HTH,
> > > Kevin Spencer
> > > .Net Developer
> > > Microsoft MVP
> > > Big things are made up
> > > of lots of little things.
> > >
> > > "Gerben van Loon" <no************ *@home.nl> wrote in message
> > > news:bu******** **@news3.tilbu1 .nb.home.nl...
> > > > Hi Kevin,
> > > >
> > > > First of all thanks for your reply. I'm not understanding you

100%,
> but
> > > > let's see if I'm right:
> > > >
> > > > - An ASP.NET project is an application and not just a couple of > > webpages.
> > > By
> > > > making a virtual directory for a project IIS knows that hat

virtual
> > > > directory is an application. So every project needs an own

virtual > > > directory
> > > > to run, you cannot have multiple projects in 1 virtual directory since
> > > every
> > > > virtual directory represents an application.
> > > >
> > > > - Frontpage server extensions can automaticly create a virtual
> directory
> > > on
> > > > a remote server so that a ASP.NET can directly be run.
> > > >
> > > > So this would conclude that when you only have FTP access to a
> webserver
> > > it
> > > > isn't posible the deploy ASP.NET projects?
> > > >
> > > > greets,
> > > >
> > > > Gerben.
> > > >
> > > > "Kevin Spencer" <ke***@takempis .com> wrote in message
> > > > news:eZ******** ********@TK2MSF TNGP11.phx.gbl. ..
> > > > > Let me see if I can help you to understand these entities

better.
An
> > > > ASP.Net
> > > > > web application is an executable application. Therefore, it must run
> > > under
> > > > > some process. This process is defined by the web server
> configuration
> > of
> > > > an
> > > > > "applicatio n". Because it is a .Net application, directly under the
> > root
> > > > > folder of the web server application, there must be a bin folder > where
> > > the
> > > > > DLLs can be located. Location is almost everything in .Net. The > > > web.config
> > > > > file containing the "Machine to application" settings for the app
> must
> > > > > reside in the root folder of the application. The various
ASPX pages
> > and
> > > > > other files can be located anywhere at or under the root folder
of
> the
> > > > > application. However, this has nothing whatsoever to do with
> FrontPage
> > > > > server extensions. Those are used by Visual Studio.Net for

working
> > with
> > > > the
> > > > > web server, getting documents, setting up a Web Application,

etc.
> They
> > > are
> > > > > completely unnecessary at run-time.
> > > > >
> > > > > It is therefore possible to FTP your files to the web

server, or to
> > put
> > > > them
> > > > > where they belong in any way you like. Setting up the web
> application
> > in
> > > > IIS
> > > > > is something which must be done by the network admin of the web > > server.
> > > > >
> > > > > --
> > > > > HTH,
> > > > > Kevin Spencer
> > > > > .Net Developer
> > > > > Microsoft MVP
> > > > > Big things are made up
> > > > > of lots of little things.
> > > > >
> > > > > "Gerben van Loon" <no************ *@home.nl> wrote in message
> > > > > news:bu******** **@news4.tilbu1 .nb.home.nl...
> > > > > > Hi there, hope someone can help me on this:
> > > > > >
> > > > > > I'm planning to deploy several ASP.NET projects to a production
> > > server.
> > > > > > Normally I used the "Project / Copy project" option in VS.NET, but
> > to
> > > > this
> > > > > > production server I only have FTP access. I tried copying the > files
> > > with
> > > > a
> > > > > > FTP tool, but it seems that every application needs to
have an own
> > > > virtual
> > > > > > directory, is this true? Or is it possible to just make 1
virtual
> > > > > directory
> > > > > > and put al the projects in there?
> > > > > >
> > > > > > So is there a possibility to deploy with ftp access only,

or do
I
> > need
> > > > to
> > > > > > ask the system administrator to set up frontpage server
> extensions?
> > > > > >
> > > > > > Greets,
> > > > > >
> > > > > > Gerben.
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Nov 18 '05 #10

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
1501
by: D E | last post by:
I've created an app using SWING gui and awt. It originally was just a client app with some JDBC calls. How would I go about deploying it onto my website? I want to "show it off" I realize in real life, applets and SWING over the web spells security problems, but this is for a "portfolio" of various projects i've completed... thanks a lot...
2
6465
by: pieter.breed | last post by:
Hi All, The company I work for has traditionally used COM/ActiveX for the solutions that it provides. We are in the process of moving to .NET and a few applications have been written in VB.NET up to this point. Some of the applications are class libraries which need to be callable via the COM interface from some of the older applications. Could someone please explain to me the issues involved in deploying such a class library?
1
1737
by: dansan | last post by:
We have a webservice that we have been deploying using the deployment project in Visual Studio. Now we are trying to deploy this service to a server that has multiple sites. I have looked everywhere in the deployement project to see where I can allow the person installing to choose the root, but I can't find anything. Is there a way to install in a desired root using the deployment project? or is Visual Studio installer more of a...
1
2519
by: K Meyer | last post by:
Everything in the deployment works fine with the exception of the address of the database also deployed on the remote server. The string address is found under "oledbconnection" in the ".... .aspx.jsl" file. What should the string address look like on the remote computer? On my development machine the address is:
0
934
by: Kevin Banks | last post by:
I am engaged with a team that will be working on multiple concurrent releases if an asp.Net app. Historically, we have used SourceSafe for deploying code across our dev/test/prod environments, and have only redeployed those files that have changed. Because we already have processes in place to manage code using this model, I would like to know if there is a way to set up projects so that only code that has been updated can be deployed...
7
1723
by: Egghead | last post by:
Hi all, Is there a way to deploy a web application to a live server without using the windows installer (not following the "Walkthrough: Deploying a Web Solution" in the VS.net's help). The application contains C# classes, asp.net pages, and some third party's dll. Just that we are not that comfortable with VS.net's Setup and Deployment Projects. It messes up some COM object ver in our's desktop application. TIA Egghead
21
3854
by: Al Christoph | last post by:
I posted this last week end in the MSDN forums. No luck there. Let's see what the experts here have to say:-)))) I have a rather convoluted project. The distributable will come in eight different flavors, each with its main program, libraries, datafiles, doco, etc. Each flavor will also have one or more standalone executables that can be called as tools from within the main program.
3
2611
by: pooba53 | last post by:
I have a VB .NET 2003 application that communicates with an Access db. I am deploying the application using the Wizard that creates an install package and it IS properly grabbing the Access db and putting it in the Program Files directory along with the application executable, no problem. The problem is this... The OleDbConnection knows of the database in an absolute location (i.e. C:\Documents and Settings\ApplicationDB\data.mdb
11
7113
by: mjahabarsadiq | last post by:
Hi I have created a web application. I am using ant to build the war and deploy in tomcat. The war file is deployed under "TOMCATE_HOME/work/standalone/localhost/onlineres.war". I have my source files in "D:\Sadiq\Projects\Onlineres". The folder structure is as follows. 1) D:\Sadiq\Projects\Onlineres: This folder is having the context.xml, web.xml, build.xml and build.properties files.
0
8595
by: Hystou | last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it. First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
0
9142
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. Here is my compilation command: g++-12 -std=c++20 -Wnarrowing bit_field.cpp Here is the code in...
1
8875
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
0
8849
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
0
7699
agi2029
by: agi2029 | last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own.... Now, this would greatly impact the work of software developers. The idea...
0
5855
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert into image. Globals.ThisAddIn.Application.ActiveDocument.Select();...
0
4353
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
0
4608
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
3
1989
bsmnconsultancy
by: bsmnconsultancy | last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.