Category Archives: Uncategorized

Colin’s ALM Checkin Policies VS 2019

I won’t go at length explaining the title, as post is useful only to people who already use this Visual Studio extension. At the time of writing this post, extension is not available for Visual Studio 2019. Last post from the author on this subject suggests he won’t be looking into this any time soon (post is 3 months old now). Multiple PRs have been submitted already so I am taking liberty of making available publicly my personal build of the extension.

I have not thoroughly tested the extension or ran unit test. It covers my teams basic use case, so I take no responsibility to maintain it.

Visual Studio Extensions dialog

Source code

Multiple EntityFramework contexts with code-first migrations

I’ve encountered an issue with code-first migrations in a brown field project which uses Oracle DBMS for data persistence. First to describe my goal in short:

  • Store all application data in single database
  • Application may have multiple data contexts
  • Old parts of database will not have any migrations, as they are created and updated externally
  • Application will have modules which don’t have tight dependency to some central data layer
  • Each module may have it’s own EF DB context. And each module may perform code-first migrations independently of other modules

Sounds quite straight forward, and it is, until we’ve hit a bug in EF. So, we created additional DbContexts, with their own migrations. Upon running the migration, what we’ve encountered is error back from Oracle.

ORA-00955: name is already used by an existing object

What has happened is that EF is attempting to create __MigrationHistory table which already exists. So, although there was another context which created the MigrationHistory table, next context attempts to create it again. We’ve found this bug reported in EF GitHub repo, all the way back in 2016. Workaround that bug author has used is to have separate __MigrationHistory table per context, which I did not like for a couple of reasons.

  • I may have many (more than 5) contexts, and I don’t want variants of __MigrationHistory table to clutter the databases
  • Configuration which allows this change is AppDomain wide, so we would have to either have separate apps to do migrations, or do juggling of AppDomains per DB context

Over investigation of the problem, what we’ve found is that it happens only if user does not use SQL Server dbo schema. Since we use Oracle, this was clearly the case. So we found two potential workarounds. One is clearly, create dbo user and __MigrationHistory table inside it. A cleaner one is to set default schema for HistoryContext of EF. This is EF internal context which is used to read migrations history. So, what you need to do is:Annotate DbContext with your own configuration (MyConfiguration)

1. Annotate DbContext with your own configuration (MyConfiguration)

    public class MyDbContext : DbContext

2. Implement the configuration. It’s purpose is to return subclasses history context. In this case MyHistoryContext

    public class MyConfiguration : DbConfiguration
        public MyConfiguration ()
            SetProviderServices("Oracle.DataAccess.Client", EFOracleProviderServices.Instance);
            SetHistoryContext("Oracle.DataAccess.Client", (connection, defaultSchema) => new MyHistoryContext(connection, defaultSchema));

3. Implement the subclasses context to use your desired schema

    public class MyHistoryContext : HistoryContext
        public MyHistoryContext(DbConnection dbConnection, string defaultSchema)
            : base(dbConnection, defaultSchema)

        protected override void OnModelCreating(DbModelBuilder modelBuilder)

Running ASP.NET application under elevated privileges

Hopefully there are better ways to run an application in IIS under elevated privileges. For my purposes, what I’ll describe in this post will have to do. Have in mind that having any kind of endpoint exposed to public web under elevated privileges is extremely bad idea. I’m doing this in lab circumstances, on a system whos purpose is to run tests on.

To elevate privileges of a web application, IIS process must be elevated of course. I did not see a way to elevate only single application in my short search.

You would think that impersonating an administrator for a single application would work, or that creating App Pool which runs under an administrator account would work. However, this is not the case.

You’ll have to run to machine.config file in one of following folders (I’ve edited configs of .NET 4, 32 bit and 64 bit):

machineConfigPathsSet userName attribute of <processModel /> element to System.

iisProcessModelAfter you run iisreset your application should be able to do serious damage to the system.

Early access to HttpRequest in ASP.NET application

This is I see question often asked by people working on legacy applications. When IIS Integrated application mode was introduced, there were couple of breaking changes that caused (badly designed) access to web request to crash.

