Data Layer Validation with Entity Framework 4.1+

This is a helpful series for when you need to start doing any sort of validations on your entities. I need to dig more into OData and how it integrates nicely with NG and friends using .NET. Personal notes follow.
Continue reading “Data Layer Validation with Entity Framework 4.1+”

Correctly Setting the VMWare Provider for Vagrant on Windows

When you purchase the VMWare provider for Vagrant on Windows you learn that the provider name is vmware_desktop. The only time that you will ever use this name is when you install the provider and the license. If you use that provider name anywhere else you will get message

The provider ‘vmware_desktop’ could not be found, but was requested to back the machine ‘default’. Please use a provider that exists.

The correct provider name is vmware_workstation.
You might mix up the two names when specify a provider when you are bringing a box up. I did it. He did it. It is easy to do, especially if you scan a box page to find the provider name. The name there is for the name to install the license, not to start up a box.
This “issue” has been around for over a year and wastes about an hour of your time if you are facing it on Windows.

Entity Framework 4.1 – DbContext Data Access

Entity Framework 4.1 – DbContext Data Access covers the DbContext object. It is important. The lecture explains why it is important. It might seem abstract if you haven’t touched any of this stuff before. That is OK. You will recall it when you need it.
Personal notes follow.
Continue reading “Entity Framework 4.1 – DbContext Data Access”

How to Correctly Enable Flycheck in Babel Source Blocks

If you already have Flycheck turned on then you already have it running your babel source block buffers, but, it isn’t working how you expect it. That buffer hasn’t got a file name. Flycheck can’t be smart about helping you out here. Via this post, the solution follows.

(defadvice org-edit-src-code (around set-buffer-file-name activate compile)
  (let ((file-name (buffer-file-name))) ;; (1)
    ad-do-it                            ;; (2)
    (setq buffer-file-name file-name))) ;; (3)

This is one of those things that if you had though about it for a few minutes, you would have turned it on yourself. It reveals how easy it is to return to the mode of “application user” from “application designer”, of Emacs. That is the source of most of my dumb “misses” regarding workflow optimizations in Emacs.

How to Handle and Large Slow Org Files

When some of us open large Org mode files, Emacs becomes nearly unresponsive, and nearly unusable. My stock advice has always been to call #+STARTUP: showeverything or do a binary search more or less to figure out which package is stomping Emacs. In this post, though, Puneeth explains that the issue may go away entirely for some of us.