<configuration>

	<configSections>
		<section
			name="btnetSettings"
			type="System.Configuration.NameValueFileSectionHandler,System, Version=1.0.3300.0,Culture=neutral, PublicKeyToken=b77a5c561934e089" />
		<section
			name="pop3Settings"
			type="System.Configuration.NameValueFileSectionHandler,System, Version=1.0.3300.0,Culture=neutral, PublicKeyToken=b77a5c561934e089" />
	</configSections>

	<system.web>
		<compilation debug="true">
		</compilation>
		<pages validateRequest="true" />
	</system.web>

	<btnetSettings>

		<!--
			Change this to point to your database
		-->
<!--
    	<add
    		key="ConnectionString"
    		value="server=(local);database=corey;user id=Administrator;Trusted_Connection=yes"
    	/>
-->

    	<add
    		key="ConnectionString"
    		value="server=(local);database=btnet1;user id=sa;password=sa;Trusted_Connection=no"
    	/>

		<!--
			These entries control where attachment file are uploaded to and how large
			the files can be.
		-->
		<add key="UploadFolder" value="c:\temp\upload" />
		<add key="MaxUploadSize" value="1000000" />

		<!--
		From Martin:
		I added a new value to the web.config
		<add key="CultureName" value="de-DE" />
		For the US, the setting should be "en-US"!
		If no value is set the current culture info on the ASP process on the server
		is used.

		If this culture info is set correctly all parsing is done correctly.

		If you set CultureName, you don't have to set "DateTimeFormat" and 	"JustDateFormat".
		If no values are set the default settings of the culture are used.
		If "DateTimeFormat" or "JustDateFormat" are used, they overwrite the culture
		settings selected by "CultureName".
		So the bugtracker will also work completly correct without any of
		"CultureName", "DateTimeFormat", "JustDateFormat" being set.
		-->

		<!--
		<add key="CultureName" value="de-DE" />
		<add key="CultureName" value="en-US" />
		-->


		<!--
			Set the first to your local date-time format.
			Set the second to your local date format without time
		-->

		<!-- American style -->
		<add key="DateTimeFormat" value="yyyy-MM-dd h:mm tt" />
		<add key="JustDateFormat" value="yyyy-MM-dd" />

		<!-- European style
		<add key="DateTimeFormat" value="dd.MM.yyyy HH:mm" />
		<add key="JustDateFormat" value="dd.MM.yyyy" />
		-->

		<!--
		Format SQL Server expects the dates to be in
		This doesn't affect what user sees on web pages.
		-->
		<add key="SQLServerDateFormat" value="yyyy-MM-dd HH:mm:ss" />


		<!--
			You can turn the logging and emailing of errors on and off.
			Log file name is "btnet_log_yyyy_mm_dd.txt"
		-->
		<add key="LogEnabled" value="1"/>
		<add key="LogFileFolder" value="c:\temp"/>


		<add key="ErrorEmailEnabled" value="1"/>
		<add key="ErrorEmailTo" value="YOUR EMAIL HERE"/>
		<add key="ErrorEmailFrom" value="FROM EMAIL HERE"/>


		<!--
			You can "subscribe" to email notifications on a per-bug basis.
			You will receive an email whenever the bug is updated.
		-->
		<add key="NotificationEmailEnabled" value="1"/>
		<add key="NotificationEmailFrom" value="FROM EMAIL HERE"/>

		<!--
			Controls whether notifications are sent as just one
			email with a lot of recipients, or as several separate
			emails, each with one recipient.   The first way is faster.
		-->
		<add key="SendJustOneEmail" value="1"/>

		<!--
			If you aren't using the local SMTP server that comes with IIS,
			set the name, user, and password for your SMTP server here.
		-->

		<!--
		<add key="SmtpServer" value="smtp.sbcglobal.yahoo.com"/>
		<add key="SmtpServerAuthenticateUser" value="ctrager@sbcglobal.net"/>
		<add key="SmtpServerAuthenticatePassword" value=""/>
		-->

		<!--
		Specify the pickup directory if you have the problem described here:
		http://support.microsoft.com/default.aspx?scid=kb;en-us;816789#8
		-->

		<!--
		<add key="SmtpServerPickupDirectory" value=""/>
		<add key="SmtpSendUsing" value="1"/>
		-->


		<!--
		Ignore this setting unless you are esperiencing the symptoms
		related to this: http://cr.yp.to/docs/smtplf.html
		-->
		<!--
		<add key="SmtpForceReplaceOfBareLineFeeds" value="1"/>
		-->

		<!--
			Admins can do everything.
			These switches give more power to non-admins.
		-->
		<add key="AllowQueryPageForNonAdmins" value="1"/>
		<add key="AllowBugDeletionForNonAdmins" value="0"/>
		<add key="AllowCommentDeletionForNonAdmins" value="0"/>
		<add key="AllowBugMergingForNonAdmins" value="0"/>
		<add key="AllowAttachmentDeletionForNonAdmins" value="0"/>

		<!--
			Unless you know your users, you shouldn't let them put
			whatever SQL they want into the system.
		-->

		<add key="AllowQueryEditingForNonAdmins" value="1"/>

		<!--
			If category/project/status/priority are not enough bug attributes
			for you, here's one more that you can name yourself
		-->
		<add key="ShowUserDefinedBugAttribute" value="1"/>
		<add key="UserDefinedBugAttributeName" value="YourAttribute"/>


		<!--
			If you don't like seeing the SQL on the queries or search page.
		-->
		<add key="HideSql" value="0"/>


		<!--
			This controls whether entries are inserted into the bug_history table
			when the user changes description, category, priority, assigned to. or status.
		-->
		<add key="TrackBugHistory" value="1" />

		<!--
			Controls whether the bug history entries are show with the
			bug comments or seperately
		-->
		<add key="ShowHistoryWithComments" value="1"/>

		<!--
			Sort order of comments and history.
			"desc" is most recent first.
			"asc" is oldest first.
		-->
		<add key="CommentSortOrder" value="desc"/>


		<!--
			Controls whether the bug history entries are printed when
			you print bugs
		-->
		<add key="PrintHistory" value="1"/>


		<!--
			Used when creating absolute href's.  For example, in notification emails.
			Don't forget trailing slash!.
		-->
		<add key="AbsoluteUrlPrefix" value="http://127.0.0.1/btnet/"/>


		<!--

			Set WindowsAuthentication to "1" if you want to use
			windows authentication instead of the logon page.

			1) Configure your IIS virtual directory so that anon
			access is unchecked and windows authentication is checked

			2) Configure IE to automatically send username and
			password

			3) Usernames in users table should match your
			windows usernames. Passwords in users table will be
			ignored.

			If you want BOTH modes to work, set "WindowsAuthentication"
			to "2".

			Configure your IIS virtual directory as normal (allowing
			anon access).   Follow these instrunctions for the file "loginnt.aspx":

			* From IIS Manager, right-click the file loginnt.aspx and select properties
			* Select the Security tab
			* Click Edit in the Anonymous Access and Authentication frame
			* Ensure Anonymous Access and Basic Authentication is cleared
			* Ensure Integrated Windows Authentication is selected
			* Click OK
			* Select the Custom Errors tab
			* Select HTTP Error 401;2 and click Edit Properties
			* Set the message type to File and select the file login.htm, including the full local path. (Note that this must be a file	reference and not a URL)

			The idea is that when the user access default.aspx, it redirects to loginnt.aspx.
			When access to loginnt.aspx is denied, IIS resonds with the custom error login.htm.
			Login.htm then redirects to default.aspx.

		-->

		<add key="WindowsAuthentication" value="0"/>



		<!--

		When per-project permission is not specified, what is the permission?
		3 = "reporter" allow adds but after bug is added, only allow posting of additional comments
		2 = allow everything
		1 = allow view only
		0 = hide
		-->

		<add key="DefaultPermissionLevel" value="2"/>

		<!--
			Set these to control what values who up in the edit_bug.aspx page
			when adding a new bug.
		-->
		<add key="DefaultProject" value="[no project]"/>
		<add key="DefaultCategory" value="[no category]"/>
		<add key="DefaultPriority" value="[no priority]"/>
		<add key="DefaultStatus" value="[no status]"/>
		<add key="DefaultUserDefinedBugAttribute" value="[none]"/>

		<!--
		TextArea for Custom fields
		This setting is used to format custom defined fields.  If a field is greater than TextAreaThreshold, it will be
		displayed as a TextArea instead of a normal Input control.  The number of rows in the TextArea is
		determined by dividing the field length by TextAreaThreshold up to a maximum value indicated by MaxTextAreaRows.
		-->
		<add key="TextAreaThreshold" value="80"/>
		<add key="MaxTextAreaRows" value="3"/>


		<!--
		Set this to "1" if you want the passwords in the db to be stored encrypted.

		When you logon, BugTracker.NET will check the database for both the encrypted and unecrypted forms,
		so setting this on and off won't break anything.

		Passwords that are already stored aren't affected.  If you want to change what's already stored,
		you need to go the the "settings" page or "edit user" page.
		-->

		<add key="EncryptStoredPasswords" value="1"/>


		<!--
		Some folks don't like the word "bug".   These next four settings allow you to override the text of the
		logo and the word bugs.
		-->
		<add key="AppTitle" value=""/>
		<add key="SingularBugLabel" value=""/>
		<add key="PluralBugLabel" value=""/>


		<!-- customize marker for creating hyperlinks in bug comments -->
		<add key="BugLinkMarker" value="bugid#"/>

		<!--

		Uncomment this to customize the logo in the upper left.   You have to HTML encode
		all the HTML tags embedded here.

		-->
		<!--
		<add key="LogoHtml" value="&lt;td style='color: red; font-weight: bold;'&gt;Your Logo" />
		-->


		<!--
		In dropdowns featuring users, do you want to see the logon names or their full names, in
		"LastName, FirstName" format?
		-->
		<add key="UseFullNames" value="0"/>

		<!--
		In edit_bug.aspx, you can have your own link appear:
		<a href="your_url.aspx?bugid=...">YOUR LINK</a>

		You have to HTML encode any HTML tags embedded here.

		-->
		<!--
		<add key="CustomBugLinkLabel" value="YOUR LINK"/>
		<add key="CUstomBugLinkUrl" value="your_url.aspx"/>
		-->


		<!--
		You can add to the menu, just to the left of the "about" link
		You have to HTML encode any HTML tags embedded here.
		-->
		<!--
		<add key="CustomMenuLinkLabel" value="YOUR LINK"/>
		<add key="CUstomMenuLinkUrl" value="your_url.aspx"/>
		-->

		<!--
		Display your own HTML on the default.aspx page.   You have to HTML encode it here.
		-->
		<!--
		<add key="CustomWelcomeHtml" value="&lt;div style='color:red;font-weight:bold;'&gt;For demo, logon as &quot;user1&quot;, &quot;user2&quot;, or &quot;user3&quot;.&lt;br&gt;Password=&quot;guest&quot;&lt;div&gt;"/>
		-->


		<!--
			If you want replies to be generated automatically.
		-->
