|
|||||||
 |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
07-12-2002, 03:23 AM
|
#1 |
|
Banned
Join Date: Jul 2002
Posts: 257
|
Visual Basic .NET DLL?
does anyone know if vb.net still uses its own dll (i.e msvbm60)
|
|
|
|
07-12-2002, 09:05 AM
|
#2 |
|
Member (10 bit)
Join Date: Apr 2001
Location: Michigan
Posts: 850
 |
.Net makes use of XCOPY so there are no more conflicts with DLL's and versioning. Personally I think I'll stick with Visual Studio. .Net is too proprietary for me.
|
|
|
|
|
07-12-2002, 04:12 PM
|
#3 |
|
Banned
Join Date: Jul 2002
Posts: 257
|
but does it still have its own dll cuz with older versions you had to have the runtime installed or it wouldnt work is this still trus with .NET or is it like a C++ program and ready to go
|
|
|
|
|
07-14-2002, 03:30 AM
|
#4 |
|
Registered User
Join Date: Nov 2001
Posts: 1,965
|
I think .NET programs always need .NET runtime in order to work.
|
|
|
|
|
07-18-2002, 07:16 AM
|
#5 |
|
SQL nutcase
Join Date: Sep 2000
Location: Belgium
Posts: 1,136
 |
All .NET assemblies need the .NET framework to work. This because the assemblies are not the final code. A .NET assembly is made up out of IL (Interface language). And will be compiled on your machine on execution by a JIT (Just in time compiler) that optimizes the code for your machine. This results in a better overal performance.
|
|
|
|
|
07-18-2002, 07:32 AM
|
#6 |
|
Banned
Join Date: Jul 2002
Posts: 257
|
Kool didnt know .NET was that advanced
|
|
|
|
|
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Linear Mode
