C# dll creation and make it not editable

Question

1.00/5 (3 votes)

See more:

Hi everybody,

i create a Dll file and i use it c# project.However in c# project my dll class can editable but i dont want o someone edit my dll file.How can i fix?

Posted 9-Feb-16 1:52am

Member 10525430

Updated 9-Feb-16 2:05am

F-ES Sitecore

v2

Add a Solution

Comments

PIEBALDconsult 9-Feb-16 8:08am

"i change some line in dll files"
That makes no sense. Do you actually mean the code? Or the DLL that results from compiling it?
Even the DLL _can_ be edited in certain ways and there's nothing you can do about it. Don't spend your time worrying about such things.

Sergey Alexandrovich Kryukov 9-Feb-16 10:05am

Exactly. This short comment is better than all three answers I can see right now, because first thing is first — the inquirer does not understand the basics of programming, what compilation does, what's on input and output, forget life cycle. This needs learning.
—SA

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

OriginalGriff · Answer 1 · 2016-02-09T02:08:00

.NET DLL files are Assemblies - and that means they aren't "editable". They are readable (and always will be, even if you obfuscate the content to make it harder) because the system needs to be able to read them in order to execute the code they contain.
But they aren't "editable" in any useful sense - there is no "Assembly editor" which allows me to make changes directly to your DLL. That doesn't mean I can't edit them using a hex editor, if I know exactly what I'm doing - but they can't be changed in in teh sense of altering your code as C# and the DLL "magically" reflects that. In order for teh DLL to change, it would need to be recompiled.

So if you are "changing lines in DLL files" then that implies that you have added the DLL Project to your solution - which is fine, and allowed because you often want to develop the EXE and one or more DLL Assemblies at the same time. But it's not the only way. Backup first, then remove the Project from the Solution, and the references from the other projects. Then create a new Solution, and include the DLL Assembly as its Project. Build that for Release.
Go back to your original Solution, and add a Reference to the newly created DLL in it's Release folder using the Browse button.

Now your app will build, and will be able to use the DLL content, but it won't be able to change it.

F-ES Sitecore · Answer 2 · 2016-02-09T02:06:00

Solution 1

If you don't want someone to edit your cs file then don't give them access to it. cs files are designed to be editable so if you have people you don't want developing you need to implement some kind of code repository like SVN or GIT that has relevant access controls.

Posted 9-Feb-16 2:06am

F-ES Sitecore

Sascha Lefèvre · Answer 3 · 2016-02-09T02:08:00

Solution 3

A DLL can't be (easily) edited. You probably included the source project into your solution and that's why you can edit the source of it. If you (or someone else) just add that DLL as a reference to a project then it's not editable.

Posted 9-Feb-16 2:08am

Sascha Lefèvre