DLLs

[Visual Boodu .NET]

Is there any way I can prevent people using my DLLs in their programs? I
mean, I'm new to making DLLs and I'm guessing that if I can reference my
DLLs in my projects then there is nothing stopping anyone else from
referencing my DLLs in their projects.

Also, Just wondering whether there is a type of *thing* which is like a DLL
but includes a form as well. I want to include modules in my app, so say
for example purposes my app contains a main form and a calculator module.
The main form is the exe and the calculator gets called from a separate file
when needed? Any ideas?

Thanks for the help.

[Auric__]

On Fri, 28 May 2004 08:35:01 GMT, Visual Boodu .NET wrote:

Is there any way I can prevent people using my DLLs in their programs? I
mean, I'm new to making DLLs and I'm guessing that if I can reference my
DLLs in my projects then there is nothing stopping anyone else from
referencing my DLLs in their projects.
Nothing that can't be bypassed by a determined cracker. You could have
your DLL look in the registry for something, look for another
preexisting file, require a password (either fixed or determined by
something within the user's system), etc. - basically, do the same
things that commercial programs do - but again, crackers bypass this on
a daily basis. (Although they usually crack apps to use the app, not
just one specific file.)
Also, Just wondering whether there is a type of *thing* which is like a DLL
but includes a form as well. I want to include modules in my app, so say
for example purposes my app contains a main form and a calculator module.
The main form is the exe and the calculator gets called from a separate file
when needed? Any ideas?

I don't usually store forms in DLLs but I would assume that it can be
easily done; others here will have that answer.
--
auric underscore underscore at hotmail dot com
*****
Obviously our captor underestimated the wrath of a man and his hamster.

[mayayana]

You can put forms in a DLL and call them. There's no
limitation.
For restriction: Somewhere on MSDN there's a page
about how to make a control licensed, the same way
that VB controls are licensed and can't be run otherwise.
I don't have a link to it, though. Another option might be
something like a dummy parameter. Your DLL parameters
can be seen in an object browser but that doesn't explain
them. So besides the natural difficulty in figuring out how
to call a function given object browser info., you could also
make it more confusing by adding a dummy parameter,
naming the parameters in a vague way, etc.

--
--
Visual Boodu .NET <[e-mail]> wrote in message
news:VQ******** ********@news-server.bigpond. net.au...

Is there any way I can prevent people using my DLLs in their programs? I
mean, I'm new to making DLLs and I'm guessing that if I can reference my
DLLs in my projects then there is nothing stopping anyone else from
referencing my DLLs in their projects.

Also, Just wondering whether there is a type of *thing* which is like a DLL but includes a form as well. I want to include modules in my app, so say
for example purposes my app contains a main form and a calculator module.
The main form is the exe and the calculator gets called from a separate file when needed? Any ideas?

Thanks for the help.

[Visual Boodu .NET]

Auric__ wrote:

On Fri, 28 May 2004 08:35:01 GMT, Visual Boodu .NET wrote:

Is there any way I can prevent people using my DLLs in their
programs? I mean, I'm new to making DLLs and I'm guessing that if I
can reference my DLLs in my projects then there is nothing stopping
anyone else from referencing my DLLs in their projects.
Nothing that can't be bypassed by a determined cracker. You could have
your DLL look in the registry for something, look for another
preexisting file, require a password (either fixed or determined by
something within the user's system), etc. - basically, do the same
things that commercial programs do - but again, crackers bypass this
on a daily basis. (Although they usually crack apps to use the app,
not just one specific file.)

Thanks, yea I didn't think of that. Might be a good idea me thinks!

Also, Just wondering whether there is a type of *thing* which is
like a DLL but includes a form as well. I want to include modules
in my app, so say for example purposes my app contains a main form
and a calculator module. The main form is the exe and the calculator
gets called from a separate file when needed? Any ideas?

I don't usually store forms in DLLs but I would assume that it can be
easily done; others here will have that answer.

[Visual Boodu .NET]

mayayana wrote:

You can put forms in a DLL and call them. There's no
limitation.
For restriction: Somewhere on MSDN there's a page
about how to make a control licensed, the same way
that VB controls are licensed and can't be run otherwise.
I don't have a link to it, though. Another option might be
something like a dummy parameter. Your DLL parameters
can be seen in an object browser but that doesn't explain
them. So besides the natural difficulty in figuring out how
to call a function given object browser info., you could also
make it more confusing by adding a dummy parameter,
naming the parameters in a vague way, etc.
How do I put a form in a DLL? Probably if I make vague functions & that
then I'll probably get confused! I'll check out MSDN for that licencing
thing. Thanks for your help.
--

Is there any way I can prevent people using my DLLs in their
programs? I mean, I'm new to making DLLs and I'm guessing that if I
can reference my DLLs in my projects then there is nothing stopping
anyone else from referencing my DLLs in their projects.

Also, Just wondering whether there is a type of *thing* which is
like a DLL but includes a form as well. I want to include modules
in my app, so say for example purposes my app contains a main form
and a calculator module. The main form is the exe and the calculator
gets called from a separate file when needed? Any ideas?

Thanks for the help.

[Auric__]

On Fri, 28 May 2004 20:50:07 GMT, Visual Boodu .NET wrote:

Auric__ wrote:

On Fri, 28 May 2004 08:35:01 GMT, Visual Boodu .NET wrote:

Is there any way I can prevent people using my DLLs in their
programs? I mean, I'm new to making DLLs and I'm guessing that if I
can reference my DLLs in my projects then there is nothing stopping
anyone else from referencing my DLLs in their projects.

Nothing that can't be bypassed by a determined cracker. You could have
your DLL look in the registry for something, look for another
preexisting file, require a password (either fixed or determined by
something within the user's system), etc. - basically, do the same
things that commercial programs do - but again, crackers bypass this
on a daily basis. (Although they usually crack apps to use the app,
not just one specific file.)

Thanks, yea I didn't think of that. Might be a good idea me thinks!

Yes, well, just remember that crackers can bypass *any* protection
scheme if they have reason to.
--
auric underscore underscore at hotmail dot com
*****
Jennifer Lopez wears enough diamonds to blind a city block.

[Visual Boodu .NET]

Yea, thats fine, I think I would feel honoured if I saw my app on some
cracker page :)

Auric__ wrote:

On Fri, 28 May 2004 20:50:07 GMT, Visual Boodu .NET wrote:

Auric__ wrote:

On Fri, 28 May 2004 08:35:01 GMT, Visual Boodu .NET wrote:

Is there any way I can prevent people using my DLLs in their
programs? I mean, I'm new to making DLLs and I'm guessing that if
I can reference my DLLs in my projects then there is nothing
stopping anyone else from referencing my DLLs in their projects.

Nothing that can't be bypassed by a determined cracker. You could
have your DLL look in the registry for something, look for another
preexisting file, require a password (either fixed or determined by
something within the user's system), etc. - basically, do the same
things that commercial programs do - but again, crackers bypass this
on a daily basis. (Although they usually crack apps to use the app,
not just one specific file.)

Thanks, yea I didn't think of that. Might be a good idea me thinks!

Yes, well, just remember that crackers can bypass *any* protection
scheme if they have reason to.

[mayayana]

How do I put a form in a DLL?

A DLL is like an EXE with a COM interface. You can do
anything you want to. Just add the form to the project and
control it through your exposed class(es).
You can also pass the events through if you need to.
In the exposed class, assuming you have a Form1, use:
Private WithEvents Frm as Form1
You can then write subs in your class for the form events, like:
Private Sub Frm_Clicked()
Msgbox "Form was clicked."
end sub

[Visual Boodu .NET]

Excellent advice, thanks. I made a DLL with a form which had a button and
'referenced' the DLL in my project (project - references) then added this
code:

Dim frm As Projectdll.Clas s1

Set frm = New Projectdll.Clas s1

Call frm.LdForm

Is that the right way to work with DLLs? What does 'Private WithEvents Frm
as Form1' do? What is a COM interface?

Thanks!

mayayana wrote:

How do I put a form in a DLL?

A DLL is like an EXE with a COM interface. You can do
anything you want to. Just add the form to the project and
control it through your exposed class(es).
You can also pass the events through if you need to.
In the exposed class, assuming you have a Form1, use:
Private WithEvents Frm as Form1
You can then write subs in your class for the form events, like:
Private Sub Frm_Clicked()
Msgbox "Form was clicked."
end sub

[Visual Boodu .NET]

OK I figured out I can just do:

Dim frm As New Projectdll.Clas s1

And that works OK. Now I would like the DLL to be a MDI child form to be
called into my (obviously) MDI parent. When I try to do this it craps
itself (it can't find a MDI parent form). Is there any way around this?

Visual Boodu .NET wrote:

Excellent advice, thanks. I made a DLL with a form which had a
button and 'referenced' the DLL in my project (project - references)
then added this code:

Dim frm As Projectdll.Clas s1

Set frm = New Projectdll.Clas s1

Call frm.LdForm

Is that the right way to work with DLLs? What does 'Private
WithEvents Frm as Form1' do? What is a COM interface?

Thanks!

mayayana wrote:

How do I put a form in a DLL?

A DLL is like an EXE with a COM interface. You can do
anything you want to. Just add the form to the project and
control it through your exposed class(es).
You can also pass the events through if you need to.
In the exposed class, assuming you have a Form1, use:
Private WithEvents Frm as Form1
You can then write subs in your class for the form events, like:
Private Sub Frm_Clicked()
Msgbox "Form was clicked."
end sub