Applications which used to access HttpRequest early, in Application_Start greet visitors with an exception:

Request is not available in this context

In simple words, request is not yet available in this stage of execution. It will be available later. Documentation for HttpContext.Request property states:

ASP.NET will throw an exception if you try to use this property when the HttpRequest object is not available. For example, this would be true in the Application_Start method of the Global.asax file, or in a method that is called from the Application_Start method. At that time no HTTP request has been created yet.

There are many suggestions that involve catching the exception, checking message or other properties and make a decision based on that. While this will work, it’s not good approach for number of reasons.

Most important of which, it will negatively impact performance of your application, which is explained in this MSDN article.

Checking message is not safe, since different language version of .NET framework may be used, with localized messages. Or the message can be changed in updated version of .NET framework.

In the end, determining that Request is not always enough. One may decide to allow this, if information in the request is not critical, but some (awful) code may require the request to properly perform the initialization.

Workaround is simple enough, that I’m amazed there are so many proposals for what I’ve described above.

  1. Move initialization from Application_Start to Application_BeginRequest.
  2. Since request handling method executes on each request, make sure it’s executed only once
public void Application_BeginRequest()

private static bool _startupPerformed = false;
private static object _startupLock = new object();
private void DoStartup()
    if (!_startupPerformed)
        lock (_startupLock)
            if (!_startupPerformed)
                _startupPerformed = true;
                // Initialize here

Creating network share with anonymous access

I needed to create a network share on Windows server machine which would require no authentication whatsoever from users. This post is intended to serve me as a reminder, since googling the solution every time eats easily away hours.

Settings which need to be changed of course depend on version of Windows of network share host. This post describes how to do it on a Windows 2012 R2.

Rougly what needs to be done is:

  • network share should be created
  • share permissions need to be set
  • security settings need to be changed

In more words:

  1. Share a folder by opening folder properties, navigating to Sharing tab and clicking
    Advanced Sharing…
  2. Enable sharing and click Permissions
  3. Add Everyone (should already be there), Guest and ANONYMOUS LOGON and give them Read access
  4. Open Group Policy Editor (hit Ctrl+R, type gpedit.msc and hit enter)
  5. Navigate to Computer Configuration → Windows Settings → Security Options
  6. Change following:
    • Accounts: Guest account status – change to Enabled
    • Network access: Let Everyone permissions apply to anonymous users – change to Enabled
    • Network access: Restrict anonymous access to Named Pipes and Shares – change to Disabled
    • Network access: Shares that can be accessed anonymously – enter name of share you created in the text field

This let me access the share \\<MachineName>\Share without providing any login information.

Running Windows 8.1? With how similar these two OSs seem, you’d expect this would be enough. However, it is not. For Windows 8.1, Microsoft recommends using Home groups. It is still possible to get conventional file share working, but I have not had time to try this out and it doesn’t seem a good security practice. I’ll just refer you to a find I stumbled upon on MS Technet Forums. Essentially what it suggests is using LanMan level 1 compatibility mode which would allow OS to accept LM authentication (in addition to NTLMv2). I’m not going to pretend to understand what kind of repercussions this has on machine security so I won’t recommend you to do it outside of your home LAN, and maybe not even there if it’s exposed over WiFi.


Web server returning proper response with 500 status


I’ve had a funny problem today. It wasn’t so funny during hour time I was trying to solve it. Directing my browser to a web page which looked OK yesterday resulted in a horrific view of content without downloaded styles and smelled like missing script files.

Debugger has shown that indeed, some of the static files could not be downloaded. Status 500, server said. Internal server error, server said. Ok then, let’s see what this is about. So I open Response body and what do I see? I see proper response, from start to end.


This happened to random static files.

Root cause

My bad…

I’ve placed some debugging code which occasionally failed in Global.asax.cs, Application_Start method. Code was such that it failed for random web request, and IIS was configured through web.config to let ASP.NET handle all requests, including static files. So, from standpoint of ASP.NET, web request has failed since an exception was thrown and it returned status 500 to IIS. However, it did not return any response body along with status, so IIS grabbed the file and sent it back.


