The default YAF Membership provider is mostly to allow for backwards (upgradability) from older versions of YAF -- which was not possible with the default asp.net membership.

Also, the YAF providers have built-in caching for speed.

Hi Jaben,



I knew that was coming. I'm sure I read about it on the blogs of the developers who work for Microsoft. They normally reflect what is going on inside of Microsoft. Also since i'm working on an add-in there are issues with the web site model that is not well supported and is difficult to work with. This is probably was behind what I said about the admitting part. In my project I gave up using the automation model that was offered for being too basic. I wasn’t trying to exaggerate about it mate.



I'm very happy with that. It would make the conversion much easier.



Those who produce never have enough time. So I can say the same thing too. I only can try to see if I can come up with a generic solution when I have the time.

BTW, did you get my email that I sent to you a while back? I used the email being shown on your main site mate.

I appreciate the hard work you've been putting in this project.

I just re-sent the email to you. The original email was sent on 02/12/2007.

Great work on 1.9.3.

Maybe this is a stupid question regarding membership and roles (hopefully not). Can someone help me understand how user data will be stored in the YAF DB if a different membership provider is used? I have seen this topic posted numerous times, but would appreciate further direction.

My Problem:
- Existing users/registration/login (with SQL backend) in a separate web application (classic ASP).
- Want to use YAF forum, but use existing SQL user login in different DB than the YAF DB.
- Do not want to expose password retrieval or registration or profile update to users since user data will be stored in existing SQL DB.

Do I need to maintain user information in both DBs?

I hear ya -- but all of those arguments cannot go up against the big one: YAF main UI should be simple to modify. What do I say to people who cannot modify the basic UI because they don't have 600 USD to buy Visual Studio Pro? Plus, the project is NOT all Web Site -- most of the code isn't. Just the UI/Pages code -- which I feel is a decent trade-off.

Update with fixes such as the user suspend issue and RSS issue. (Plus all the other little bugs posted...)

Root Key in app.config now supports "~/forum" for the application root.

I'm on vacation next week so I won't be looking on the board much or working on YAF.

Happy Holidays to everyone.

I just downloaded 1.9.1 source, and installed Web Application Project (WAP) add-on to VS2005 Pro so I could open the solution (working in a corporate environment, I cannot install SP1 for VS2005 without forcing other developers to do the same). I am looking to deploy a forum on the company's intranet, which already requires the users to authenticate there. So it looks like I will want to download 1.9.3 to do this. Based on my initial, limited, experience with YAF, I have the following questions/comments:

1). Could Jaben or one of the other core developers take a few minutes to update the Roadmap on the Wiki? It still shows 1.9.3 as a Q3 2007, 1.9.5 as Q4 2007 etc. for projected release dates. Having accurate projected release dates and summary of proposed features/enhancements is helpful to anyone evaluating YAF and whether it does or will soon meet the needs of the person/company looking to use it.

2). Moving away from the WAP methodology not only benefits users the do not have VS2005 Pro, but also benefits folks in corporations that are not using VS2005 SP1. In my specific case, I have administrative rights to my machine and was able to download and install WAP myself. But some corporate environments could be so restrictive that even installing WAP to VS2005 might require going through a lengthy approval process. While 1.9.1 is still the offical release, could there be a note or disclaimer that WAP or VS2005 SP1 is required to properly work with the solution if you choose to download the source?