Dealing with site-down time

Question

Hi..

Just wanted to check out if anyone can help me out.

Whenever I update my website (assuming any code-behind file or else), site appears after 10-20 seconds in browser.

I googled out lot but everyone says to update the .DLL file(s) on hosting server in bin directory, I'm confused here, where's that bin directory located? I'm using FileZilla to update my site but this is not showing that bin directory.

Please advice here...

(i) How I create that DLL file on development server?
(ii) How I find DLL file on development server?
(iii) How I find \bin directory on hosting server?

Thanks in Adv

Suthish Nair · Answer

update web config of server app: compilation debug=false

Abhimanyu K Vatsa · Answer

Mini & Suthish : both of you guys are right but I am just hosting a simple site so I'll prefer to Suthish here. Thank you guys

Suthish Nair · Answer

mani is right we too also using a balancing server for that. If one is down other is there. but it depends upon the organisation and how much they needed. increase website performances + asp.net

Manikavelu Velayutham · Answer

You can achieve Zeor down time using Twin Tower methodology. You should have two server with the same configuration. One should be active and the other should act as passive server. Consider you have the build version 2.0 in both the server. Now you are going to publish the next version 3.0 in the production. First you should update the passive server with 3.0 in the production. whereas the site wont be down since its point to the active server 2.0 version. once the updates completed in the passive server. just point out the production url to the passive server so that server becomes active now and the active server becomes passive now. Now you can sync the passive server with the version of 3.0 Your site is now Zero Down Time

Abhimanyu K Vatsa · Answer

@Suthish Now that's exactly the same I'm already using after rising this thread. At this time you are right! { ASP.NET code explicitly disables batch compilation when debug = true. That means that every page that gets hit creates its own dynamic assembly. These assemblies get scattered all over the address space and fragment memory. The result is that you dramatically increase the probability of an OOM exception. There are also other drawbacks such as the batch timeout value being ignored which can cause other problems down the chain. I think it's very bad idea to have debug=true on production server. } @Sam Yes we can use FileZilla to copy the site exactly as Visual Studio does. However VS is good but don't know why I am comfortable with FileZilla since my web-hosting life started.

Sam Hobbs · Answer

I am not as experienced with publishing web sites as the others are but I think you can't use FTP for an ASP site and I assume that FileZilla uses FTP. I think Visual Studio uses Front Page Extensions (although it might now be called something else). So Suthish and other members can help you better but I think you essentially need to use VS to publish the site. If it is possible to use FTP then it would help me to know how.

Manas Patnaik · Answer

Publish the Asp.Net app  and browse the folder you can find Bin folder. Regarding late display of changes make sure you have cleared browser cache .Also make sure to check with your server side cache settings

Abhimanyu K Vatsa · Answer

Thank you Suthish for quick reply I really appreciate this. I googled out all articles but no use. So I need some ideas here. Thanks

Suthish Nair · Answer

You need to publish the website and host it to server. Browser for articles How to Publish a Web Site.