Questions for CSharpHeaven:
Where does Microsoft admit that it was a "big mistake"? Link please.
YAF does have namespaces -- so I don't see how this argument holds water for YAF. If you are griping about most "Web Site" projects, understandable, but this doesn't apply to YAF.
I knew going Web Site was not necessarily going to be a popular decision with the more established programmers.
Main reasons: Every day someone is asking how to compile YAF. YAF is an international forum. A lot of people cannot afford to compile YAF using WAP because VS2005 PRO is required. Web site design is so much easier for modifications. It means that basic (literally) programmers can change a few variables here and there and change how YAF works.
Most of the libraries still require compilation -- but not Visual Studio Pro. The WAP project was included with the source distribution. Maybe I'll come up with a way to "have it both ways" here with some automated changes. For now, I'm chosen to support the majority over the knowledgeable minority who I figured could make it WAP if they wanted.
I'm open to further dialog on this topic though. Remember, I have very limited time and resources. If you give me solutions (auto-WAP project generation script), it would help. :)
Edited by user
15 years ago
| Reason: Not specified