This is the actual server application. Extract the zip file into a folder, then web share that folder with the alias NETnotifier. Now you can access the WSDL interfaces by pointing your browser to http://localhost/NETnotifier.
You could of course, if you had a SQL Server 2000 database configured correctly. If you don’t, there are two ways to get around this little snag:
- Use the sample Access database included in the data subfolder. To have the server using that database, comment as needed the following lines in web.config:
<add key= “conn”value=”Provider=Microsoft.Jet.OLEDB.4.0; Data Source=c:\myfolder\NETnotifier\data\NETnotifier.mdb” />
<!– sql server –>
<add key= “conn”value=”Provider=sqloledb;Data Source=localhost;Initial Catalog=NETnotifier;Integrated Security=SSPI;” />
Of course, change c:\myfolder\ to the folder where you have extracted the zip file.
- Configure a SQL Server 2000 database. Create a NETnotifier database in an instance of SQL Server 2000, then import the tables and data from the sample Access database. Remember to grant dbo_owner permissions to the ASPNET user.
To test if the application is correctly installed, point a browser to http://locahost/NETnotifier/user.asmx and call the Login method using test/test as username/password. If everything is configured correctly, you should receive back a return status and a GUID.
Congratulations, you have a copy of NETnotifier running.