This is the second post from Taming TFS series. What I’d like to do here, is to give the big picture on how tfs operates, what it utilizes and how to use that. If you’re already familiar with the basics, you can skip this post, if not, then consider yourself invited to read on.
Let’s assume there is an application database and the various client applications developed in Windows Presentation Foundation, Silverlight, Windows Phone 7 and ASP.NET MVC 3. The database is either MS SQL Server or MS SQL Server CE. Now the potential customer may use one or many of these applications/platforms so the connections to the database must be performed from all of these clients. The following scenarios are considered. I tried to list some points that should be considered when choosing particular connection approach. The pictures represents the general architecture of the approach.
Recently I had to install an encryption software because I have started to keep some confidential data on my laptop and wanted to be sure it will not be compromised in case of my laptop is stolen. I was really surprised when notice the mass of encryption software available on the market. There is various options and features which such software can serve and they are quite neatly described on Wikipedia.
During software application development there is always a moment when user manual an help content must be written. Choosing appropriate tool for that is very important and decides about help creating and updating process speed. Help format is as important as the help itself and must be easily accessible from the application and convenient for the end user.
I’ve recently heard a couple of times about mongodb and finally had a moment to look further into it.
The concept is pretty familiar – to have a data store that is not a relational database. I’ve stumbled upon the info about xml or file system databases (the latter one is used e.g by svn), though nothing seemed to stick.
A while ago Microsoft released a very handy feature that allows for transforming web.config files during builds. This is a great thing, except for some reason, they limited the functionality to web.config files, which was strange, because the engine itself was designed to work against any xml file. Thankfully, that limitation is pretty much gone with a plugin called SlowCheetah.