Visual Studio 2026 not building .lib file in dll project

Question

Visual Studio 2026 not building .lib file in dll project

Sahil Dash 0

Hello! As the title states, I have set up a vs dll project, but when i build the project, only a dll file is generated; there is no .exp or .lib files. I have gone online to find a fix for this, but all of the fixes included something I already did, like adding the (proj name)_EXPORTS preprocesser definition and the __dllspec(dllexport) and import macro, so I hope you guys can help me. This is the first time i've asked a question on this sort forum, so i dont know exactly how much information to give, but basically, my dll project builds into a dll and lib file which is then used by another project in the same solution (and so the other project can't build because there is no .lib file). If you need any other info to help me, like source code screenshots or anything else, just tell me, as I wish to go back to working on my project asap. Thanks!

2 answers

Your answer

Answer 1

Viorel 125.7K

Try this setup: go to New Project, select C++, Windows Desktop Wizard, enter name and press Create. Then select Dynamic Link Library (dll), select Export Symbols.

The compiled files will include .dll, .lib, .exp. If it works, then add your functions, remove the samples.

Sahil Dash 0 Reputation points

2025-12-11T04:50:47.39+00:00

Um, im not sure what you mean by that? do you mean create a new solution? or an empty c++ project? I don't see any "Windows Desktop Wizard" option. If it helps, i'm using vs26. Thanks though!
Viorel 125.7K Reputation points

2025-12-11T06:30:40.6933333+00:00

First, you can experiment with a new solution.

Make sure that “Desktop development with C++” is selected in Visual Studio Installer.

Answer 2

Adiba Khan 1,520 Microsoft External Staff

Thanks for reaching out. This normally occurs then the project is missing export definitions on certain configuration settings.

Ensure At least one function/class is exported from the DLL the import library(.llb) is only generated if exported symbols exist in your DLL make sure your header uses __declspec(dllexport)
```
   #ifdef MYDLL_EXPORTS
   #define MYDLL_API __declspec(dllexport)
   #else
   #define MYDLL_API __declspec(dllimport)
   #endif
   MYDLL_API void MyFunction();
```
Then Define MYDLL_EXPORTS in the project settings: Project properties -> C/C++ -> Preprocessor -> Preprocessor Definitions -> add:
```
   MYDLL_EXPORTS
```
If no exports exist, Visual Studio will not generate a .llb file.
Verify the project type Ensure you created: Project Type: Dynamic link library(DLL) Not:
1. Empty project
2. Static Library
3. Console App
Check: Project -> Properties -> General -> Configuration Type = Dynamic Library (.dll)
Check if the .llb file output path is correct Go to: Project properties -> Linker -> General ->Output file And Project Properties -> Linker -> General -> Import Library The default import library path is:
```
   $(OutDir)$(ProjectName).lib
```
If the import library field is empty, add the above value.
Check for “No import library” setting Go to: Linker -> Advanced -> No import library Ensure it is set to:
```
   No
```
If set to yes, the .llb will never be generated
Clean and rebuild Try: Build-> Clean solution Build-> Rebuild solution

Additional notes

Visual Studio generates .exp and .lib files only when you export at least one symbol
If you are using module (.def) files. Ensure exports are correctly defined.

Please let us know if you require any further assistance we’re happy to help. If you found this information useful, kindly mark this as "Accept Answer".

Viorel 125.7K Reputation points

2025-12-11T09:11:46.6533333+00:00

Maybe $(OutDir)$(ProjectName).lib should be changed to $(OutDir)$(ProjectName).llb?
Sahil Dash 0 Reputation points

2025-12-11T23:16:24.7666667+00:00
I tried/checked everything you said, but it still does not work.

I have defined this macro in my project's header files:

#ifdef MPIC_EXPORTS #define MPIC_API __declspec(dllexport) #else #define MPIC_API __declspec(dllimport) #endif

and here is an excerpt of one of my header files' code:

MPIC_API class Engine { private: Window window; Renderer renderer; SceneManager sceneManager; bool running = true; public: void Run(Scene* scene); };

As you can see, I am using that macro, and i also use that macro on all of my other classes and such, but still nothing is getting compiled. If you need me to send any other info, just tell me.
Adiba Khan 1,520 Reputation points Microsoft External Staff

2025-12-12T06:55:14.1966667+00:00
Thank you for sharing the macro definition and header excerpt. Since the.lib file is still not being generated even with the proper __deslspec(dllexport) usage You need to check a few additional areas that can prevent Visual Studio from producing the import library.

Confirm that at least one exported symbol is implemented in a .cpp file in your header, you have:
MFIC_API void Run(Scene* scene);
please make sure the corresponding implementation is written in a .cpp file with the same macro:
#include "Engine.h" void Engine::Run(Scene* scene) { // implementation }
if the method is declared but never defined, Visual Studio will not create a .lib because it finds 0 valid exports. This is one of the most common causes

ensure the macro MFIC_EXPORTS is actually defined in the DLL project go to: project properties-> C/C++-> preprocessor -> preprocessor definitions ensure it contains:
MFIC_EXPORTS
if this macro is missing, every symbol becomes dllimport , and the .lib will not be generated.

Verify that your project is not set to “no import library" go to: linker-> advanced -> no import library make sure it is:
NO
if this setting is “Yes”, the build system will intentionally skip creating the .lib

ensure the import library path is not empty go to: linker-> general-> import library expected default value:
$(OutDir)$(ProjectName).lib
if this field is empty Visual Studio outputs only the .dll and .exp files.

Check if your class is being exported correctly When exporting a class, make sure the macro applied to the class itself:
class MFIC_API Engine { //.... }
you are already doing this which is correct however, if any member function is declared in line inside the class Visual Studio may not treat them as exported to avoid inline exports stripping the .lib ensure key functions (e.g., constructor, destructor, public methods) are implemented in .cpp files.

Check for /GL whole program optimization issue if you enabled whole program optimization or link time code generation manually, it can remove exports. Go to: C/C++-> optimization-> whole program optimization-> disable linker-> optimization-> link time code generation-> default

try creating a minimal test export to verify, add a simple exported function: EngineExports.h:
extern "C" MFIC_API int TestExport();
EngineExports.cpp:
#include "EngineExports.h" int TestExport() {return 1;}
rebuild your solution. if the .lib appears, the issue is inside the class export structure.

Please let us know if you require any further assistance we’re happy to help. If you found this information useful, kindly mark this as "Accept Answer".

Share via

Visual Studio 2026 not building .lib file in dll project

2 answers

Your answer