|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
 |
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
|
|
|
|
| ||||||||||||||||||||||||||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
Dev Articles Community Forums Sponsor:
|
|
|
|
#1
April 8th, 2003, 11:58 PM
|
|||
|
|||
Difference between using system dll and visual basic dll?
What is the difference between using system dll and visual basic dll?
|
|
#2
April 9th, 2003, 02:41 AM
|
||||
|
||||
|
A DLL is a DLL - you can write a DLL in C++, VB, etc... DLL's contain classes which allow you to perform procedures. There's no real distinction between them. What exactly do you mean by a system dll...?
|
|
#3
April 9th, 2003, 02:20 PM
|
|||
|
|||
|
The main differences between writing DLL files in different languages is the threading model; VB6 is not good for apps that need to scale up because of it's apartment-threading model. For example, you wouldn't write a VB ActiveX DLL to run a huge website that will have 10,000 concurrent users. Typically free threading is the way to go, but that requires extra coding in c/c++, not in c# though !
|
|
#4
April 9th, 2003, 11:38 PM
|
|||
|
|||
|
Quote:
Thanks for u r reply.I just wanted to know the difference between using windows system dlls or functions like kernel and using our own dlls written in VB.
|
|
| Viewing: Dev Articles Community Forums > Programming > ASP Development > Difference between using system dll and visual basic dll? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
 |
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
