further polished edit_bug.aspx - CODE BEHIND (cbmod11b)

Late update:

- After publishing this I found two locations that had my local
customizations in this code that should not be part of public code.
Those places that I fixed are:
- Line 801-802 in edit_wi.asp.cs (disables SVN revisions from showing)
- Line 892-893 in edit_wi.aspx.cs (disables Merge bug from showing)
The new file patch is btnet349_cbmod11B_2011-04-27_2355.zip

maintainable code-behind version of edit_bug.aspx as edit_wi.aspx and edit_wi.aspx.cs for BT.NET 3_4_9

well, fixed one more mistake :), this time it was on the comment section only

This CBMOD11B version has today been installed in our real development ecosystem. The environment in question consists of 10+ users and about 5+ active projects. The Bugtracker.net features we are not using just yet(!) are: SCM (svn,git) integrations, LDAP, Windows authentication, Merge bugs (because of automated time tracking merging gets more complicated), voting-feature, "seen"-feature and the email input and may be something that I don't remember right now:). We utilize workflow.cs to show only status-selections that are appropriate for the situation and with this CBMOD11 to also show custom configurable help-texts for each category . These help texts specify the purpose of each category (=when should it be used) and what information should be either filed when submitting the work item and/or have been produced as a work product at the time when the work item is checked in. And yes, we are using the system for all kind of work items: bugs are just one category.

- this code still contains some unnecessary warning comments section about issues that do not exist anymore (so these warnings are false alarms)
- I will probably continue to make small ( mainly cosmetical/ layoyut / standards compliance type of ) improvements to this code during the next few days or a week.

- I am continuing improvements to the CBMOD11B. The new package will come out as CBMOD11C later, I guess within 1 week or so from now
- while doing this I found out that the name "edit_bug.aspx" is pretty much hard-coded into at least 3(+) files and I want to support (to ease up everybody's development and testing) having two paraller "edit_bug" page versions available under the bt.net at least so, that swapping between them would be at least not more difficult than changing one setting line in the web.config. This means that App_Code\print_bug.cs and App_Code\bug_list.cs need to be developed further too.
- I will add HTML/CSS standards compliancy to the items that I encounter in the files I need to touch. I already fixed all of them from the edit_wi.aspx/.aspx.cs code
- I am of course making the changes so, that any existing code calling the App_Code -classes and methods would work just the same as before improvements.

Preview of new web.config settings related to increased - yet easy - configurability

- added a preview (screenshot file) of new flexiblity enhancing settings for the web.config. These support for example customizable starting page (where the user lands right after a login), customizable bug/item list pages and customizable edit bug/item page too. All other BT.NET code would work seamlessly with the customized and third party (other open source software) pages when these are in effect. Yet, these great configurability extensions are - I claim so - very easy to understand, so to my mind they do not add complexity at such amount, that you could even say one word about it :)

- I have published "cbmod11c" preview 1 here:
https://sourceforge.net/tracker/?func=detail&aid=3296523&group_id=66812&atid=1214931