Web fonts and IE on Windows 2012

I’ve had not a good day with web. It’s been throwing me curve balls whole day. One of things which wasted my time was Internet Explorer which is ran on a server OS.

I did not expect everything to go completely smooth, as it’s usual to have to go around IE enhanced security on server operating system if you wish to browse at all.

I’ve fired up IE’s debugger to see what’s going on, expecting that problem lies in MIME types configured in IE (or web.config file). However it turned out that IE did not request web fonts at all. There was no warning or notice in console either.

Iconless buttons
IE on server OS does not request web font unless site is trusted

Problem was that IE does not even request web fonts unless host is added to list of trusted sites. Run to IE options, Security tab, select Trusted sites and add target host to the list. Problem should be solved



Upgrading Windows 8.1 edition to Pro

The problem
I’ve recently got a new laptop with licensed version of Windows 8.1, however I needed a Pro version since I need Hyper-V. So… I downloaded “multiple edition” setup ISO from MSDN and repaved the machine. It did not ask for a product key and just got activated automatically as a standard edition. After searching around I found out you can change your product key (in a couple of ways) so I gave it a shot with my Pro key. But I was greeted with an error message.

That key can’t be used to activate this edition of Windows.

Googling and Binging around didn’t help as everyone pointed to using an “Upgrade key” which is a different thing. This doesn’t work for me since I’m MSDN subscriber. Why in hell would I then buy another key? I won’t budge… Go for another longer session of search…

The solution

Disable User Account Control

After disabling UAC changing product key worked like a charm. I’m amazed as anyone else…

View manipulation in AngularJS applications

Occasionally everyone has bad luck to have to manipulate DOM imperatively, based on business logic. It’s good idea to keep this code away from the controller. Problem comes up when you need access to controllers scope in UI code as soon as it’s created.
There are few rules which need to be followed in order to get the job done AND keep clean separation of concerns:

  1. Get access to controller scope as soon as possible
  2. Don’t make changes to controller which introduce dependency on UI code (it would be possible to call global function from a controller to inform about the event)
  3. Don’t create any global variables

A way to do it (admittedly, ugly way) is to use ngIf directive.

I marked controllers element with an ID so I can find it’s scope later, and aliased controller name to capture controller reference in a variable. I’ve called it vm here, as in “view-model”.

<div ng-controller="MyController as vm" id="myView">

