|
-
Sep 28th, 2004, 01:12 PM
#1
asp.net compile application?
In ASP.NET, you build the application into a DLL file. Is this how you are supposed to deploy the asp.net application to the webserver? in a single DLL file? or do you upload individual aspx pages?
I am having trouble just displaying a simple aspx page on my webserver (works on my local IIS no problem)
My webhost has .net 1.1 installed on IIS.
-
Sep 28th, 2004, 01:57 PM
#2
yay gay
You have to put both the .DLL and .ASPX
\m/  \m/
-
Sep 28th, 2004, 02:08 PM
#3
also my webhost has a control panel (pretty crappy one, but one all the same) and you can select directories and select "create application" under any directory. They said to try doing this if I cant get an ASP app to work... any ideas what this setting does on IIS when I "create application"
I know its hard to explain since you dont know what the control panel looks like
-
Sep 28th, 2004, 02:09 PM
#4
yay gay
Sorry, I never did anything related to ASP.NET
\m/  \m/
-
Sep 28th, 2004, 04:47 PM
#5
Frenzied Member
I've deployed asp.net applications two ways. 1 - use the package and deployment stuff and create a setup.msi and 2 - just copied my directory and subdirectories over, then create a virtual directory in IIS.
I've also (but just once) uploaded the .dll in the .bin folder, then tried to run the application, and kept on adding files when I got exceptions. You do need the web.config, .asmx files etc.
-
Sep 28th, 2004, 06:20 PM
#6
Originally posted by Mike Hildner
I've deployed asp.net applications two ways. 1 - use the package and deployment stuff and create a setup.msi and 2 - just copied my directory and subdirectories over, then create a virtual directory in IIS.
I've also (but just once) uploaded the .dll in the .bin folder, then tried to run the application, and kept on adding files when I got exceptions. You do need the web.config, .asmx files etc.
yeah right before i left work today I tried the last thing you said, I made a bin folder off the root of the app directory on my web space, and FTPed the DLL into the bin directory, and the aspx and web.config and all that into the app directory and it worked fine. We use a webhost, so I cant give them a setup.msi to run, and I dont have access to the virtual directory, I can only access it via FTP
-
Sep 28th, 2004, 07:33 PM
#7
Frenzied Member
I have an account at Brinkster.com and when I needed to deploy my proof of concept there, that's exactly what I had to do. Kind of a pain, but heck, if someone's hosting your stuff, what can you do? If it goes commercial, I'll have my own servers
-
Sep 28th, 2004, 11:47 PM
#8
Originally posted by kleinma
any ideas what this setting does on IIS when I "create application"
Creates a Virtual Directory.
-
Sep 29th, 2004, 08:11 AM
#9
Originally posted by mendhak
Creates a Virtual Directory.
even though the physical directory off my webroot is already created?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|