A friend of mine, that I’ll keep anonymous, asked me to help her with an ASP page that didn’t work. The changes she made wasn’t visible when she ran the script on the server. I got most of it running on my local machine and thought there should be no problem running it on the production server. A couple of hours later the ASP file contained nothing but plain HTML and it still wasn’t working.
I’ve been involved in a couple of projects where SourceSafe was kicked out. In most cases there were long discussions on how to handle the history in SourceSafe. Most developers seems to manage without migrating the history, but there has always been a vocal minority that desperately want to have the history migrated.
When dealing with this it has struck me that every project that was in favor of migrating the history also was missing decent release practices.
I’m reading Pro BizTalk 2006by Apress and a section in the chapter about setting up a new BizTalk project made me a little upset.
The author thinks it is a disadvantage that: ‘A formal build-and-deploy process becomes essential.‘
WTF; in an organization big enough to think about, and afford, BizTalk I would say that a formal build-and-deploy process is a prerequisite. Since BizTalk is a lot, if not all, about integrating different systems and organizations having a strict configuration management is essential to keep the cost down and the quality up.
I’ve got the old PC up and running again. It was no easy quest to find a matching motherboard for an ancient computer. I ended up buying a used board. The current plan is to run it as a file- and svn-server mainly, but I had to keep running XP so the kids can do their stuff on it. I will probably have the svn repository on the system disk and back it up daily to the other disk.
I’m using OpenSVN to manage the source code to some of my projects, but it has been down for a couple of days now. That is a real pain. IT is (was) a free service so have expected that it would shut down eventually.
I don’t have a computer that I can run SVN on. I do all my programming on the same machine so I could possibly run SVN or (evil thought) SourceSafe on that and use Diino for external backup.
Make sure your automatic, daily and continuous, build actually works.
It is just like checking that your backup procedures actually works. You do not want to find out either one of those is not working when you really need them.
This weekend our Team Foundation Server was moved and everything looked all right on Monday morning. There was no problem at all to connect to the new server and the Cruise Control Tray icon was a comforting green.
Lots of times I have been involved in lengthy discussions about how to solve a problem and trying to guess what the user really wanted based on his initial request. It is not uncommon that implementing all of the possible solutions and lettings the user choose the one that satisfies his needs would have been done in a shorter amount of time than discussing it.
I’m probably rambling but if we have a continuous build, that is releasable, we could in many of these cases give the customer builds with all of the solutions and let the customer decide.
I have quite often ended up in situations where the salesman has promised new or existing customer non-existing functions. Functions that took lots of overtime and ugly code to get done. When developers, more or less loudly, protests against this practice they are either laughed off or told they don’t understand the sales process.
Quite often these forced solutions are not tested enough so the client isn’t satisfied anyway.
Assuming you took my previous advice and created releasable daily builds, I suggest you deliver what you have at the moment and update with new functionality as it is done.
Edit 2012-01-17: OpenSVN seems to be down. I moved to xp-dev.com a couple of months ago. They have a free plan that works like a charm.
This was a plug for OpenSVN a free subversion repository.
I use it for keeping my university work so I can reach it from all my computers and revert to old version of reports and source code.
Sourceforge also uses subversion, but I guess my school work doesn’t really apply as an open source project.
Nightly builds are almost useless if there is no collective responsibility to keep the code in a buildable state.
Why should I even bother to make sure my code builds before checking in, when the build has been broken for a week and no one, who can/should do anything about it, cares?
Is it the responsibility of the ones who do care to be a PITA, or should we take it upon our selfs to fix all error just because we care?
When doing pc based development I think that having a working build environment that you can quickly recreate on a developers machine is very important.
I also beleive that making it possible to have more than one instance of said environment on any computer should be a prioritised goal.
save a lot of time when introducing new developers.
make it easy to do more than one thing at a time.
Since I didn’t find this info the first time I searched I’ll add it here to.
This is what you have to do to get the Team Explorer to work correctly if your TFS Server has a different DNS name than it’s machine name.
…and what is really missing in that instruction is to disconnect/reconnect you project in Team Explorer since all URL’s are cached on the client.
Attrice Corporation Team Foundation Sidekicks
From the site:
Team Foundation Sidekicks is a suite of tools for Microsoft Team Foundation Server Administrators and advanced users providing Graphic User Interface for administrative and advanced version control tasks in multi-user TFS environments.
In the field of computer software the term software build refers either to the process of converting source code files into executable code or the result of doing so. Release:
A software release refers to the **distribution**, whether public or private, of an initial or new and upgraded version of a computer software product.
If your Visual Studio instance hangs when doing operations that normally show a dialog, it might be because you have multiple monitors and the one Team Foundation wants to show the dialog on is not connected or you have swapped the primary and secondary monitor. This is actually not a TFS-only problem I’ve seen the same hang in other applications too so I guess it’s Windows that hasn’t figured out that a monitor is missing.