How to Publish aspx pages without configuring an application?

  • Thread starter Thread starter Anil Gupte/iCinema.com
  • Start date Start date
A

Anil Gupte/iCinema.com

I seem to have read somewhere that one can do this by copying the
code-behind page into the .aspx file. Is there an easier way?

I tried to create a simple web page (I just need a quick registration page
that is temporary). Do I really need to logon to the server, create a
virtual directory and all that junk, just to publish my page? I tried
simply to publish using the FTP publish and here is what I got:
Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This error
can be caused by a virtual directory not being configured as an application
in IIS.

Source Error:

Line 49: ASP.NET to identify an incoming user.
Line 50: -->
Line 51: <authentication mode="Windows"/>
Line 52: <!--
Line 53: The <customErrors> section enables configuration


I am so used to years of ASP, where you can build an entire app in notepad,
publish it and you are up and running. Something simple like that would be
my favorite.

Any advice?
 
Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level.  This error
can be caused by a virtual directory not being configured as an application
in IIS.
Click to expand...

This error is most likely because you do not have the application in a
Virtual Directory in IIS. Unfortunately, the ASP.NET page must reside
in a Virtual Directory that is configured as an ASP.NET application
(make sure you set it to use 2.0 as that's most likely what you'll
need).

The other option is to drop it under an existing ASP.NET site if you
have one you can use (since it'll already be configured as a Virtual
Directory)

Thanks,

Seth Rowe [MVP]
 
Thanx, that is the bad news I was expecting. I often write some small apps
to do specific things and I had to create a virtual directoy for each, I
would be swimming in them. Perhaps I will try your suggestion of dropping
it into an existing application. Of course the automated FTP publishing
won't work then - I think I will have to make sure not to ftp the web.config
or perhaps use the automated approach and then delete the web.config.

If I do manually plop the files under an exiting app, do I have to tell it
that the original app that it has some new friends? Or will it compile
them. I guess I can just try it and see.

Thanx for your help.
--
Anil Gupte
www.keeninc.net
www.icinema.com
www.wizo.tv
rowe_newsgroups said:
Parser Error Message: It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This
error
can be caused by a virtual directory not being configured as an
application
in IIS.
Click to expand...

This error is most likely because you do not have the application in a
Virtual Directory in IIS. Unfortunately, the ASP.NET page must reside
in a Virtual Directory that is configured as an ASP.NET application
(make sure you set it to use 2.0 as that's most likely what you'll
need).

The other option is to drop it under an existing ASP.NET site if you
have one you can use (since it'll already be configured as a Virtual
Directory)

Thanks,

Seth Rowe [MVP]
 
Thanx, that is the bad news I was expecting.  I often write some small apps
to do specific things and I had to create a virtual directoy for each, I
would be swimming in them.  Perhaps I will try your suggestion of dropping
it into an existing application.  Of course the automated FTP publishing
won't work then - I think I will have to make sure not to ftp the web.config
or perhaps use the automated approach and then delete the web.config.

If I do manually plop the files under an exiting app, do I have to tell it
that the original app that it has some new friends?  Or will it compile
them.  I guess I can just try it and see.

Thanx for your help.
--



This error is most likely because you do not have the application in a
Virtual Directory in IIS. Unfortunately, the ASP.NET page must reside
in a Virtual Directory that is configured as an ASP.NET application
(make sure you set it to use 2.0 as that's most likely what you'll
need).

The other option is to drop it under an existing ASP.NET site if you
have one you can use (since it'll already be configured as a Virtual
Directory)

Thanks,

Seth Rowe [MVP]
Click to expand...

Yeah, try it and see, it sorta depends on how the application is set
up. Also remember that web.configs are inherited, so if you drop your
stuff in a sub folder you can add in some pieces just for the new page
in a web.config that lives in that subfolder.

Thanks,

Seth Rowe [MVP]
 
Back
Top