[Mono-bugs] [Bug 688794] NullReferenceException in GetCustomEncoderFromConfig on new ASP.Net MVC webapp

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Apr 21 04:59:47 EDT 2011



Marek Habersack <mhabersack at novell.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |NEEDINFO
       InfoProvider|                            |cinyc.s at gmail.com

--- Comment #3 from Marek Habersack <mhabersack at novell.com> 2011-04-21 10:59:46 CEST ---
(In reply to comment #2)
> Created an attachment (id=426014)
 --> (http://bugzilla.novell.com/attachment.cgi?id=426014) [details]
> Test case for xsp4
> I'm attaching an xsp4 testcase (basically, the "skeleton" set of files that
> MonoDevelop generates).  You should be able to replicate by:
Thanks, but unfortunately the test case is not what I asked for - I need the
app/test ready to run (i.e. with bin/*.dll). I need to have the _exact_ piece
of software that fails for you. I cannot reproduce it otherwise (created the
sample app as you described, it works fine both on Mono/master and Mono/2.10)

> 1. tar jxvf MVCHTTP.tar.bz2 && cd MVCHTTP && xsp4 --applications :/.
> 2. Visit http://localhost:8080
> 3. Switch back to the console, you should see the exception stack trace.
> Unfortunately, outside of MonoDevelop, the exception gets reported as being in
> <filename unknown>.  I don't know how to replicate the MonoDevelop stacktrace
> behaviour in a self-contained, standalone way.
Changing your web.config <compilation> element to say 'debug="true"' and
running XSP like this will do that:

MONO_ENV_OPTIONS="--debug" xsp4

> Sorry about setting the severity, I didn't know that I should have left that
> field alone.
It's ok, this is quite a confusing option :)

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list