BugNET

I have the app unzipped and sitting in a subfolder of my site, and the site's set as an application with the default settings for pool and pipeline (integrated). This site happens to have one other application installed, but that's not relevant. IIS7, latest build, Vista, the SQL database is 2008, latest build, hosted elsewhere.

The search feature here isn't returning me answers on this, so sorry if this has already been done, but here we go. Please shout if there's an easier way to do this... Navigate to the BugNET subdirectory...

(1) "There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined"

I'd have thought this should just work, with the web.config as shipped, but it doesn't, so I've not understood how applications work well enough. No matter, in the web.config I remove the scriptResourceHandler and also the webServices group, both of which are dupes from my main site's web.config. Save the file, return to the web page...

(2) Then it barfs on the modules and handlers, which look like the standard IIS7 stuff I'll already have, so I comment those out too.

A quick refresh, and bang, I discover this ships with customErrors on ... and something's still broken, so I turn them off, hit F5...

(3) "Section or group name 'system.web.extensions' is already defined"

Well of course it is, so I take that out of the application's web.config, and hit F5... grind, grind...

(4)  The connection name '*xxxx' was not found in the applications configuration or the connection string is empty.

Ah, that's because the app clears the connexion strings out, and I have a role provider which uses one (I can see this in the error message). Ok, I disable the role provider in BugNET, although actually I'd like to only allow users who are "Developers" to access it, but I will worry about that later. Role Manager disabled, F5..

(5) Parser Error:  The base class includes the field 'progress1', but its type (System.Web.UI.UpdateProgress) is not compatible with the type of control (System.Web.UI.UpdateProgress).

I know what sort of thing causes that, but I'm starting to think that either someone out there already did this and has a list of the stuff I need to do, or no one did it, in which case I need to find a different bug tracking tool..... anyone out there done this, which is basically to run BugNET as an application within a subdirectory, using the parent site's membership provider?

Thanks... although I actually tried that before. This time I tried harder (having restored the web.config and made sure the site's been well and truly restarted).

That ought to work though - I must be missing something. On IIS7, I convert the directory to an application, specifying the classic asp pool, but again I get a 500.19 error, "There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined" as before. So it's not isolating the application somehow. Perhaps this is my problem with IIS7 rather than a BugNET problem - I will look in other places for an answer, although I've got other applications (eg BlogEngine.NET) which work precisely this way. Hmm.

thanks - I'll post if I can figure out what it is.

(update: I tried clreating a new classic-mode app pool and using that, but it makes no odds.)

Ok, so I can get rid of all the stuff the parent site already has, hack hack hack. No problem there, and I can whittle it down to errors like:

The base class includes the field 'ScriptManager1', but its type (System.Web.UI.ScriptManager) is not compatible with the type of control (System.Web.UI.ScriptManager).

Ok, so that's an ajax doobrie; I commented out or back in the lines for the AjaxControlToolkit and  asp extensions, then I noticed that you're using:

 <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0,

Where as my VS2008 likes to use, and used for this site:

<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0,

So that's probably where this problem is - it don't fly with asp.net 3.5. Is that correct? If it is, has anyone made it work with asp.net 3.5? I'm sure it can be done..

 Here we go: http://www.bugnetproject.com/Forums/tabid/54/forumid/5/postid/2426/scope/posts/Default.aspx

 Ok, so you need 1-5 above, then fix as per above link, which works fine as far as it goes.

 (6) Now it barfs: "An attempt to attach an auto-named database for file [...]". But I know my connexion strings are good as they're inherited from the parent. Hmm.

Ok, so that could be some Vista/ IIS7 thing, so I stick it back onto Mosso/Rackspace to try the new hacked web.config there...

(7) " Could not load type 'BugNET.Global'." on the global.asax.cs

Okay, I'll search for that.