A possible cause for System.IO.FileLoadException

“An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.”

Could not load file or assembly ‘file:///C:ProjectsworkerqueueSourceDA.WorkerbinDebugpluginsNewtonsoft.Json.dll’ or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)

Check the assemblies loaded do not need to be unblocked:

Desktop Windows Manager consuming high CPU on Windows 8

I don’t know what caused it, but my video on Windows 8 became slow and jerky. Videos would not play. Desktop Windows Manager was consuming 20 to 25 percent of CPU (an entire core, I have a quad core machine). I killed Aero and rebooted my machine. Nothing worked. I have a dual monitor setup. When I uninstalled the video driver I lost the second monitor, but the video was normal again. I re installed the video driver and so far its working.

PST file size versus Sql Server file size

I’m a bit of a pack rat — I don’t throw anything away, including emails.

In 1998 I started using Microsoft Outlook. For the time it was a great program. The best feature was the integrated MS Word support as the editor. Now that is common place, but back then it’s was the cats meow.

Over the years I’ve saved my PST files into an archive, it has grown to over 10 gigs. It was time to extract the messages and store them in a more searchable medium. I’ll be posting more on what I’m doing later. To my point, I am blown away with the size difference between the PST file format and the Sql Server.


*Image Reference

Stats

Emails: 51574
Attachments: 8637 (yes, I have saved everyone of the attachments to the database)

PST: 8.9 gigs
Sql Server: 368 MB

I don’t know the inner workings of either product. Sql Server is optimized for data storage, Outlook is apparently not. I’m not surprised that SQL Server has a much smaller footprint. I’m surprised by the degree of which SQL Server is smaller.

Ditching the Laptop, Moving to the Tablet

I sold my laptop and replaced it with a tablet. The biggest challenge to moving to a tablet is to maintain the ability to code C# on the road.

A text editor is always an option, but that does not solve the compiling problem. Looking around I discovered that most tablets support Bluetooth mice and keyboards. I’ve concluded that there will not be a visual studio android app anytime in the future. This means I have to get into an environment where I can code and compile C#. I have one option: to remote desktop into a machine.

There are a number of remote desktop apps for the android. I settled on the WYSE Pocket Cloud app. It’s a full screen solution that runs over the remote desktop protocol. It works similar to other web based solutions such as logmein. Logmein does have an app, but it’s twice the cost and lacks some of the features of the WYSE PocketCloud app.

My tablet setup looks like this: A Samsung 32gig 10.1 tablet, a Logitech Bluetooth keyboard for the android and a Bluetooth mouse. This gives me the flexibility of a laptop and the benefits of a tablet.

Hypersonic 2.1 Released!

A new version of Hypersonic was release today!

A new feature was added to help retrieve Identities from the insert. The headache of declaring and out parameter in C# is no longer.

public int Insert(User user)
{       
		List parameters = database.GetParameters(User);
 		parameters.SelectIdentity();

		_database.NonQuery("User_Insert", parameters); 
		return parameters.Identity(); 
}

The C# Code Generator for Hypersonic has been updated to support the new out parameter feature.

New Job

I started a new job and bought a house in the last month. I have been very busy. I’m starting a new blog on house related issues over at http://house.chuckconway.com. Please check it out! The new job is challenging. I’m working with a group of smart people that school me daily. I hope to post some of those lessons here.

Ooooh the Pain — Conditional Compilation Directives

I never use them. It does not feel right. Baking in environment specific information into your compiled code never sounded like a good idea. I want my code to behave the same way in all build configurations/environment. Development should not have code enabled that is not available to QA. That’s crazy!

If you want environment specific code use the provider model/pattern, use the web.config transformation, use a data driven configurations.

For heaven’s sake do not compile environment specific configurations into your code!

Ooooh the pain!

Chronic Contractor

This developer is always looking for a gig. There is always something better. Chronic Contractors are expensive. Mileage per dollar varies.

They have battled many and because of this they see problems. Something about every gig frustrates them.

Chronic Contractor tend to work in cutting edge technologies and loathe older “inferior” technologies. They have no allegiance, they don’t care if the ship sinks, another is waiting in the docks.