I live and work in Sydney where I spend most of my days working with .Net developing all sorts of applications such as ASP.Net applications, Windows forms, MSMQ, Web Services, Enterprise services, windows services etc.
These days I don't have much time at home as we are very busy at work. We have spend the last few days getting our applications ready for deployment and because we now have to support multiple versions of our solutions we had to make quite a few changes to our code base as well as our MSI for deployment.
Our applications run in a standard web farm and we have a separate MSMQ Server with a couple of windows services running to support async. operations. To support parallel versions running on the same servers we are now creating a new web site for each release and go in via a new port on the server. Also because of a long and 'patchy' history of the development of the solutions most appsettings were located in the machine.config file. we are now moving these out to the different applications, but to minimise our work for our web applications and web services we have created a virtual root folder under which all our apps sit. So for each release we will have a new virtual root with new settings which will then cascade down to all the web apps and web services for each version of our solutions.
Unfortunately we haven't found any easy way for versioning of our windows services and we have to rename the service names to incorporate the version number in order for us to run multiple versions of the same windows service. Oh well. It's all getting there and we should be ready tomorrow with the last changes and the users can start testing.
I recently downloaded the new Vs.net 2005 Beta 2 that I now spend my nights trying out. Such as shame that Indigo and Avalon doesn't work with Beta 2 yet...can't be bothered going back to the CTP version of vs.net 2005. I had a few problems with that version as the items in the toolbox wouldn't show up till I removed a folder under my user in documents and settings.