>>1) web.config file:
-I'm surprised to see this: <compilation defaultLanguage="c#" debug="true"/
Shouldn't debug be set to false by default or are you expecting your customers to change this manually? Can I ask which mode (release or debug) was used when you compiled the solution and created the dll files (sampleportal.dll and  CuteSoft.Chat.dll)?

The above line can help us help the client debug the problem when they install cute chat.  You can remove that line after you install it successfully.

 

The DLLs are created using release mode.

 

>>2) Database:
-In one of the posts in the forum (http://cutesoft.net/forums/thread/26787.aspx) you said that the application requires database owner permissions. In reality the application only needs select/update/delete/insert permissions on the tables created by the SQL script (CutechatStandalone.sql).

You are correct. DB ower permission is a short answer.

 

>>Why don't you use stored procedures? I understand that CuteChat can be used against different types of databases (SQL Server, Oracle, etc.) but surely it's possible to use stored procedures if you connect to SQL Server and access direcly the tables if you connect to a different type of database. That would also simplify the permissions required.

 

In the framework of Cute Chat, we have a provider system which allow support different databases. Aother issue is the performance issue.

 

>>3)Documentation:

 

We will improvde our documentation. Sorry for the inconvenience.

For the connection string issue, please check the following code:

 

'Retrieves the Cute Chat database connection string
Public Function GetConnectionString(ByVal user As CuteSoft.Chat.UserIdentity) As String Implements CuteSoft.Chat.IHttpApplicationConnectionStringProvider.GetConnectionString

Code Example

Public Function GetConnectionString(ByVal user As CuteSoft.Chat.UserIdentity) As String Implements CuteSoft.Chat.IHttpApplicationConnectionStringProvider.GetConnectionString

    Return System.Configuration.ConfigurationSettings.AppSettings("SiteSqlServer")

End Function

 

>>I'm also getting confused with the configuration page of the administation console. I've just set 'Show Room List' to false but the room lists still appear. Am I doing anything incorrectly? Is this a bug? If so, is it documented somewhere?

Where did you find 'Show Room List'? You can set a chat room to hidden in Room Administration page/

 

>>My users are already logged in so I don't want them to have to login again. I'm using vb.net

 

Integration with an existing user membership database

 

 

 

Hope it helps.  Let me know if you have any further questions.