Application output file (.exe) should change to (.dll) on build in visual studio 2008

Question

1.00/5 (2 votes)

See more:

VS2008

, +

I have a project that is made on windows form and returns output (.exe) but i want it to return output file in (.dll).
The reason why i want it in dll file is because this software has some additional features which every user shouldn't posses.

Note:- i cannot change projects output type from windows application to console because later i need to run that file.

Please feel free to ask me if you have any query regarding this question.

Thanks in advance

Posted 9-Jun-15 3:32am

agent_kruger

Updated 9-Jun-15 3:41am

v2

Add a Solution

Comments

[no name] 9-Jun-15 9:49am

"Please feel free to ask me if you have any query regarding this question", okay so what is the problem exactly?

agent_kruger 9-Jun-15 10:14am

problem is that i want to convert my exe file to dll file on building the project

[no name] 9-Jun-15 10:32am

No that is not a problem at all. Why are you unable to change the project type or write a simple rename script in the build event? "I want" is not a description of any kind of a problem. And, what you want to do makes no sense anyway.

agent_kruger 10-Jun-15 9:30am

I explain the whole situation. i have 2 project in a solution 1st is the main and core application which has all the calculations in it and second project has some piece of code that just corrupts the software (as per my requirement). so i made the second application as windows application too.So, at the time when i need to corrupt the software the other exe corrupts the main software and that is why i need the 2nd project exe to be hidden so that user doesn't crash the main software by mistake.

[no name] 11-Jun-15 7:31am

And? That still doesn't make any sense at all. There probably no reason at all for you to do any of this. And making self destructing software is unethical IMO.

CHill60 9-Jun-15 9:53am

If you want a DLL why are you trying to change it to console?
"later I need to run that file" ... what file?

agent_kruger 9-Jun-15 10:14am

i am not trying to change it to console but i want my app kind of hidden so i need to change the extension at build

agent_kruger 10-Jun-15 9:30am

I explain the whole situation. i have 2 project in a solution 1st is the main and core application which has all the calculations in it and second project has some piece of code that just corrupts the software (as per my requirement). so i made the second application as windows application too.So, at the time when i need to corrupt the software the other exe corrupts the main software and that is why i need the 2nd project exe to be hidden so that user doesn't crash the main software by mistake.

Richard MacCutchan 9-Jun-15 9:54am

So change you project to create a DLL and not an executable.

agent_kruger 9-Jun-15 10:15am

no i cant read the note part in the question. it says i cant do so coz the application would need a physical path to run or my code need a place to locate to fire the application

CHill60 9-Jun-15 10:24am

It's very difficult to understand what you are trying to do.

Are you just trying to prevent certain users from using specific parts of your application. Do you think that by renaming the executables this will "hide" them from users?

agent_kruger 10-Jun-15 9:30am

I explain the whole situation. i have 2 project in a solution 1st is the main and core application which has all the calculations in it and second project has some piece of code that just corrupts the software (as per my requirement). so i made the second application as windows application too.So, at the time when i need to corrupt the software the other exe corrupts the main software and that is why i need the 2nd project exe to be hidden so that user doesn't crash the main software by mistake.

CHill60 10-Jun-15 9:33am

Just leave it as an executable but don't provide a shortcut to it as part of your install. Stick it in a sub-folder if you need to. But any user who randomly runs executables on their PC without knowing what they are deserves everything they get.

agent_kruger 10-Jun-15 9:34am

no my users are cranky and opens any executable files they see that is why i am changing it to dll

CHill60 10-Jun-15 9:39am

As I said - then they deserve what happens.
In the meantime rename the file after it has been built to something other than .exe (and I suggest anything other than .dll)

agent_kruger 10-Jun-15 9:51am

if i rename it manually each time after build there might be a chance that i forget to rename it and it is also not possible to remember renaming it everytime and i cannot risk customers data to get corrupted. any other suggestion my dear friend?

CHill60 10-Jun-15 10:08am

Don't do it manually. Use a build event[^] or use a custom event[^] in your setup project

agent_kruger 10-Jun-15 10:12am

btw i don't use setup i install manually

CHill60 10-Jun-15 10:16am

Then use a build event. Or put the rename step into your install batch file or onto your install checklist. If you don't have either of those then I strongly recommend that you do one of the three (setup project, batch file or checklist - in that order)

agent_kruger 10-Jun-15 10:29am

what actually does build event do? can we specify a specific task to it?

CHill60 10-Jun-15 10:51am

It allows you to do things before or after each build - run batch files, change manifest etc. Look at the documentation in the link from my comment above. More detail at jeremybytes[^] blog

Richard MacCutchan 9-Jun-15 10:28am

Sorry, that makes no sense. You sound as though you are confused about the difference between a DLL and an EXE. I suggest you start by creating a new DLL project, and copy in the code that you need from the existing application.

agent_kruger 10-Jun-15 9:26am

i know how the dll works but i want the application to be hidden until the code is fired to make it exe again

agent_kruger 10-Jun-15 9:30am

I explain the whole situation. i have 2 project in a solution 1st is the main and core application which has all the calculations in it and second project has some piece of code that just corrupts the software (as per my requirement). so i made the second application as windows application too.So, at the time when i need to corrupt the software the other exe corrupts the main software and that is why i need the 2nd project exe to be hidden so that user doesn't crash the main software by mistake.

Richard MacCutchan 10-Jun-15 12:00pm

Sounds rather silly to me. But hey ho, if that's what you want to waste time with then it's your funeral when it all goes wrong.

1 solution

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2015-06-09T04:26:00

Application type should be "class library".

Yes, I mean it. And then, in a library, you don't need entry point (static Main method). But if you leave it there, the library will still work: you can reference it in other application and then use the forms from your DLL. Technically, the only different feature if DLL is: it is not required to have this method.

You need to understand that in .NET there is no fundamental difference between .EXE and .DLL. The central concept is assembly, and PE files are modules. An assembly can have more than one module, but Visual Studio directly supports creation of only one per assembly. And then assemblies can reference each other. I can tell you more: even if you leave your .EXE as is, it can be referenced by some other assembly exactly as .EXE. There are even cases when doing so makes some practical sense, for example, simple plug-in architectures.

—SA

Application output file (.exe) should change to (.dll) on build in visual studio 2008

1 solution

Solution 1

Add your solution here

Preview 0

Application output file (.exe) should change to (.dll) on build in visual studio 2008

1 solution

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us