[Mono-bugs] [Bug 643763] New: BuildProvider.SetVirtualPath is not called when BuildProvider has no BuildProviderAppliesToAttribute

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=643763

https://bugzilla.novell.com/show_bug.cgi?id=643763#c0


           Summary: BuildProvider.SetVirtualPath is not called when
                    BuildProvider has no BuildProviderAppliesToAttribute
    Classification: Mono
           Product: Mono: Class Libraries
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: kornelpal at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Community User
           Blocker: ---


Created an attachment (id=393024)
 --> (http://bugzilla.novell.com/attachment.cgi?id=393024)
BuildManagerDirectoryBuilder.patch

Description of Problem:
ArgumentNullException in Dictionary.ContainsKey in
BuildManagerDirectoryBuilder.AddBuildProvider because BuildProvider.VirtualPath
is null.

Steps to reproduce the problem:
1. Create a simple BuildProvider that has no BuildProviderAppliesToAttribute.
2. Register in Web.config
3. Access a path that triggers the BuildProvider.

Actual Results:
ArgumentNullException

Expected Results:
No problem

How often does this happen? 
Always

Additional Information:
Adding BuildProviderAppliesToAttribute to the BuildProvider resolves the
problem.

The actual problem is in BuildManagerDirectoryBuilder.GetBuildProvider that
BuildProvider.SetVirtualPath is not called when BuildProvider has no
BuildProviderAppliesToAttribute.

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