first of all: Great Work :!: :!: :cheesy:

I have downloaded the latest version (1.9.3) of YAF via SVN and convertet it to a Visual Web Developer 2005 Project, because there are some issues in YAF, so that it won't compile in VWD.

I hope someome find this useful.

How to install:

- decompress the RAR (sorry the upload of ZIP don't work 😞 )

- open the Folder in VWD

- goto APP_DATA -> right click -> an create an new Database named: Forum.mdf (you can rename it in the app.config)

- start the website ... done

Features:

- Moved all code in the APP_CODE-folder, now you don't need to compile the YAF.DLL because it will be automatic fully compiled by the webserver :arrow: Now it's possible to edit the source complet e.g. with notepad on your server without an installed version of visual studio or vwd, then start the page and the IIS will recompile it

- deleted the designer.cs and resx-files, because they are not needed

- changed in all ascx-files in <%@ Control ... the "Codebehind" to "CodeFile=" / created an new Class (Tools) / Fixed some bugs in the code and stored procedures

- Note that the web.config has changed; don't remove the

- updated the German translation (now 1.9.3 compatible)

EDIT: Thanks for update of German translation, I'll update it in SVN.

I have a problem related to this topic. I referenced the yaf dll in Visual Developer Express 2005, opened the code and made my customizations. Then I run it but my changes were ignored, it looks like it uses the original dll and ignores my changes. How can I recompile the dll so it contains my modifications?:?:

Thanks a lot!

Radoslav

I like your converted yaf vwd2005 version, especially breaking the big yaf.dll into readable objects. I am trying to setup your code in VS2005 and SQL2005, while I have an error message on the third install step that it could not connect to the SQL database. (The database and connectionstring are OK as I could see.) Could you please advice what could I do to make it work? Thanks a lot.

On SQL Server 2005 Standard you have to create the new database with SQL Server Management Studio (Express) and change the connect string in the app.config in something like that:

Thanks for coming back on my question.

It's right that I use the SQL server developer edition. I did not create the database as you mentioned in the intall instruction. What I did is a bit like you mentioned in your reply to my question

- I created the database using SQL server management studio, I named the database forums_yafvwd. Is the name change matters?

- then in VS 2005, I created the connectionstring in server Explorer against this database forums_yafvwd, and I copied the connection string to the connection string in web.config.

Then I put the application under IIS and lauched the application in IIS. The install goes fine until the step "Create Forum". By this step, I could see the database, views, stored procedures are all created in the database. I see them in SQL server management studio. But I could not see the triggers yet at this stage.

Then the issue comes. When I validate this step by click next, it comes the message that it could not connect to SQL server database. So I wonder the issue?

- is it because the user instance? It must matters, where I could change then?

- is it because I have to put in a real smtp? I am testing in IIS, I don't know what to put there.

Really want to make it works too in VS2005 and against SQL 2005. Thanks for further advice.

I have one question. Did you downloaded my archive from the first post? Because I had posted this archive nearly a year ago. Meanwhile the actual 1.9.3 is also compatible with VWD and you can change and build the site without compiling the yaf.dll. You can disable it in the web.config. Just download the current version via SVN.

I assume that your issue comes from missing the aspnetdb.mdf which does not exist in your database instance. In the current 1.9.3 Version the membership tables are included in the YAF database.

If this was not the solution of your issue, I think there may be a security problem in your database instance. Make sure that the autogenerated user from the IIS and the ASPNET user have enough rights in the database.

I need more member attribute than allowed by the aspnetdb, so I choose not to use the membership function. That would explain well my issue. Thanks again.

I need more member attribute than allowed by the aspnetdb, so I choose not to use the membership function.

What do you mean with "more member attributes"? Additional information for a member like postal code or gps coordinates ...? Then you may take a look at http://msdn.microsoft.com/en-us/library/2y3fs9xs(VS.80).aspx  (the keyword in ASP.NET is "Profile" ) It's also supported in YAF.

If your attributes need to be stored in multiple tables just use the MembershipUser.ProviderUserKey as foreign key in the other tables. It's a GUID wich is unique for every user.

1. I would need to plan for two types of users to login through different functional areas of the application. I do not plan to include them in the same user table. I wonder membership and profile could handle this. Or the user identification and authorization would be better done directly through custom ADO.NET codes.

2. I understand although pretty much any user attributes could be included in the Profile, all of them are inserted in a single cell and make it hard to retrieve code. The service of the application would heavily depend on the profile of each user, so I would need to be able to retrieve and regroup the user attribute easily. Then I have two choices, either using a custom profile provider or using custom ADO.NET codes and pass by Profile. I understand ADO.NET would give better flexibility.

That's pretty much where I am on this, and I would need to investigate further. If you have experience on this area, your idea is appreciated.