Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Jason Mauss' Blog Cabin

Because someone's got to do the dirty work

  • How would you store the information?

    One of the new products I'm developing for my company is "NQuery", a SQL builder WinForms UserControl. It displays various schema information so the user can drag and drop tables, choose some fields, set some criteria values, etc. in order to have the SQL statement created for them. (btw, props to Scott for coming up with the name "NQuery" - I'll try to round up some swag for you, Scott.)

  • I've sinned and I'm going to gather requirements

    I really don't understand why putting together software program requirements tends to be such a hellish, ill-fated task. I just have to rant today because if I don't, I might break some piece of equipment I need to be able to work. Then again, maybe I'd finally be able to take some time off if that happened.....but I digress.

  • Help Me Name A Product!

    At my company, Knowledge Relay, we're going to be building a query builder/designer similar to what you get with SQL Server Enterprise Manager and Access. You can see an example of what I'm talking about if you look at this page. The main difference between what we want to build and BinaryWorx's tool is that we want the QueryEngine to work server-side so that you can also implement the component as an ASP.NET server control as the UI display. We've thought about ".Query" since it is going to be built with .NET. We also want to try and integrate our company name (Knowledge Relay or 'KR') into the name of the product if possible. Something like "KR Query Maker" maybe. Anyway, if you can think of a good name and/or suggestion, please, let me know!

  • Neglecting the Weblog

    I've been pretty quiet on the blog lately, mostly because I've been so busy with work and family and church that I haven't had much time for anything else. I guess it's good to be busy. I do like writing though, so I have to get back into blogging.