Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:multiasm:exercisesbook:pc [2026/06/11 10:10] – [Visual Studio Community solution with static assembly library] pczekalski | en:multiasm:exercisesbook:pc [2026/06/11 10:11] (current) – [Standalone assembly] pczekalski | ||
|---|---|---|---|
| Line 158: | Line 158: | ||
| After finishing all the steps, we should be able to properly compile the solution and observe results in a console window. | After finishing all the steps, we should be able to properly compile the solution and observe results in a console window. | ||
| + | ===== Dynamic lib in C++ ===== | ||
| + | |||
| + | ===== Dynamic lib in C# ===== | ||
| + | |||
| ===== Standalone assembly ===== | ===== Standalone assembly ===== | ||
| It is possible to use command-line MASM tools to assemble, link, and create libraries written in assembly language. You can use any editor to create the assembler source code and translate it into machine code. The tools required are integral elements of the Visual Studio Community installation, | It is possible to use command-line MASM tools to assemble, link, and create libraries written in assembly language. You can use any editor to create the assembler source code and translate it into machine code. The tools required are integral elements of the Visual Studio Community installation, | ||
| Line 187: | Line 191: | ||
| The easiest way is to put all required files in the same folder on the disk. This is not the case for more complex projects, so file names should be preceded by their full paths. | The easiest way is to put all required files in the same folder on the disk. This is not the case for more complex projects, so file names should be preceded by their full paths. | ||
| </ | </ | ||
| - | |||
| - | |||
