how to link dll with exe
-
hi , i am a beginner.i want to make a dll file and link it with an exe.the dll files should have functions and exe file should call and run those functions.but i dont know how.this may help me a lot.please correct me if i am going in wrong way.i am using visual c# express 2010
Unless you have a good reason for having a DLL, it is much easier just to create an executable, in order to get used to the structure of a program and how it fits together. Once you have all your code working then you can always separate parts out into a DLL if necessary. However, remember that a DLL is only any use if it is likely to be shared by multiple applications.
Use the best guess
-
Unless you have a good reason for having a DLL, it is much easier just to create an executable, in order to get used to the structure of a program and how it fits together. Once you have all your code working then you can always separate parts out into a DLL if necessary. However, remember that a DLL is only any use if it is likely to be shared by multiple applications.
Use the best guess
Richard MacCutchan wrote:
However, remember that a DLL is only any use if it is likely to be shared by multiple applications.
I'd be prepared to argue against that point! :laugh: I often use a single EXE and separate DLLs to hold the different assemblies of a project: DL and BL for example, or to separate logical segments to reduce any "accidental" interactions. The EXE is just the final PL as far as I am concerned, with even the user controls that make up the UI separated out into a different DLL (and assembly)
The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
hi , i am a beginner.i want to make a dll file and link it with an exe.the dll files should have functions and exe file should call and run those functions.but i dont know how.this may help me a lot.please correct me if i am going in wrong way.i am using visual c# express 2010
It's pretty easy - or at least it is in the Pro version of VS210, I don't have the Express version. So if any of this doesn't work, let me know... :laugh: Open your solution, and look at the Solution Explorer pane. Right click your solution name, and select "Add...New Project..." from the drop down list. In the dialog, Select "Class Library" from the middle panel, and give it a sensible Name. Press OK. Build your solution. Now, open your EXE project in the Solution Explorer pane, and right click the "References" branch. Select the "Add Reference..." option. In the dialog the appears, select the "Projects" tab from the list on the left, then select your new DLL project on the right. Press the "Add" button. Done! You can now use classes in the DLL project in your EXE project. (You may want to add the appropriate
usingstatement to your code files)The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
Richard MacCutchan wrote:
However, remember that a DLL is only any use if it is likely to be shared by multiple applications.
I'd be prepared to argue against that point! :laugh: I often use a single EXE and separate DLLs to hold the different assemblies of a project: DL and BL for example, or to separate logical segments to reduce any "accidental" interactions. The EXE is just the final PL as far as I am concerned, with even the user controls that make up the UI separated out into a different DLL (and assembly)
The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
It's pretty easy - or at least it is in the Pro version of VS210, I don't have the Express version. So if any of this doesn't work, let me know... :laugh: Open your solution, and look at the Solution Explorer pane. Right click your solution name, and select "Add...New Project..." from the drop down list. In the dialog, Select "Class Library" from the middle panel, and give it a sensible Name. Press OK. Build your solution. Now, open your EXE project in the Solution Explorer pane, and right click the "References" branch. Select the "Add Reference..." option. In the dialog the appears, select the "Projects" tab from the list on the left, then select your new DLL project on the right. Press the "Add" button. Done! You can now use classes in the DLL project in your EXE project. (You may want to add the appropriate
usingstatement to your code files)The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
It's pretty easy - or at least it is in the Pro version of VS210, I don't have the Express version. So if any of this doesn't work, let me know... :laugh: Open your solution, and look at the Solution Explorer pane. Right click your solution name, and select "Add...New Project..." from the drop down list. In the dialog, Select "Class Library" from the middle panel, and give it a sensible Name. Press OK. Build your solution. Now, open your EXE project in the Solution Explorer pane, and right click the "References" branch. Select the "Add Reference..." option. In the dialog the appears, select the "Projects" tab from the list on the left, then select your new DLL project on the right. Press the "Add" button. Done! You can now use classes in the DLL project in your EXE project. (You may want to add the appropriate
usingstatement to your code files)The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
It's pretty easy - or at least it is in the Pro version of VS210, I don't have the Express version. So if any of this doesn't work, let me know... :laugh: Open your solution, and look at the Solution Explorer pane. Right click your solution name, and select "Add...New Project..." from the drop down list. In the dialog, Select "Class Library" from the middle panel, and give it a sensible Name. Press OK. Build your solution. Now, open your EXE project in the Solution Explorer pane, and right click the "References" branch. Select the "Add Reference..." option. In the dialog the appears, select the "Projects" tab from the list on the left, then select your new DLL project on the right. Press the "Add" button. Done! You can now use classes in the DLL project in your EXE project. (You may want to add the appropriate
usingstatement to your code files)The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
Looking at these messages[^], OP is either a very fast learner or just going through every language until he/she finds one that he/she can understand.
Use the best guess
Gawd! Looks like he did a two week course in C++ in May and then panicked... Interesting choice of project to start with "develop your own language" - they didn't give us that on day one of the first year! (They didn't even get us to write a BASIC interpretter until year 3)
The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
Why aren't you out in the sunshine frolicking in the meadows with your sheep? Me; I'm just gathering my strength for a cycle ride to Windsor and back this afternoon.
Use the best guess
Cause I've spent the day hoovering, fixing the hoover, cleaning out the hoover so the damn thing sucks properly, cleaning the bathroom, dumping dead vermin in the river and hoovering up the remains, etc., etc. And I've got to pick Herself up from work in an hour, then wash the car this arvo before cooking supper.
The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
hi , i am a beginner.i want to make a dll file and link it with an exe.the dll files should have functions and exe file should call and run those functions.but i dont know how.this may help me a lot.please correct me if i am going in wrong way.i am using visual c# express 2010
-
Unless you have a good reason for having a DLL, it is much easier just to create an executable, in order to get used to the structure of a program and how it fits together. Once you have all your code working then you can always separate parts out into a DLL if necessary. However, remember that a DLL is only any use if it is likely to be shared by multiple applications.
Use the best guess
no not like ur wrong guess.i m
-
no not like ur wrong guess.i m
