•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the ASP.NET section within the Web Development category of DaniWeb, a massive community of 391,127 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 3,251 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our ASP.NET advertiser: Lunarpages ASP Web Hosting
Views: 872 | Replies: 1
![]() |
| |
•
•
Join Date: Jan 2006
Location: Its the internet... i am everywhere lol
Posts: 274
Reputation:
Rep Power: 3
Solved Threads: 10
It doesnt by default for a website in VS2005. you would just upload your aspx files to your webserver.
You can get it to compile to a dll and upload the dll if you want. It is more secure on the webserver but harder to maintain.
I usually keep my aspx files as they are (and the cs code behind files) on the webserver to make it easier to change. Most of the web stuff gets served up to the user anyway and they can view the source. It wouldnt take much to be able to work out your code. Also if they can get into your server to steal your aspx files then they can steal your dll, reverse engineer it in seconds and make any changes and upload it so it isnt any more secure.
We keep all our other more secure code in normal dlls and either host them on the same server or call them through other means which makes the code more secure and also the dlls themselves.
If you just want your site to run then you dont have to compile it to a dll just upload it to a webserver.
You can get it to compile to a dll and upload the dll if you want. It is more secure on the webserver but harder to maintain.
I usually keep my aspx files as they are (and the cs code behind files) on the webserver to make it easier to change. Most of the web stuff gets served up to the user anyway and they can view the source. It wouldnt take much to be able to work out your code. Also if they can get into your server to steal your aspx files then they can steal your dll, reverse engineer it in seconds and make any changes and upload it so it isnt any more secure.
We keep all our other more secure code in normal dlls and either host them on the same server or call them through other means which makes the code more secure and also the dlls themselves.
If you just want your site to run then you dont have to compile it to a dll just upload it to a webserver.
![]() |
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
•
•
•
•
•
•
•
•
DaniWeb ASP.NET Marketplace
- bad or missing system file (Windows NT / 2000 / XP / 2003)
- missing or corrupted file... (Troubleshooting Dead Machines)
- Missing Config file not allowing boot (Windows NT / 2000 / XP / 2003)
- BIG problem, cant find a missing (critical) file (Windows NT / 2000 / XP / 2003)
- Using x86 Assembly Language with Microsoft Visual C++ (C++)
- XP - "Invalid boot.ini file" (Windows NT / 2000 / XP / 2003)
Other Threads in the ASP.NET Forum
- Previous Thread: 404 Error on Postback
- Next Thread: Bind data to controls (SQL)


Hybrid Mode