How do you get the latest release? GitHub!

YAF.NET: https://github.com/YAFNET/YAFNET/releases/tag/v2.1 
YAF.NET DNN Module: https://github.com/YAFNET/YAFNET-DNN/releases/tag/v2.1 

NOTE: v2.x Requires .NET Framework v4.0

YAF.NET Community Appreciation Station

Super thanks to  tha_watcha !!! Special thanks to  JP ,  Zero2Cool ,  squirrel ! Thanks to the entire YAF.NET community! You guys keep YAF.NET going!

Project Move! Again!
YAF.NET is now on GitHub! https://github.com/YAFNET 

The Twitterz and Facebookz
YAF.NET Twitter is here: http://twitter.com/yafnet  and Facebook is here: http://www.facebook.com/...mNET-YAF/156302224384947 

Build It!
Building YAF.NET from source now requires Visual Studio 2010/2012/2013. YAF.NET can be build using the freely available Visual Studio 2013 Express .

---

We upgraded yesterday to v2.1. Looking good!

Great news!!!

Will not upgrade until next year, though.... 😁 😂

---

Upgraded from 2.0 to 2.1 with fixes from yesterday.

Looks absolutely great, and seems more stable than 2.0, 👍

---

Hi, I used the binary installation (https://github.com/YAFNET/YAFNET/releases/download/v2.1/YAF-v2.1-RTW-BIN.zip) to set my forum up.
After installing the forum there was the "YAF compiled in DEBUG mode" notification at the bottom of the page. The issue was fixed by building the sources in the Release configuration with subsequent replacement of the binaries received with the installation by the built ones. Original binaries also seemed to cause "Internal server error 500", which hopefully disappeared after replacing them with the newly built ones.

I also installed the RTW 2.1. But it seems a debug build.
Do we get a release build soon or does everyone needs to build the release mode themselfs? I prefer to download the release build instead of installing Visual Studio Express for Web.

(I don't know if there is a lot of #if DEBUG which slows down the process, but for me as an admin the sql performance list at the bottom is not pleasant)

- Robert

I also installed the RTW 2.1. But it seems a debug build.
Do we get a release build soon or does everyone needs to build the release mode themselfs? I prefer to download the release build instead of installing Visual Studio Express for Web.

(I don't know if there is a lot of #if DEBUG which slows down the process, but for me as an admin the sql performance list at the bottom is not pleasant)

- Robert

http://build.yetanotherforum.net/ 

That might provide you want you want.

I also installed the RTW 2.1. But it seems a debug build.
Do we get a release build soon or does everyone needs to build the release mode themselfs? I prefer to download the release build instead of installing Visual Studio Express for Web.

(I don't know if there is a lot of #if DEBUG which slows down the process, but for me as an admin the sql performance list at the bottom is not pleasant)

- Robert

http://build.yetanotherforum.net/ 

That might provide you want you want.

Yeah, but that is a daily build with an unknown status.

I downloaded Visual Studio Exress 2013 for web (I still had VS 2010) en compiled it in release mode. Copied the bin/dlls to the site and it is running.
But I hope that not all users who want V2.1.0 have to do this.

Another quick question.
I have been using YAF for years now and recently the posts read has been changed. There is an option to keep track of the read posts in the database. But there is a warning that it lets the database grow (or something like that).
Too be honest, database size is not an issue. It is over 40GB now. But how about the performance?
Is the YAF forum here (this forum) using the database option? For a large forum, is it wise to maintain it in the database?

I am using the db tracking option, the reason is to get the same read/unread status on any device that you use to login to the forum for viewing posts.

IMHO, the database tracking option is the only way to go.

---

Tried the db tracking option a few times. Each time it has failed to function as expected and reverted to the other option which works.

It's not perfect for multipage topics at the moment, no... In 1.9.6.1+ it worked fine for me also for multipage.
Will do as you for the moment.

---

Thanks for the feedback.
Two different experiences. Maybe I need to test it on the test site and see what happens. I was assuming it was/is working, but that only things might slow down due to more database access (extended queries). That is what I am afraid of

Thanks for the feedback.
Two different experiences. Maybe I need to test it on the test site and see what happens. I was assuming it was/is working, but that only things might slow down due to more database access (extended queries). That is what I am afraid of

Definitely. With my feedback, keep in mind my site went from DragonFly CMS to DotNetNuke w/YAF, to its current state of ASP.NET w/YAF so its quite possible in the flipping around over years I jagged something up quit nasty. :)

I can't recall many issues with the read/unread icons, but I have had users state such issues persist, hence why I tried db tracking several times.

Reverting back to db again, non-db did the same on me in a 178 page topic with 100 posts/page (presumably timeout)...

This last-read issue should be split into a separate topic and not reside in the YAF announcement topic.

---