Random assembly names

[Mike Hildner]

My apps always seem to have two loaded assemblies that have random 8 character names, but always the same version. Notice the first and last items in the attached pic.

I can't seem to find any good info on where these are coming from. Anybody know?

Thanks,
Mike

Edit: Here's the code I use to load the ListView

        private void DisplayLoadedAssemblies()
        {
            Assembly[] assemblies = AppDomain.CurrentDomain.GetAssemblies();
            foreach (Assembly a in assemblies)
            {
                AssemblyName an = a.GetName();
                ListViewItem item = new ListViewItem(an.Name.ToString(), 0);
                item.SubItems.Add(an.Version.ToString());
                this.lvAssemblies.Items.Add(item);

                Debug.WriteLine(a.ToString());
            }
        }

[Kasracer]

Post your Application's Assembly

[Mike Hildner]

Post your Application's Assembly

ok, now I feel stupid What do you mean my application's assembly? My application gets compiled into a .exe - surely you don't mean that? Or you mean the AssemblyInfo.cs?

Thanks,
Mike

[Kasracer]

AssemblyInfo.cs is what I mean

[Mike Hildner]

Here it is.

[Kasracer]

Wow that's wierd. Your assembly looks fine to me.

I got no idea. Maybe someone else will?

If it's possible, you could upload the entire solution and I would try to build it.

[Mike Hildner]

Thanks for taking a look. Unfortunately I'm not allowed to upload the entire solution. It'd be quite the burden anyway, as it's complex with lots of references to our own frameworks, application blocks etc.

I googled like crazy trying to find any info on this and could not. But I've got it narrowed down a little. I can see that a dynamically named assembly gets added to the end of list immediately after I call a web service for the first time.

Thinking about this a little more, I was at a talk once on XML serialization and the speaker was talking about what happens. .NET will output a .cs file and compile that using cs.exe on the fly. This is (at least one reason) why cs.exe is part of the .NET redistributable.

Interestingly, there's an entry you can make in your .config file that preserves the newly created assembly to make future stuff happen faster - I can't remember what that is, though.

Mike