IME, it depends enormously on the position you're interviewing for, and how you deliver it. Both of those trace to your internalization of it.
For one thing, bear in mind: Aspbergers' is a syndrome, not a pathology. The same is true for autism. It's a collection of symptoms, most of which just so happen to compliment tech fields. To the point of cliche.
It's really not a big deal. Discrimination happens when prejudices are triggered, so avoid this by wrapping it in humor. I broach the topic in an interview like, don't you kind of have to be at least a little autistic to do what we do? I mean, what are we doing, really? We're stacking blocks. We put those blocks inside other blocks, and then we stack them again.
We're playing with Legos. For a living.
This makes it amusing, and light-hearted, and firmly frames the topic as being a person with autism, not an autistic with person. The idea that it's a 'disorder' is completely avoided: obviously we're ideally suited for this task, and how does 'disorder' fit into that? The end.
On the occasion coworkers / bosses inquire (always after hire ;) ), the dialogue follows these lines: yeah, I really am autistic. It's whatever. Sarcasm is sometimes lost on me. I default to stone-cold literal, meaning sometimes I will react completely literally to what I couldn't tell was a joke, and I won't even stop to wonder if you were serious until you start looking at me like I'm the weird one. :P Sometimes, you'll ask me a question and I'll deep-dive to no apparent in a quest to provide a complete answer. It's a bit annoying, especially for me - but hey, at least I take you seriously. ^_^
Anyway, that's how I deal with it. HTH :)
--- Edited to add context and clarify strategy for demonstrating this as desirable
So, interviewing, for me, is necessarily for senior dev. I expect to speak with multiple people - often the entire team. The ratio of business-facing (ie, the project manager) to devs is usually ~1:3-4 and at least one will be the lead dev. It's a luxury - being able to safely presuming everyone is well-versed in the culture of software dev, business or dev.
The key is in your thinking: your technical skills are the reason they're interested in you to begin with! Emphasize this and how it translates into, say, the apparently uncanny knack for delivering what they WANT, based on what they SAY. Conversely, play down frustrating traits (ie, deep-diving technical issues unto infinity, etc - you know how we can be, I'm sure ;) ) with humor. This creates the contrast necessary for potential employers to perceive your dx as flattering, instead of prohibitive.
-- hth :)