hahaha .... ok I see there is a problem here BUT only in the native english speaking world where you know about the term "Nuke them" ... In Sweden were I operate there is absolutely no problem with the name dotnetnuke .... everybody interpreter dotnet first as something from microsoft and when you tell them it is for free they love it .... so I don't agree with rebranding the name BUt you guys working in US (where the term Nuke them has been used most ....strange I don't know why?)..... just start using DNN on a large scale and the problem is gone ....

/Johan Kontorshotell

 if European wouldn't have lost control over their colonies in the new world an few hundred years ago, we would for sure not have to deal with this problem today at all. Unfortunately, there is no use to complain about it nowadays....

If you can't favorably explain DotNetNuke in under 30 seconds to a client you shouldn't be using it.  Get comfortable with it or find something else.  In my case, clients hire me and I provide what's required for their needs.  If they have specific requirements that don't match me, such as not wanting to use DNN, then I suggest they choose a developer more suited to their requirement.  Every job I turn down is that much more time to do the jobs for the clients that really want me.

That said, I couldn't always do this.  I have had to beg for work and do anything to get it, I'm just happy that this is rarely the case anymore.

Jeff