Then I added script element where I can place UI manipulation code and applied ngIf directive to it. Parameter of ngIf directive is the controller.

      <script type="text/javascript" ng-if="vm">
        var view = angular.element('#myView');
        if (view.hasClass('ng-scope')){
          $scope = view.scope();

          function viewManipulator($rootScope){
            alert('Controller has loaded');
            $scope.$watch('Name', function (newValue, oldValue){
              if (!newName)
              alert('Hello ' + newValue + '!');

          viewManipulator['$inject'] = ['$rootScope'];

viewManipulator will be called right after controller is loaded and therefor scope is created and alert will show up. There we can hook up watches over scope data.

Why does this work?
Key is in lines 1 and 3. ngIf directive manipulates DOM to remove and add elements depending on provided expression. The first time that browser loads the script, the script gets executed. Controller is not yet created at this point. For that reason we have line 3, which checks for magic AngularJS class. ng-scope class is a special class that AngularJS applies to elements which have their own scope created (for example controller elements). First time that line 3 executes, controller is not created and ng-scope class is not applied.

AngularJS continues initializing the controller. Before MyController controller is fully created, ngIf directive on our script element removes the script (because our controller does not exist yet). After creation of controller is finished, ngIf is re-evaluated, vm is available and script element is added to DOM again. Because script is added, it is executed again, but this time line 3 evaluates to true so our UI manipulation code can be executed this time.

I’ve injected $rootScope just to illustrate that we can also get dependency injection. It’s not needed in this example. $scope cannot be injected, so we are closing over variable in which we captured it. Other services can be injected.

You can see a demonstration of the hack in this plunk. Buttons modify model in controller code, but UI is changed from view code which is hooked up to controllers scope. I can already hear some of you say “But you can do this with a filter!”. Yes, I can do what I demonstrated with a filter, but this is just a simplified example. Actual scenarios are not always so simple. Sometimes calculations need to be performed and complex decisions need to be made when changing the UI.

Hope this is useful to someone, and that I didn’t break too many rules with this approach.

Caliburn.Micro contextual view woes or: XAML is not a purely declarative language

When using Caliburn.Micro in ViewModel first approach, and binding contextual content inside a view to same model (initial ViewModel), make sure to set View.Context before setting View.Model.

The long version:
This is not a criticism of Caliburn. It is really an excellent framework to speed up development, and make WPF a little less verbose for you. It did cost me quite a bit of time to get used to it and to understand it’s concepts. For same reason it’s easy to shoot yourself in the foot and find what the problem is about.

My foot wound was caused by this setup:

<ContentControl cal:View.Model="{Binding}" cal:View.Context="{Binding State}"></ContentControl>

View.Model and View.Context dependency properties provided by Caliburn.Micro. They provide us a way to host content inside a ContentControl, bind it to model provided by View.Model and select a view control depending on value of View.Context. There is seemingly nothing wrong with code above. At least for me, because I look at WPF as a declarative language. However, after running the application I get an exception:

TargetInvocationException wrapped around InvalidOperationException, stating:

“Logical tree depth exceeded while traversing the tree. This could indicate a cycle in the tree.”

at System.Windows.FrameworkElement.FindResourceInTree(FrameworkElement feStart, FrameworkContentElement fceStart, DependencyProperty dp, Object resourceKey, Object unlinkedParent, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference, DependencyObject boundaryElement, InheritanceBehavior&amp; inheritanceBehavior, Object&amp; source)
at System.Windows.FrameworkElement.FindResourceInternal(FrameworkElement fe, FrameworkContentElement fce, DependencyProperty dp, Object resourceKey, Object unlinkedParent, Boolean allowDeferredResourceReference, Boolean mustReturnDeferredResourceReference, DependencyObject boundaryElement, Boolean isImplicitStyleLookup, Object&amp; source)
at System.Windows.FrameworkElement.FindImplicitStyleResource(FrameworkElement fe, Object resourceKey, Object&amp; source)
at System.Windows.FrameworkElement.GetRawValue(DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry&amp; entry)
at System.Windows.FrameworkElement.EvaluateBaseValueCore(DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry&amp; newEntry)
at System.Windows.DependencyObject.EvaluateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry newEntry, OperationType operationType)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry&amp; newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.InvalidateProperty(DependencyProperty dp, Boolean preserveCurrentValue)
at System.Windows.FrameworkElement.UpdateStyleProperty()
at System.Windows.TreeWalkHelper.InvalidateOnTreeChange(FrameworkElement fe, FrameworkContentElement fce, DependencyObject parent, Boolean isAddOperation)
at System.Windows.FrameworkElement.ChangeLogicalParent(DependencyObject newParent)
at System.Windows.FrameworkElement.AddLogicalChild(Object child)
at System.Windows.Controls.ContentControl.OnContentChanged(Object oldContent, Object newContent)
at MahApps.Metro.Controls.TransitioningContentControl.OnContentChanged(Object oldContent, Object newContent)
at System.Windows.Controls.ContentControl.OnContentChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry&amp; newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
at System.Windows.Controls.ContentControl.set_Content(Object value)

Since in my mind WPF was a advanced, nicer, smarter, better HTML, I first went after the problem in my ViewModels and code. Little did I know, problem was in the one line from beginning of this post. Order of Caliburns dependency properties was to blame. Looking more carefully, I noticed that ContentControl was getting filled with same user control which hosted it. It turns out that, though bindings give impression of declarative coding they are dependant of each other. Since View.Model was set first, Caliburn started looking for appropriate View for the model provided. Since View.Context was configured later, it defaulted to main view control. Correct declaration would be following:

<ContentControl cal:View.Context="{Binding State}" cal:View.Model="{Binding}"></ContentControl>