[Mono-bugs] [Bug 498667] New: Scanning with stand-alone MoMA vs scanning with MoMA in MonoVS produce different results

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=498667


           Summary: Scanning with stand-alone MoMA vs scanning with MoMA
                    in MonoVS produce different results
    Classification: Mono
           Product: Mono: Tools
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Visual Studio Integration
        AssignedTo: jpobst at novell.com
        ReportedBy: mchristensen at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Description of Problem:

Scanning with stand-alone MoMA vs scanning with MoMA in MonoVS produce
different results.

The method for scanning with MonoVS is simply scanning using hte Mono Menu to
scan the project.

To scan with stand alone moma:

   1. Open Visual Studio.
   2. Open mojoportal-complete.sln
   3. Build -> Build Solution
   4. Select mojoPortal.Web in the solution Browser
   5. Build -> Publish mojoPortal.Web
   6. Choose a target directory
   7. Start stand-alone MoMA
   8. Scan the new directory


As an example, scanning with MonoVS shows only one P/Invoke while scanning with
stand alone MoMA shows 198 P/Invokes.

I'm attaching the two scans.

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