Re: [Ikvm-developers] Suggestion popups in visual studio with internal packages.

[Jeroen F. <je...@su...>]

Hi Dawid,

It turns out to be a known Visual Studio bug:
http://connect.microsoft.com/VisualStudio/feedback/details/587408/intellisense-shows-empty-namespaces-when-using-assembly-internalsvisibleto

It's amazing how they always manage to fail to meet even my low expectations.

Regards,
Jeroen

> -----Original Message-----
> From: daw...@gm... [mailto:daw...@gm...] On Behalf Of
> Dawid Weiss
> Sent: Saturday, October 01, 2011 09:51
> To: Jeroen Frijters
> Cc: ikvm-developers
> Subject: Re: [Ikvm-developers] Suggestion popups in visual studio with
> internal packages.
> 
> Hi Jeroen,
> 
> Yes, I checked all the things you mentioned -- that's why it's so
> frustrating. Let me send you the problematic assembly off the list.
> 
> Dawid
> 
> On Sat, Oct 1, 2011 at 9:12 AM, Jeroen Frijters <je...@su...>
> wrote:
> > Hi Dawid,
> >
> > I have to ask the obvious question first, are you sure the assembly
> doesn't have an InternalsVisibleToAttribute for the assembly that you're
> editing in Visual Studio (or possibly an InternalsVisibletoAttribute
> that VS might misinterpret).
> >
> > AFIAK, that's the only mechanism that allows non-public classes to be
> visible.
> >
> > Also, it could be a simple Visual Studio caching bug, if you've only
> recently made the change. It wouldn't surprise me if the Intellisense
> stuff is cached somewhere in a database in the solution.
> >
> > If you use one of these non-public classes and then build do you get
> the expected compile error?
> >
> > Regards,
> > Jeroen
> >
> >> -----Original Message-----
> >> From: Dawid Weiss [mailto:daw...@cs...]
> >> Sent: Saturday, October 01, 2011 09:02
> >> To: ikvm-developers
> >> Subject: [Ikvm-developers] Suggestion popups in visual studio with
> >> internal packages.
> >>
> >> Hi everyone,
> >>
> >> I have a task to investigate but I thought maybe somebody already has
> >> a solution/ answer to this. The problem we have is this:
> >>
> >> 1) we compile a Java JAR with ikvmc, making a single package public
> >> (using ikvmc publicpackage directive).
> >> 2) everything works fine, classes in other packages are marked
> >> internal,
> >> 3) visual studio still _does_ come up with a suggestion drop list
> >> when typing in the "internal" namespaces even if there's nothing
> >> public in them (and once you get to the package level where classes
> >> reside the combo is empty).
> >>
> >> Visual Studio 2010, didn't check any other versions. This does not
> >> happen with C# assemblies as far as I can tell. More: this also
> >> doesn't happen on simple Java examples (when I tried to isolate the
> problem).
> >> Are there any special attributes or namespace data you can think of
> >> that may be causing this? I'll dig, but wanted to make sure I'm not
> >> duplicating work.
> >>
> >> Thanks,
> >> Dawid
> >>
> >> ---------------------------------------------------------------------
> >> ---
> >> ------
> >> All of the data generated in your IT infrastructure is seriously
> >> valuable.
> >> Why? It contains a definitive record of application performance,
> >> security threats, fraudulent activity, and more. Splunk takes this
> >> data and makes sense of it. IT sense. And common sense.
> >> http://p.sf.net/sfu/splunk-d2dcopy2
> >> _______________________________________________
> >> Ikvm-developers mailing list
> >> Ikv...@li...
> >> https://lists.sourceforge.net/lists/listinfo/ikvm-developers
> >
> >