The system uses 2 connection strings. One for the system (to store the ads) and one for members (User registration). While the source code works with Microsoft SQL Server, there is no reason it would not work with SQL Server Express. The basic rule is that you need to use either SQL Server 2008 or SQL Server Express 2008, or better.

The name of the system database connection string is oplacoConnection:

<add name="oplacoConnection" connectionString="Data Source=(local);Initial Catalog=Oplaco_SYS;User ID=YOUR_USERID_HERE;Password=YOUR_PASSWORD_HERE" providerName="System.Data.SqlClient"/>

The name of the member database connection string is oplacoMembersConnection:

<add name="oplacoMembersConnection" connectionString="Data Source=(local);Initial Catalog=Oplaco_USR;User ID=YOUR_USERID_HERE;Password=YOUR_PASSWORD_HERE" providerName="System.Data.SqlClient"/>

Now there is no reason to use those names. However if you want to change the names to something else, keep in mind that you need to modify the web.config on all places where the connectionstrings are used.
On top of that, you also need to change the following:

In the core project:

Ads.Designer.cs – InitConnection method.
Categories.Designer.cs – InitConnection method.
Locations.Designer.cs – InitConnection method.
Members.Designer.cs – InitConnection method.
Stats.Designer.cs – InitConnection method.


Oplaco’s membership is based on the .NET membership & role providers. Defining how registration is done, is set in the web.config.



In order to use the mail components, you could use the Gmail smtp server;

      <smtp from="" deliveryMethod="Network">
        <network defaultCredentials="false" enableSsl="true" host="" port="587" password="yourpassword" userName=""/>

Last edited Jan 24, 2011 at 7:05 AM by chefdog, version 1


No comments yet.