Friday, 7 June 2019

Configuring SignalR

Each host has access to an IConfigurationManager which allows you to tweak some default SignalR settings. Some things that can be tweaked are:

  •     ConnectionTimeout - Represents the amount of time to leave a connection open before timing out. Default is 110 seconds.
  •     DisconnectTimeout - Represents the amount of time to wait after a connection goes away before raising the disconnect event. Default is 30 seconds.
  •     KeepAlive - Representing the amount of time to wait before sending a keep alive packet over an idle connection. Set to null to disable keep alive. This is set to 30 seconds by default. When this is on, the ConnectionTimeout will have no effect.

Tuesday, 7 August 2018

Ignoring a property in Fixture

I've been using Fixture for unit testing, and today I needed to ignore a property in a model. This is how its done:

Tuesday, 26 June 2018

Querying an IIS Express site over the LAN

Open this file:

C:\Users[YourName]\Documents\IISExpress\config\applicationhost.config


Add this row to the bindings element

<binding bindinginformation="*:yyyy:xxx.xxx.xxx.xxx" protocol="http" />


where yyyy is your chosen port number and xxx.xxx.xxx.xxx is IP address on your network.


Run these two commands in a admin cmd prompt

netsh http add urlacl url=http://xxx.xxx.xxx.xxx:yyyyy/ user=everyone

netsh advfirewall firewall add rule name="IISExpressWeb" dir=in protocol=tcp localport=1914 profile=private remoteip=localsubnet action=allow

Tuesday, 20 February 2018

EF edmx update wizard not responding when updating models from SQL Server 2017

Recently when updating my db-first edmx from my SQL Server 2017 database, the update wizard would hang. I overcame this problem by temporarily changing the compatibility level of the db to 2012 like so:


So far this seems to have no ill-effects.

Saturday, 3 February 2018

Completed 406 Not Acceptable with Devise

I had some trouble after an update of ruby/rails/gems on a something I hadn't worked on for ages. When register a user with Devise it would error with a Completed 406 Not Acceptable with Devise
As usual Stack Overflow came to the rescue, where I found this: "Devise responding to json by default has been removed from version 2.2" The fix was simple, I added this to my confif/application.rb and everything was working fine again:

config.to_prepare do
      DeviseController.respond_to :html, :json
    end