From the comments on Nick’s excellent post (that instantly made me feel hungry <g>):
If you find your developers bringing in their own equipment to work then you know there is a problem.
That reminds me of this story: Read the rest of this entry »
Archive for July, 2010
Nick Hodges | The End of the Chow Line
Posted by jpluimers on 2010/07/30
Posted in About, Keyboards and Keyboard Shortcuts, Opinions, Personal, Power User, RSI, ThinkPad, UltraNav keyboards | Leave a Comment »
LinkedIn should send “Notifications for Requests to Join My Group” #fail
Posted by jpluimers on 2010/07/30
Right now, LinkedIn does not send Notifications for Requests to Join My Group.
They should!
Right now you need to watch the LinkedIn group very frequently, otherwise you miss the “requests to join.
Mail notification would make that much less of a burden.
–jeroen
Share this:
Posted in LinkedIn, Opinions, Power User | Leave a Comment »
CodePlex: choosing a license
Posted by jpluimers on 2010/07/29
One of the toughest parts on creating a new [Archive.is] CodePlex project is choosing a license.
As Jeff Attwood wrote a couple of years ago, choosing a license – any license – is important, because if you don’t, you declare an implicit copyright without explaining how others could use your code.
In addition to that, Jeff published a list of licenses with a one-line phrase describing them, so it becomes easier to start making a choice.
Last year, ShreevastaR extended that list in his answer to this StackOverflow.com question on CodePlex licensing.
Brian Campbell did the same a few months later on another StackOverflow question about CodePlex licensing.
There are many more StackOverflow.com threads like those 2, and they give similar results.
The reason I want to put up a CodePlex project, is to put my sample code for conferences, blog articles and course examples on-line so they are easier to share with other people.
Most is from Visual Studio or Delphi projects using languages C#, VB.NET and Delphi.
Some of it are batch-files, XSD, XSLT, or other small snippets to get stuff working. Read the rest of this entry »
Share this:
Posted in .NET, Access, CodePlex, Database Development, Delphi, Development, Firebird, InterBase, Software Development, SQL Server | 4 Comments »
.NET/C#: a generic exception class
Posted by jpluimers on 2010/07/28
I want my exceptions to be bound to my business classes.
So you need your own exception class, and are expected to override the 4 constructors of the Exception class.
But I got a bit tired of writing code like this again and again:
using System;
using System.Runtime.Serialization;
namespace bo.Sandbox
{
public class MyException : Exception
{
public MyException()
: base()
{
}
public MyException(string message)
: base(message)
{
}
public MyException(string message, MyException inner)
: base(message, inner)
{
}
public MyException(SerializationInfo info, StreamingContext context)
: base(info, context)
{
}
}
}
Searching for Generic Exception Class did not reveal any generic exception classes.
So I wrote this instead: Read the rest of this entry »
Share this:
Posted in .NET, C#, C# 2.0, Development, Software Development | Leave a Comment »
Visual Studio 2005/2008/2010: ContextSwitchDeadlock was detected Message (via Keith Barrows)
Posted by jpluimers on 2010/07/27
Like Keith Barrows, each time I see a message like below, I’m reminded that I forgot to change my Visual Studio 2005/2008/2010 to disable these kinds of MDA messages:
ContextSwitchDeadlock was detected Message: The CLR has been unable to transition from COM context 0x1a7728 to COM context 0x1a75b8 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.
Steps to get rid of these messages:
- Start Visual Studio :-)
- In the menu, select “Debug”; “Exceptions…” (Ctrl-D, E)
- Open the “Managed Debugging Assistants” tree
- Uncheck the first checkbox in the “ContextSwitchDeadlock” row
Maybe I won’t forget this next time :>
–jeroen
Via: Keith Barrows : ContextSwitchDeadlock was detected Message.
Share this:
Posted in .NET, Development, Software Development, Visual Studio and tools | 1 Comment »
The Wiert Corner - irregular stream of stuff 