When the obvious has been ruled out....

...you're probably missing something equally obvious.

I was trying to uncompress a large (5Gb) file today, and kept getting "Insufficient Disk Space" or variants thereof.

I tried again (a 10 minute operation) after each of the following:

1. Ensure target disk has plenty of space (80+Gb)
2. Ensure source drive has enough space (10Gb)
3. Ensure temp directory has enough space (just)
4. Ensure system drive has enough space (30Gb)
5. Move temp directory to another drive with more space

I finally remembered that the partition I was copying to had originally been created for a partition-magic style auto-restore partition. FAT32 is a great choice for that sort of thing (boot time access), but not quite as nice for storing single 5Gb files >:(

A swift C:\convert F: FS:NTFS to convert the partition to NTFS without losing any data, and it's all sweet 15min later.

T

It's Blog time!

It's the end of the world, I've finally decided to start blogging.

I'm a .Net Technical Lead in Australia, currently working on a large project for a client, and looking after a dozen or so devs.

After using thousands of blog posts and articles to help debug issues over the years, I've decided to try and give something back, documenting the nasty gotchas that inevitably pop up on a regular basis (the gristle in our .net T-Bone).

I'm sure there'll be some other random musings etc as I go.

My phobia about private information on the web is still pretty strong, hence the lack of real detail here, for my privacy, and that of my employer and client(s). If you know me, feel free to say G'day :)

T

JavaScript errors from WebResource.axd when calling an aspx over HTTPS

I ran into a pearler the other day,

The project we're working on requires that user credentials only ever pass over https, but we don't want to run the entire (behometh) site over SSL for server performance reasons.

As soon as we called our login page (which has asp.net ajax validators etc) via SSL, we started getting the now familiar 'asp.net ajax javscript isn't here' type errors. Fiddler showed very few files being served compared to an unsecured request.

Googling kept turning up a fix revolving around the ServicePointManager (example), but it didn't seem relevant to my error... The penny finally dropped when I checked the Event Log of the server, and saw the errors mentioned on Jan Tielens blog, which also has the best treatise on why this occurs.

Using the ServicePointManager.ServerCertificateValidationCallback to return true instantly solved the issue.

Because I wasn't on the consuming side of these requests (as opposed to me making a ScriptService call), I hadn't run into the exception from the consumer side, which explains why it took so long for me to twig that this was in fact the fix I needed.

It took 2 days, but I chewed that Gristle down :)