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.
I stumbled upon a problem when trying to set up a default route for an asp.net mvc3 application. The routing mechanism itself is pretty straightforward, so I didn’t really expect any problems here, but as it turned out I was wrong.
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.
Earlier I wrote about the problems of a common authentication approach. Today, I’m going to do a quick demonstration how to set up forms authentication to secure a web app with an oData service and how to use forms authentication to connect to the service from a wpf client.
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.
In this article I would like to show you my implementation and approach for using abstract repository no matter if the client is connecting directly to the database using Entity Framework, over WCF service or WCF Data Services (WCFDS) service.
This blog shortly describes a few chosen DI containers and their out-of-the-box functionality. If a certain container does not have a specific platform listed, it doesn’t necessarily mean that it’s not possible to use it there – it just means that it’s not in the box.