Michael Washington wrote
I too work in Local Government (Los Angeles County, California). For us DNN is a time saver and cost saver. As far as modules are concerned we always buy the source code, period. If the module developer goes out of business I simply don't care because I can made any modifications needed. I still have saved time and money. When I need workflow and versioning I write it myself.
The thing that i find funny when people throw out other CMS's is that I can develop in ASP.NET far faster than any other platform.
Those are two important points for module developers to pay attention to, though maybe for a different reason than you pose. Source code has value, and modules with source available can command a higher price. I find developers afraid that I'll "steal" their source. I could care less about their source, other than my needs to modify it or retain it if they disappear. I'm willing to pay for the license to use and modify it, and redistributing their source would get me in trouble with my employers faster than with the developer.
The second point is that developers have a bias in coding. I am also far better in ASP.NET than in competing languages, but I've spent more time and effort becoming proficient with it. I just can't code my way out of a paper bag, no matter what the language. :)
I have a colleague who can't write ASP.NET code, he's been writing RPG and Java for decades. For him, the solution is something he knows, not ASP.NET. For me, I don't know RPG more than printing my name on a screen and Java is something that comes from Starbucks. Neither of us is "wrong", we just arrive at the same solution by a different, albeit often incompatible, means.
The second half of the ASP.NET skill set issue is that I am pretty much the only ASP.NET programmer. And my job function is network administration, not programming. I'm not about to tackle workflow and versioning, nor am I willing or able to maintain it as DNN versions change. That's something I need available from an outside developer. As either a core function (preferable) or a module. I especially need this to be an outside, reliable, developer since there would be little, if any, continuity if I leave my employment.
Everybody's, and every organization's, needs are different. Which is probably why the real answer to this question is that DNN modules are both underpriced and not underpriced. The answer is unique to the purchaser, and the criteria is different for every purchaser. I equate this to the graphic design world (my wife is a graphic designer) and Adobe's product line. Adobe Photoshop is around $700, while Adobe Elements is more like $99. For my wife, a professional, Photoshop is a good value, even at $700. For my sister, Elements is more than she'll need and may even be overpirced for her at $99.
To each their own...
Jeff