override form method from dll class

Question

2.00/5 (2 votes)

See more:

i want to build dll file that deals with system.windows.forms.form how can i override any form method from dll class such as (WndProc)?

C#

public partial class MyDll
{
    public MyDll(System.Windows.Forms.Form form)
    {
        // i want to override WinProc form from my dll file.
    }
}

Posted 20-Mar-14 9:47am

Rabee Rabee

Updated 20-Mar-14 9:53am

v3

Add a Solution

1 solution

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)

Sergey Alexandrovich Kryukov · Accepted Answer · 2014-03-20T10:24:00

In exact same way as it was in EXE file. There is no difference.

In .NET, the difference between "EXE" or "DLL" is almist insignificant. Everything are assemblies; and "EXE" or "DLL" files are modules (usually, main modules) of the assemblies. EXE has an entry point (Main) to be executed as an application. EXE can be used exactly as class library (referenced); and one can build some alernative hosting system where DLLs could play the roles of executable.

Let's say, you have application ("EXE"), and it uses some library ("DLL"). The best way to do it is having them in the same solution, and reference by the tab "Projects" of the "Add Reference" window (if this is Visual Studio; other environments will have similar features). Then you can simply forget about boundary between these two assemblies; write everything as it would be monolithic assembly. The only requirment is the public or protected access modifiers, to have types and members accessible in a different assembly.

However, if you want dynamically, during runtime, change some implementation by changing implementind DLL, this would much more difficult problem solved using reflection. If you are interested, we can discuss it, but it will require more serious knowledge and deeper understanding of the fundamentals.

—SA