Dedicated Server Shared Server

How to make a Timely event in ASP .Net?
Hello, How can I make a timely event in ASP .Net. I mean an event which should get fire at midnight 12:00 and also an event which can check some changes after firing itself after (let say) 20 Minutes. 2nd thing can be achieved using threading (and then thread sleep) but for this we must have a event which must reside in memory permanently. Application_Start is an event where we can write this. But as last client will be closed Application_End will get fired and will stop excution of Application_Start. Is there any way that Application_Start will stay in memory for ever? Finally i will be having dedicated Server. But currently me testing it at a Shared Server.. Thanks in Advance Regards,

there is a timer object you can drop onto your project (or create by hand) that you can let rip and it will check at periodic intervals.. a common control.

Setting up Intranet in an office?
I have to set up an intranet for a small business. We have two offices that are connected by a leased line. I need to set up an intranet that the offices can use to share a database. This database has to be on a dedicated server computer that can be updated by either office. This database has to be accessible by both offices via the intranet. We currently have an intranet set up with a web application that is very inefficient. I want to upgrade to a dedicated server to do this. Is there a way to do this? I also need the database to be accessible to both offices, the database editable by both offices. Hardware and software tips are much appreciated Thank you guys!

2 offices connected via a leased line. Can the computers from different offices see each other currently? If so, no problem at all. Just transfer whatever web application to your own new, intranet web server (use whatever you want to use, but Apache on Linux - if you know how to maintain it - is most cost effective). If they cannot see each other, then you'd need to configure NAT on your routers in both offices and assign appropriate IP addresses with the correct subnet masks so they can see each other. Once that is done, no problem. In this setup, your application could reside in a web server (your new dedicated machine that sits within your network) and so could your database. Offices just need to reconfigure whatever application to point to the database on the new IP address. Since you already have a leased line, I wouldn't go broadband especially if your bandwidth is considerably large enough (1-2Mb?). However if your offices tend to transfer huge music, video, or graphic files inter-office using the leased lines, then you should put a stop to it if its not work-related. If it is, consider forcing the users to use alternate forms for such transfer (inter-office email that uses an internet based mail server for example). Going broadband even with VPN, exposes your network to the public and it does bring up an entire new can of worms. You'd need to have the knowledge to manage that as well as knowledge on security and eventually as it grows, you end up with more and more things to monitor and control. Manual procedures will also have to be modified.. for example, what if a disgruntled employee who got fired cos he didn't turn up for work for a month decides to login remotely via VPN and sabotage your database? You'd need manual procedures to circumvent such things from happening and these are usually more difficult to implement due to the human factor.