Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Behavior of Assembly.GetTypes() changed in Visual Studio 2015

Tags:

I opened our solution in Visual Studio 2015 yesterday and a few of our unit tests (which ran fine in Visual Studio 2013) starting failing. Digger deeper I discovered it was because calling GetTypes() on an assembly was returning different results. I've been able to create a very simple test case to illustrate it.

In both Visual Studio 2013 and 2015 I created a new console application using .NET Framework 4.5.2. I put the following code in both projects.

class Program {     static void Main(string[] args)     {         var types = typeof(Program).Assembly.GetTypes()                 .Where(t => !t.IsAbstract && t.IsClass);          foreach (var type in types)         {             Console.WriteLine(type.FullName);         }          Console.ReadKey();     } } 

When I run in Visual Studio 2013 I get the following output (as expected).

VS2013Example.Program

When I run in Visual Studio 2015 I get the following output (not as expected).

VS2015Example.Program

VS2015Example.Program+<>c

So what is that VS2015Example.Program+<>c type? Turns out it's the lambda inside the .Where() method. Yes, that's right, somehow that local lambda is being exposed as a type. If I comment out the .Where() in VS2015 then I no longer get that second line.

I've used Beyond Compare to compare the two .csproj files but the only differences are the VS version number, the project GUID, names of the default namespace and assembly, and the VS2015 one had a reference to System.Net.Http that the VS2013 one didn't.

Has anyone else seen this?

Does anyone have an explanation as to why a local variable would be being exposed as a type at the assembly level?

like image 918
Craig W. Avatar asked Jul 21 '15 14:07

Craig W.


People also ask

How to specify Assembly information in Visual Studio?

Specifying Assembly Information in Visual Studio 1. Select the project in Solution Explorer > Right Click > Properties > Application Tab 2. Click the Assembly Information button 3. This will open the Assembly Information dialog box.

What happens if the gettypes method is called on an assembly?

If the GetTypesmethod is called on an assembly and a type in that assembly is dependent on a type in an assembly that has not been loaded (for example, if it derives from a type in the second assembly), a ReflectionTypeLoadExceptionis thrown.

What happens if I change the version of my runtime Assembly?

If you create a new version of your strong-named runtime assembly, the client program doesn't have to be recompiled. The client program continues to use whichever version of the runtime assembly is available to it, using the embedded type information for the public interfaces.

How do I update the assembly information for my project?

1. Select the project in Solution Explorer > Right Click > Properties > Application Tab 2. Click the Assembly Information button 3. This will open the Assembly Information dialog box. You will find the same information, for every field corresponding to AssemblyInfo.Cs file. The Updated information will also reflect the AssemblyInfo.Cs.


1 Answers

Has anyone else seen this?

Yes, this is caused by the new compiler behavior for lifting lambda expressions.

Previously, if a lambda expression didn't capture any local variables, it would be cached as a static method at the call site, which made the compiler team need to jump some hoops in order to properly align the method arguments and the this parameter. The new behavior in Roslyn is that all lambda expressions get lifted into a display class, where the delegate is exposed as an instance method in the display class, disregarding if it captures any local variables.

If you decompile your method in Roslyn, you see this:

private static void Main(string[] args) {     IEnumerable<Type> arg_33_0 = typeof(Program).Assembly.GetTypes();     Func<Type, bool> arg_33_1;     if (arg_33_1 = Program.<>c.<>9__0_0 == null)     {         arg_33_1 = Program.<>c.<>9__0_0 =                          new Func<Type, bool>(Program.<>c.<>9.<Main>b__0_0);     }     using (IEnumerator<Type> enumerator = arg_33_0.Where(arg_33_1).GetEnumerator())     {         while (enumerator.MoveNext())         {             Console.WriteLine(enumerator.Current.FullName);         }     }     Console.ReadKey(); }  [CompilerGenerated] [Serializable] private sealed class <>c {     public static readonly Program.<>c <>9;     public static Func<Type, bool> <>9__0_0;     static <>c()     {         // Note: this type is marked as 'beforefieldinit'.         Program.<>c.<>9 = new Program.<>c();     }     internal bool <Main>b__0_0(Type t)     {         return !t.IsAbstract && t.IsClass;     } } 

Where's with the old compiler, you'd see this:

[CompilerGenerated] private static Func<Type, bool> CS$<>9__CachedAnonymousMethodDelegate1;  private static void Main(string[] args) {     IEnumerable<Type> arg_34_0 = typeof(Program).Assembly.GetTypes();     if (Program.CS$<>9__CachedAnonymousMethodDelegate1 == null)     {         Program.CS$<>9__CachedAnonymousMethodDelegate1 =                              new Func<Type, bool>(Program.<Main>b__0);     }     IEnumerable<Type> types =                 arg_34_0.Where(Program.CS$<>9__CachedAnonymousMethodDelegate1);      foreach (Type type in types)     {         Console.WriteLine(type.FullName);     }     Console.ReadKey(); }  [CompilerGenerated] private static bool <Main>b__0(Type t) {     return !t.IsAbstract && t.IsClass; } 

You can get the desired result by filtering out classes that have the CompilerGenerated attribute attached to them:

var types = typeof(Program)             .Assembly             .GetTypes()             .Where(t => !t.IsAbstract &&                           t.IsClass &&                           Attribute.GetCustomAttribute(                             t, typeof (CompilerGeneratedAttribute)) == null); 

For more, see my question Delegate caching behavior changes in Roslyn

like image 198
Yuval Itzchakov Avatar answered Feb 12 '23 16:02

Yuval Itzchakov