Entity Framework


In a project using Entity Framework, I received the error:

Error 111: Properties referred by the principal role MyTable must be exactly identical to the key of the entitytype when you compile the project in Visual Studio.

Entity Framework Resolution

I had two existing tables in the edmx diagram.

To create a relationship:

I had to make my identity field a primary key.  I then added the relationship.

In the entity framework diagram, I deleted and re-added the foreign table.

However, I did not delete/re-add the table with the new primary key.

Then, re-add the foreign table.

Next, Visual Studio added the relationship.  The problem is that it builds a relationship to a table that thought did not have a primary key.

When I deleted/re-added the primary key table from the diagram, the error resolved.


For more information on how Acumen can help you, contact us today!

For additional help, contact Microsoft Support by clicking on the link below:


Windows Audio Device Graph IsolationWindows Audio Device Graph Isolation

One of our laptops began having all sorts of lag problems and a process called Windows Audio Device Graph Isolation seemed to be the culprit.

It manifests itself largely on website that have video content that loads automatically.

Most sites nowadays experience this because of sidebar advertisements. There’s an easy solution that has yet to cause us any problems and dramatically improved performance on the laptop in question.

  1. Right click on the Sound Icon in the Tray (lower right corner of Task Bar)
  2. Playback Devices
  3. Right Click > Properties of the default audio device (the one with the green check)
  4. Enhancement Tab
  5. Check disable all enhancements (even if none of them are checked)
  6. Ok
  7. Ok

The performance is resolved!

The process in question is called audiodg.exe if you want to kill it individually, but the problem will tend to resurface.

For more information on how Acumen can help you, contact us today!

For additional help, feel free to click on the Microsoft Support link below:





Recent updates to this reader, as of Oct 5, 2015, are causing major performance issues. The problem is rather technical but the result is that if you happen to leave it up for a few hours your entire computer will slow to a crawl.

The team is looking into the issue according to their website but the solution is fairly simple. You must do two things.

  1. Uninstall the Cloud if it is installed
  2. Delete or change the name of the file: DocoShare.fpi

Uninstall Cloud

  1. Control Panel
  2. Add/Remove Programs
  3. Foxit Cloud > Remove

Delete or Change DocoShare.fpi

  1. Open File Management (Windows Explorer, Computer, My Computer depending on Operating System)
  2. Open C:\Program Files (x86)\Foxit Software\Foxit Reader\Plugins (or something similar depending on OS)
  3. Rename or Delete DocoShare.fpi
    1. I like to rename personally and called it DocoShare-old.fpi

This should solve the problem. Hopefully FoxIt will eventually come up with a solution which will be implemented on an update.

For information about how Acumen can help you, contact us today!

For more information about Cloud Computing, visit the site below: