Assembly names

An assembly’s name is stored in metadata and has a significant impact on the assembly’s scope and use by an application. A strong-named assembly has a fully qualified name that includes the assembly’s name, culture, public key, version number, and, optionally, processor architecture. Use the FullName property to obtain the fully qualified name, frequently referred to as the display name, for loaded assemblies.

The runtime uses the name information to locate the assembly and differentiate it from other assemblies with the same name. For example, a strong-named assembly called myTypes could have the following fully qualified name:

In this example, the fully qualified name indicates that the myTypes assembly has a strong name with a public key token, has the culture value for United States English, and has a version number of 1.0.1234.0. Its processor architecture is msil , which means that it will be just-in-time (JIT)-compiled to 32-bit code or 64-bit code depending on the operating system and processor.

The ProcessorArchitecture information allows processor-specific versions of assemblies. You can create versions of an assembly whose identity differs only by processor architecture, for example 32-bit and 64-bit processor-specific versions. Processor architecture is not required for strong names. For more information, see AssemblyName.ProcessorArchitecture.

Code that requests types in an assembly must use a fully qualified assembly name. This is called fully qualified binding. Partial binding, which specifies only an assembly name, is not permitted when referencing assemblies in .NET Framework.

All assembly references to assemblies that make up .NET Framework must also contain the fully qualified name of the assembly. For example, a reference to the System.Data .NET Framework assembly for version 1.0 would include:

The version corresponds to the version number of all .NET Framework assemblies that shipped with .NET Framework version 1.0. For .NET Framework assemblies, the culture value is always neutral, and the public key is the same as shown in the above example.

For example, to add an assembly reference in a configuration file to set up a trace listener, you would include the fully qualified name of the system .NET Framework assembly:

The runtime treats assembly names as case-insensitive when binding to an assembly, but preserves whatever case is used in an assembly name. Several tools in the Windows SDK handle assembly names as case-sensitive. For best results, manage assembly names as though they were case-sensitive.

Name application components

The runtime does not consider the file name when determining an assembly’s identity. The assembly identity, which consists of the assembly name, version, culture, and strong name, must be clear to the runtime.

For example, if you have an assembly called myAssembly.exe that references an assembly called myAssembly.dll, binding occurs correctly if you execute myAssembly.exe. However, if another application executes myAssembly.exe using the method AppDomain.ExecuteAssembly, the runtime determines that myAssembly is already loaded when myAssembly.exe requests binding to myAssembly . In this case, myAssembly.dll is never loaded. Because myAssembly.exe does not contain the requested type, a TypeLoadException occurs.

To avoid this problem, make sure the assemblies that make up your application do not have the same assembly name or place assemblies with the same name in different directories.

File or assembly name system windows forms

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Have problems with Visual Studio 2019, where I have created a solution with 2 projects. The start-up project (# 1) has been created with the Console App (.NETCore) as a base. The second project (# 2) is based on the Windows Forms app (.NET Framework)

Project 1 contains the main logic and calls a procedure in project 2 that will set up a form, take care of specified values ​​and return this via global variables. Both projects do their jobs separately. It is when it comes to the call that errors occur. The call has been adapted as the initial syntax error occurred which has now been corrected so compilation of the solution is error free and without warnings. When executed, there is an interruption

System.IO.FileNotFoundException: ‘Could not load file or assembly ‘System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′. Det går inte att hitta filen.’

This means that it is not possible to track in the program as I wanted. Of course, there are differences in the two projects’ .NET environments that make up for it, but it is not told how I can get hold of the missing file.

Question 1. Does anyone know how to get the file and how it is then incorporated into the environment?

I am not a VB encoder so that with Objects, classes, methods etc. is not something I have immersed myself in. However, I can do so much that I can make it work as regular calls with arguments and so on.

The call itself is simple in itself and I think I got to that with how to send the information. However, I do not find anywhere the values ​​that the parameters should contain.

Call MYform1.Form1_Load(Mysender, Myargs)

Question 2. Does anyone know how to find which values ​​should be included in the Mysender and Myargs parameters

In the log I find this

‘Project20200727.exe’ (CoreCLR: DefaultDomain): Loaded ‘C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.6\System.Private.CoreLib.dll’.

‘Project20200727.exe’ (CoreCLR: clrhost): Loaded ‘C:\Users\janne\source\repos\Project20200727\bin\Debug\netcoreapp3.1\Project20200727.dll’. Symbols loaded.

‘Project20200727.exe’ (CoreCLR: clrhost): Loaded ‘C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.6\System.Runtime.dll’.

‘Project20200727.exe’ (CoreCLR: clrhost): Loaded ‘C:\Users\janne\source\repos\Project20200727\bin\Debug\netcoreapp3.1\WindowsApp3_20200730.exe’. Symbols loaded.

An unhandled exception of type ‘System.IO.FileNotFoundException’ occurred in Unknown Module.

Could not load file or assembly ‘System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089’. Det går inte att hitta filen.

The program ‘[13828] Project20200727.exe’ has exited with code -1 (0xffffffff).

Как в консольный проект подключить System.Windiws.Forms

System.Collections.IEnumerable; как его подключить?
int badhands ;//: System.Collections.IEnumerable; badhands =new int .

Как подключить System.Reactive вместе с mscore.dll?
Вообщем проблема такая, есть код: public IObservable .

Как подключить справку в формате pdf в проект
Нужно, чтобы по нажатии на кнопку вызывалась справка, а она в формате pdf Как это организовать?

Подключить DirectShow в Windows Forms Application (Visual Studio 2008)
Доброго время суток. Помогите подключить DirectShow в Windows Forms Application (Visual Studio.

Спасибо всем. А не подскажите как убрать «черный екран смерти» что-бы видно было только формы при запуске, а то я по книге не совсем догнал..

Добавлено через 2 минуты
kirill29, а как сделать следующе на си шарп:

Спасибо всем. А не подскажите как убрать «черный екран смерти» что-бы видно было только формы при запуске, а то я по книге не совсем догнал..

Добавлено через 2 минуты
kirill29, а как сделать следующе на си шарп:

1);
System.Windows.Forms.Application.Run(new Form1());

2)
System.Collections.Stack stack;
stack=new System.Collections.Stack()
//stack.Peek
//stack.Push
//stack.Pop
System.Console.Write(«10 konstruktorov»);

Спасибо, с этим разобрался. Но у меня есть еще вопросы:
есть ли в си шарпе вектора как в си++, или хотябы заменители..

Добавлено через 5 минут
как узнать длину строки? Допустим есть строка String s = «dfsdfsdf»; как узнать ее длину? и как обратиться к и-ому символу этой строки?

Добавлено через 1 минуту

мне больше понравился стек произвольных пипов))

Добавлено через 1 минуту
List<> — а где он должен быть (пространство имен)

Добавлено через 6 минут
как переписать этот клас, что-бы он работал?

Создай тот и другой на 1000000 элементов и сравни производительность.

Добавлено через 39 секунд

Error 1 The type or namespace name ‘List’ could not be found (are you missing a using directive or an assembly reference?) C:\Documents and Settings\Администратор\Мои документы\Visual Studio 2008\Projects\Project1\Project1\CodeFile1.cs 14 13 Project1

Добавлено через 21 секунду
HIMen, где он должен быть? я его у себя не нашел..

Alligieri, а можно как-то создать лист с Н элементами, значение которых К ?? Не прогоняя лист в цыкле

Добавлено через 18 минут

Заказываю контрольные, курсовые, дипломные и любые другие студенческие работы здесь или здесь.

Не удается подключить System.Threading.Tasks
Здравствуйте! Подскажите как подключить System.Threading.Tasks. Не удается объявить.

подключить Java class в проект C#
Доброго дня всем! Подскажите пожалуйста, каким образом подключить несколько классов Java (есть и.

Can’t use System.Windows.Forms

I have tried making (my first) a C# program:

This goes well, but if I try using System.Windows.Forms:

This is the error I get:

Some details: — I am using Visual Studio 2012; — I have installed the .NET Development Kit; — It is a Console Application.

Maybe it’s because on a Console Application can’t use System.Windows.Forms? If so, what program should be? I also have tried with a form, but I was only displaying a window and no code.

8 Answers 8

A console application does not automatically add a reference to System.Windows.Forms.dll.

Right-click your project in Solution Explorer and select Add reference. and then find System.Windows.Forms and add it.

You have to add the reference of the namespace : System.Windows.Forms to your project, because for some reason it is not already added, so you can add New Reference from Visual Studio menu.

Right click on «Reference» ▶ «Add New Reference» ▶ «System.Windows.Forms»

To add the reference to «System.Windows.Forms», it seems to be a little different for Visual Studio Community 2017.

1) Go to solution explorer and select references

2) Right-click and select Add references

Windows Form Designer: Could not load file or assembly

Has anyone ever had the issue where trying to «View Designer» on a windows form in Visual Studio .NET causes the error: «Could not load file or assembly…» ?

In this case, the assembly in question was XYZ.dll . I managed to fix this by adding XYZ.dll and all its references to my project’s references (even though my project doesn’t directly depend on them) and rebuilding the whole solution. However, after that, I removed all those references from my project, rebuilt, and it still worked.

One other piece of information is that I use Resharper 2.5. Someone else pointed out that it might be Resharper doing some shadow copying. I’ll look into this next time this happens. Does anyone have a understanding of why this error happens in the first place, and possibly the ‘correct’ way to fix it?

22 Answers 22

We have same problem. Some Form/UserControl classes can not be viewed in designer and Visual Studio causes various exceptions.

There are one typical cause: One of designed component thrown unhandled exception during initialization ( in constructor or in Load event or before ).

Not only for this case, you can run another instance of visual studio, open/create some independent project, go to menu -> Debug -> Attach to process . -> select instance of devenv.exe process with problematic designer. Then press Ctrl+Alt+E, the «Exceptions» windows should be shown. There check «Thrown» in categories of exception.

Now active the visual studio with designer and try view designer. If the exception will be thrown, you will see callstack ( and maybe source code, if the exception was thrown from your code ) and other typical information about thrown exception. This information may be very helpful.

This is an old question that still appears to have no answer, either here or in the wider forum pool, most advice relates to relentless clean>rebuilds or close>clean folders>reopen or restarting the machine. I don’t have a solid answer at present though have done some research into it and thought I might share. Summarily, there is one location into which all designer files are copied when a control or form is designed, another location which old files can exist and a method is described to catch all designer exceptions before the designer can generate the error page.

There appears to be two cases where either an assembly cant be loaded or can’t be found. The first is caused by files failing to copy to designer-required locations, the second is outdated files being left behind.

As mentioned above files can fail to copy when a project fails to directly reference all references required by its referenced references and their references, recursively, down to the framework. This can be alleviated by carefully tracking all references and their dependents, ensuring all are accounted for.

The Visual Studio designer uses a specific location to cache dlls for its use in the designer, isolated from the source /bin folders of the projects:

C:\Documents and Settings\[user_name]\Local Settings\Application Data\Microsoft\VisualStudio\10.0\ProjectAssemblies

C:\Users\[user_name]\AppData\Local\Microsoft\VisualStudio\10.0\ProjectAssemblies

In this location, compiled assemblies are copied to dynamically created folders, one folder per assembly. Checking the assembly version dates on this location, it seems to be quite up to date, being deleted when visual studio exits. All assemblies are copied when a designer is viewed with newly compiled files. A new copy of each assembly is made into this location for each designer, so the location may hold multiple identical copies of each assembly.

One other location exists however where assemblies may be copied, and is a part of the assembly search sequence, apparently ahead of the ProjectAssemblies folder and that is in:

C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE

I have no knowledge of how or when assemblies get copied to this location, but it is not often so what files do arrive here quickly become a source of outdated references. When a designer failed with the ‘Failed to load file or assembly’ error, the version sought by the designer was a version only referenced by the assembly at this location.

This was discovered by using a second Visual Studio instance debugging on the first, with all .net symbols loaded, and all known exceptions breaking on throw as opposed to when unhandled. This allowed the second instance to intercept the handled designer exceptions and reveal that file location. This was the resulting output of the designer error that I used: