Sql Server Application Role is a way to control access to the database for specific applications. It simply grants a access to a program that provides application role credentials, not for the user login that is used to connect to a database.
In my last post I have described a workaround for using a FileTable in Entity Framework 6.0. In this post I would like to show you the results of performance test of storing big documents in sql FileTable.
FileTable is a great new feature in SQL Server 2012 which facilitates storing and working with unstructured blob data in SQL Server. Unfortunately is not yet supported in Entity Framework, so you cannot simply use FileTable in your entity model. But there is a workaround for this inconvenience, which I am going to show you in this post.
In the Entity Framework we can easily enable lazy loading of navigation properties by marking them as virtual. This however applies only to properties that reference other related entity type. The framework does not support lazy loading of scalar or primitive properties. But there is a trick to fill this lack quite easily.
Recently we moved our main WPF project to .net framework 4.5 and Visual Studio 2012. Then when I tried to preview some of basic views in Visual Studio designer I faced some strange problems. We have several user controls that we use in our views.
We’ve been using semantic versioning for a while now and it’s been paying out. Though there were some ‘quirks’. Now, version 2.0 is (almost) out and guess what, it addresses them! Let’s take a look at the new version and see what changed.