Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

deploying ASP application 1

Status
Not open for further replies.

skitty123

Technical User
May 4, 2004
56
US
I have a small ASP .NET application that is in development on an XP system, uses a sql server 2000 database on the same machine.
Concurrent users will proabably be 5-6 as it will be an intarnet appication only
Management wants to keep the application on the same system instead of putting on a server and deploying it. I was wondering if there are any issues to keeping it on an XP operating system vs a server given the small number of users.
 
It should be fine. Some of the advantages to using a server include Active Directory, the ability to handle more users and processes, and better security.

That being said, Win XP Pro is a pretty good operating system and it is fairly secure. I run a website off of a Win XP Pro machine at my house and don't have any problems. Your security issues should be minimized by the fact that you are on an intranet. Since you said that it is a small application, I don't think you will be authenticating users through Active Directory, so that is okay. And, with less than 10 users, your setup sounds good to me.

For what it is worth, you have my blessing to go forth.
 
Thanks Guru7777, one more question:
I set up the virtual directory on IIS so that now other users can browse to the application and it all seems to be working ok.

Do I need to run the setup.exe ( created useing Visual studio .net to "deploy" the application) It proabbnly sounds like a stupid question, since I already have the source code on this machine, but I was wondering if the "deployment" has any performance benefits as its supposed to install compiled Dlls?
 
I guess my question is this: if I leave the current set up is thecode getting compiled each time someone navigates to the site? or once i compile it in my editor, that is the version being used untill i compile it again.

(I asked this question on another forum as well as its not just an ASP question, but C#/ .net as well so you might see it in 2 places.)
 
<snip>
or once i compile it in my editor, that is the version being used untill i compile it again
</snip>

That is a true statement.

The code behind is only compiled once for each iteration of the project. Your .aspx page is never compliled. It is rendered by the server each time that it is viewed. This would happen no matter what operating system that you were using.
 
Thanks so much!!!
This is the first time i am doing this so I was not sure,
I realise now I could have tested it by making a change and not compileing it and trying to access the site to see if the change came through. :)

I have heard that when hosting a site from an XP pro OS the number of concurrent users is 10 -- is this correct? where might I find more info on this? Is this a limit that is set in the IIS on this OS or something else?
 
1. dont know if you did this: i would create 2 virtual directories: one for you to fiddle in as a developer and one for the users. I would never let users access the development environment especially when its up and running an you want to fix things at the same time. You dont have to create a setup project just x-copy the needed files ( .dll/web.config/.aspx/ etc...)

2. aspx pages are indeed not in your "compiled" assemblies but they are also not just "rendered", they are "compiled" real time, just turn on the trace to see, read this and this[/this] for more compiling and pre-compile stuff.

quote : "ASP.NET web applications only keep running for as long as there are some active sessions -- then they shut down until there is another page request. This means that if your site isn't always getting hits, then it will stop, and later requests will have to endure the slow startup and recompilation. It also means that you cannot ever expect your ASP.NET web applications to periodically perform a background task, since it may not be running. "

This may be in your case as you have a little number of users. You can just include his .dll in your project and it will be very much faster at "every" user starting the application.


--------------------------------------
deleau@gmail.com
[URL unfurl="true"]http://de-leau.eigenstart.nl
 
I have heard that when hosting a site from an XP pro OS the number of concurrent users is 10 -- is this correct? where might I find more info on this? Is this a limit that is set in the IIS on this OS or something else?

Correct. It is enforced at the OS level & is the same for Win2K Pro. I am fairly confident Win2K Pro & XP Pro could support more users, but Microsoft make more money selling Server products... ;)

James Goodman MCSE, MCDBA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top