<!--
		<add key="AutoReplyText" value="Thanks for you email.
Don't call us, we'll call you."/>
-->

	</btnetSettings>



	<!--
		Used by btnet_service.exe and btnet_console.exe.  THese fetche messages
		from a pop3 server and stuff them into the database as bugs.   Go to admin,
		projects, and enter a pop3 username and password for each project that you
		are interested in.   One email account per project.   Don't forget to check
		the "enabled" checkbox.   THen make sure these settings are ok.

		btnet_console.exe is easier to use for getting things up and running.  It
		writes lots of little debugging error messages.    After that's working, install
		and use btnet_service.exe instead.

	-->
	<pop3Settings>
		<!--
			Replace my server with YOUR server.
		-->
		<add key="Pop3Server" value="pop.sbcglobal.yahoo.com"/>

		<!--
			BugTracker.NET username, password that btnet_server.exe will use
			to talk to BugTracker.NET.   These are not the username/password
			for the pop3 server itself - those come from the project rec in
			the projects table.
		-->
		<add key="ServiceUsername" value="email"/>
		<add key="ServicePassword" value="x"/>

		<!--
			Only retrieve messages if their subject contains the magic string below.
			If the value is blank, then btnet_pop3.exe will retrieve all messages.
			Probably for your production, the value should be blank.
		-->
		<add key="SubjectMustContain" value=""/>

		<!--
			Skip message if the subject contains the magic string below.
		-->
		<add key="SubjectCannotContain" value=""/>


		<!--
			For my own testing, it was useful to have this option.
			For production the value should be 1.
		-->
		<add key="DeleteMessagesOnServer" value="0"/>

		<!--
			How frequently should btnet_console.exe or btnet_service.exe check the server for emails?
		-->
		<add key="FetchIntervalInMinutes" value="15"/>

		<!--
			This is the setting that btnet_console.exe or btnet_service.exe uses to post the bugs
		-->
		<add key="InsertBugUrl" value="http://127.0.0.1/btnet/insert_bug.aspx"/>

		<!--
			For diagnosing problems, dump the message text to a file
		-->

		<add key="MessageOutputFile" value="c:\temp\btnet_test_messages_out.txt"/>


		<!--
			For testing, read the message text from a file rather than from
			a POP3Server.

			Seperate multiple messages in the file with a line like this:
			Q6Q6

			Maximum of 100 test messages.
		-->
		<!--
		<add key="MessageInputFile" value="c:\temp\btnet_test_messages_in.txt"/>
		-->

	</pop3Settings>

</configuration>