Rolling out an app to multiple web servers? (ASP.NET)

FinalBuilder Discussion
1

I am struggling with the best way to roll out my app (built with finalbuilder, of course) to multiple web servers ) IIS.

Suggestions?

 

Thanks!

 

Raf

 

2

(Caveat, this only works with asp.net 2.0 and later) The simplest way to do it is to just use the robocopy mirror action to copy the build to each server. The key to get this to working is app_offline.htm. If you copy a file with the name app_offline.htm into the root of the website. This will display the contents of that file no matter what you try to view on the site. If you don’t do this, you will likely run into file in use problems and other weirdness. Once the build is copied into place, delete the app_offline.htm. (Note you’ll want the app_offline.htm to also exist in the new build, otherwise the robocopy mirror will remove it prematurely.)

3

Hi Raf,

What exactly are you struggling with? Depending on the requirements of the application it can be as simple as xcopying the compiled web files to the servers and using the IIS actions to configure IIS, though that is quite a simplistic example. If you could provide more details we may be able to provide some more relevant suggestions.

Regards,
Paul.

4

We are struggling with the "overall approach" to updating code on multiple servers. We have reviewed....everything we can find. It looks like there are awesome tools for ruby devs, but not much for .NET (pls don't mention the MS tools.... non starters).

It appears what we really need is an RPC mechanism, whereby:

1) An FB script on the build system can signal server A, B, C, D, E "Build 123"

2) Those servers then start their own scripts to start the process of downloading "Build 123" and loading it up. (This means different things to different servers, as there are db servers, web servers, and app servers in this mix. Each server type has its own script.)

We want to leverage FB as much as possible. There does not seem to be a "powershell console terminal" so we are a tad hosed in that dept.

Any suggestions welcome!

5

Hi Sam

You could have FB on the servers, and use the PSExec action on your build machine to start FB on the servers… which then pull the files etc from the build machine (or where ever you put the files) and apply them as needed. A cheaper option would be to use Automise on the servers, as you don’t need the full FB functionality.

6

Thank you. That might be just the ticket. (PSExec is on my list, had not thought to integrate that with FB).

Will need to look at automize to see what IIS and sql management features it has.