Table Of Contents
General BugNET Issues
Pre-installation System Requirements
- IIS Web Server 5 or later
- Microsoft .NET Framework v2.0 Redistributable
- Microsoft Report Viewer Redistributable 2005
- Microsoft ASP.NET AJAX 1.0
- Microsoft SQL Server or Microsoft Desktop Engine (MSDE) version 2000 or later
Installing BugNET
- Unzip the latest BugNet install package to a folder (e.g c:\BugNet) of your choice. This is the required package to run the BugNet Issue tracker. For the full source code package, visit the BugNET website.
- Make sure you have created a virtual directory on your local IIS which points to the folder that you have extracted the files in step 1 (e.g C:\BugNet). (e.g the url should be http://localhost/BugNet)
- Using Windows Explorer, browse to the root folder of the website ( C:\BugNet by default ). Right-click the folder and select Sharing and Security from the popup menu ( please note that if you are using Windows XP you may need to Enable Simple File Sharing before these options are displayed ). Select the Security tab. Add the appropriate User Account and set the Permissions.
If using Windows 2000 - IIS5
- the {Server}\ASPNET User Account must have Read, Write, and Change Control of the virtual root of your website
If using Windows 2003 - IIS6
- the NT AUTHORITY\NETWORK SERVICE User Account must have Read, Write, and
Change Control of the virtual root of your website
- Create a blank SQL Database (e.g db name 'BugNet') on your sql server. For the upgrade, before you take any action, please backup your database.
- Edit the Web.config file with a text editor of your choice. Find the LocalSqlServer connection string setting and change the connectionString property to match the database you created in step 4.
- Edit the Log4net.config file in the Config folder and set the connection string to the same one that you have used in step 4.
- Browse to http://localhost/BugNet/Install/Install.aspx (or the url of the virtual directory you have created in step 2).
- The installation process will now start.
- When completed, you may log in with the admin user account.
Username: admin
Password: password
That's it, your BugNet Issue tracker installation should be up and running at http://localhost/BugNet. For any installation problems, please visit the Support Forums.
Upgrading BugNET
Upgrading From Version 0.7.X
- Backup your existing installation of BugNet, your database and rename your web.config to web.config.bak.resources
**NOTE: Be sure to rename the web.config with the resources extension or someone could potentially download your web.config file.
- Delete the existing files in your current installation with the exception of your backup of the Web.config the Uploads directory and your App_Data folder (if you are using sql express)
- Unzip the latest BugNet install package into your existing install directory.
- Copy your connection string from your previous Web.config to the new one.
- Copy your machinekey elements from your old Web.config to the new one.
- Copy the installation date appsetting from the old Web.config to the new one.
- Browse to http://localhost/~BugNet/Install/Install.aspx to complete the upgrade.
Upgrading From Version 0.6.7
- Backup your existing installation of BugNet and your database.
- Unzip the latest BugNet install pacakge overtop of your existing install.
- Make sure that the current Admin account password is at least 7 characters long. If not, run this script replacing YourPasswordHere with the password you wish to use.
UPDATE Users SET Password = `YourPasswordHere` WHERE UserName = `Admin`
- Make sure that all users have a unique email address, otherwise the upgrade will fail. Run this script to determine duplicates and fix them accordingly:
SELECT email,
COUNT(email) AS NumOccurrences
FROM users
GROUP BY email
HAVING ( COUNT(email) > 1 )
- Unzip the latest BugNet install package to a folder (e.g c:\BugNet) of your choice. This is the required package to run the BugNet Issue tracker. For the full source code package, visit the BugNet website.
- Edit the Web.config file with a text editor of your choice. Find the LocalSqlServer connection string setting and change the connectionString property to match the database you created in step 4.
- Edit the Log4Net.config file in the Config folder and set the connection string to the same one that you have used in step 4.
- Browse to http://localhost/BugNet/Install/Install.aspx (or the url of the virtual directory you have created in step 2).
- The upgrade process will now start.
- When completed you may log in as normal.
To configure windows authentication you will need to follow the steps below:
- Log into your BugNET installation as the admin account
- Add a new user with the domain\username that you wish to be the admin and add them to the super users role.
- Change the authentication in the web.config to windows authentication
- In IIS, edit the configuration for the virtual directory uncheck anonymouse access and make sure windows authentication is checked.
- Visit the application with the logged on domain user that you created earlier and you should have admin access now.
To enable seamless creation of users from Active Directory or Windows SAM when they visit the application then you will need to perform these additional steps.
- Log into the BugNET issue tracker as admin
- Goto the Administration -> Application Configuration -> Authentication Settings section.
- Set your User Account Source, Active Directory or Windows SAM
- Enter your domain in the Domain field. i.e MyDomain.
- If your domain needs authentication to lookup users enter the username and password in the proper fields.
- Locate the AuthenticationModule http module tag in the web.config and uncomment it.
Known Issues
For a list of known issues please visit http://support.bugnetproject.com.
Version History
For a version history please refer to the change log.
Acknowledgements
Thank you to everyone that has reported issues, submitted patches and your continued support.