I generally agree with most of the answers here that dislikes should be employed only if they are deal breakers, but consider that dislikes can be used strategically to enhance your CV.
While it will turn some people off, those with strong opinions often get noticed, especially by others with strong opinions - notably type A personalities that enjoy climbing the corporate ladder, or in other words your hiring manager/boss.
If you like a lot of things, and dislike nothing, it may mean that you are simply a well rounded developer that believes the right tool should be used for the right job. It could also mean that you won't speak up if the wrong decision is being made, that you waffle, and that you are a 'lukewarm' programmer that hasn't had enough experience to know what's really, truly bad.
Type A personalities
Alternately, you can use it to appeal to those with strong opinions. Guess what - there's a strongly vocal group of people that loathe VB. Of course this hatred comes from the early days of VB, but that won't stop them from hating basic in general and VB in particular. It may not hurt you to add VB as a dislike (although if you work with .NET you might want to reconsider).
Further, it can show them that you have enough expertise in a language, technology, or framework to really hate it.
I don't think you'll get many blank stares if you mention that you dislike cobol, fortran, or even MFC and it will make an interesting interview topic as you discuss the projects you've worked on where the language, technology, or framework itself proved an impediment to good development practices.
Don't treat that field lightly, but don't discount it out of hand either.