$ 0 0 For anyone who may have had this issue, after a rollback to .Net Framework 4.0 this issue was resolved!