Johan; thinking out loud.

It is painfully slow to do disk intensive things in a virtual environment on my laptop. The disk, and hence the laptop, is getting very hot. I forgot to bring my Zalman laptop cooler to work today. A mistake I get punished for now. It is not just hot as h..l it had the sound characteristics of a hairdryer. With the cooler attached I have to stress the laptop a lot before it gets really hot.

I’ve got an Acer 8204 and the disk is just a 5400 rpm. I think Acer opted for space instead of speed when they specced it. At home I have my virtual disks on an external drive and there I really like working in the virtual environments. Currently I have to force my laptop into the backpack so I have to leave the drive and cooler at home when I go to new workplaces. I think I will have to beg for a new laptop backpack so I can carry all my stuff. It is the closest thin I come to an office so I think it is worth the cost.

Share This

In light of the recent controversy of using plugins in Visual Studio Express and getting some inspiration after listening to the DotNetRocks episode with Christopher Wille on SharpDevelop I thought I should give SharpDevlop a chance again. I am working on two utilities that I plan to release as shareware and as I do not want to rely on tools supplied by my employer I have been using Visual Studio Express until now. I haven’t done any real work in #Develop yet, but I’ve got both projects up and running.

The first thing that bit me was the lack of a typed dataset designer. I was on the way to move that structure into a List<T> anyway so it doesn’t bother me that much right now. I’ll write about the progress of each project this week.

Share This

When you have more than one project in your visual Studio Solution you often get in trouble because the information in all AssemblyInfo file is almost identical.

Here is a tips on how to use Visual Studio to manage a central file with the information that should be shared across project and project specific AssemblyInfo files.

Share This

I’m trying hard to not make this blog a place where I drop links, but some tools I just can’t ignore.

GhostDoc 2.0 has been released:

Roland Weigelt : GhostDoc 2.0.0 Released

… and there is a lot of fuzz in the cloud because of these: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

Share This

… or you get an ‘Object not set…’ when trying to expand the DataSource list in the properties window,it might be because you have a corrupt datasource in your solution.

Press ALT+SHIFT+D to open the data sources window.

If there is one with a yellow sign in front of it; delete it and Visual Studio should start working again.

I got a corrupt DataSource when I imported a solution to TFS.

Share This

If your Visual Studio instance hangs when doing operations that normally show a dialog, it might be because you have multiple monitors and the one Team Foundation wants to show the dialog on is not connected or you have swapped the primary and secondary monitor.
This is actually not a TFS-only problem I’ve seen the same hang in other applications too so I guess it’s Windows that hasn’t figured out that a monitor is missing.

Share This

You can find it here.

Share This