Frequently Asked Questions

These are a few of the questions people ask me about the project. Feel free to ask other questions in the GitHub discussions. If you’re thinking it, you’re probably not the only one! If you find a defect or want to request a feature, use the issue tracker on GitHub for that, please.

Do I have to pay for this or not?

Not. POP Forums is an open source software project hosted on GitHub for use under the MIT license. There is a commercially hosted version available at PopForums.com, yes, for people who don’t write code or don’t want to mess with managing their own software. Everything on GitHub continues to be open source.

Another forum app? For real?

Yeah, I know. I’d like to think that this one is a little different, because it doesn’t exist to fit some generalized needs, it exists to fit the needs of real communities, like CoasterBuzz. The design goal of the app, from its early days in 1999, has always been to design for users, and not be a science project. This app lives because it has been required for sites like CoasterBuzz for more than two decades, and it will continue to evolve because those sites will evolve. It just makes sense to share it with others.

Sounds like you’ve been doing this a long time.

Yes, I sometimes feel cursed to rewrite it for all eternity. The Webforms versions were really kind of a mess, and no version was a true rewrite. Once MVC came along, it gave me great incentive to start fresh. Dotnet Core and the evolving front-end frameworks give plenty of new opportunities for refactoring.

Is this project the basis for the commercial hosted product?

Yes, it’s the very same code, though obviously decorated with additional code to facilitate multi-tenancy and provisioning.

What languages are supported?

Currently we have English, Spanish (es), Dutch (nl), Ukrainian (uk), Taiwanese Mandarin (zh-TW) and German (de). If you’d like to translate, the .resx file has around 400 entries. Open an issue to learn more, and we can talk about a pull request to add another language.

You used to work on the forums for MSDN and TechNet. Is this that forum?

Not at all. That app served a great many different functions and was integrated with Microsoft ID’s, a centralized profiling system, etc. It was/is huge. This app has its roots in the web sites I’ve been running for fun and profit for years, to the extent that you can find old posts on those sites from the turn of the century with all kinds of formatting failures. Those were the ASP.old days.

I noticed you’re not using [some ORM framework]. Why not?

One of the requirements back in the day was to simply work with the existing data structures of v8.x, a Webforms app. In that sense, the data plumbing was already pretty well established and known to work, and it has followed all the way up through the Core version. My opinion is that ORM’s tend to be leaky abstractions that never work in the black box way that you would hope. I have adopted Dapper though, which covers the core use case that you’re really after anyway: Mapping parameters to queries and results to objects. One doesn’t have to write actual SQL all that often, so using an ORM doesn’t provide a ton of value.

You don’t name your async methods with the Async suffix. Just who do you think you are?

Look, when almost all of your methods are async with no synchronous version what’s the point? The only place I use it is when there are both synchronous and asynchronous methods. Your fancy IDE knows what the return type is, and the compiler lets you know when you’re not awaiting. You’ll be fine.

What external frameworks are you using, and why?

I wanted to keep external binaries to a minimum, but I’m using MailKit for email functions, ImageSharp for photo resizing, NSubstitute for test mocking, and xUnit for unit testing. On the front end, the main app uses vanilla web components written in TypeScript, along with Bootstrap and TinyMCE. The admin area uses Vue.js. Github has that handy dependency graph now that you can look at for more information.

What? You’re not using React?

Here’s the thing about a forum… it’s mostly walls of text. I can tell you from the 60,000+ topics I have indexed on a couple of sites that it’s super SEO friendly. To that end, the functionality of a forum is mostly making posts, which doesn’t require a big library to do. That’s why there are little web components spread around on little islands, and not an all-in effort to React. Heck, the admin area uses Vue.js, but even that works by way of a simple script reference, and no transpiling or bundling.

The unit tests suck.

That’s not a question. In porting to Core, much of the controller-level unit testing didn’t come along, and it needs a lot of refactoring. Ideally, there shouldn’t be so much logic in the controllers, but there is still some there.

What’s the release roadmap?

It has generally been my intention to keep up with the latest .NET framework versions, which are now reliably annual and released later in the year. You can check the issue tracker for stuff currently in flight. While v19 had a lot of big bang features with a large blast radius, that seems less likely going forward.

Can I contribute?

I very much welcome translations of the .resx files, so send a pull request for those immediately! If someone really digs into the source code and understands it in a non-trivial way, then yes, I’ll happily accept pull requests. If you can find a bug to squish from the issue log, that would be a great PR to see!