See my thoughts in-line below
> 1) It looks like you can add commands in the VB code, whereas
> right now you have to have a LISP function to load and
> run the macro.
Adding commands is very very easy with .NET
> 2) It looks like the code is compiled into a DLL, loaded with
> the NETLOAD command.
>
> A) Is this truly compiled or still an interpreted code?
>
> B) Is the code as protected as a normal DLL. Right now anyone
> with a brower and 15min can unprotect a DVB.
All .NET code is compiled to Microsoft Intermediate Language (MSIL) code.
This IL code is compiled to x86 instructions at runtime, but only on an as
needed basis. If you never run a particular method, then that method is
never compiled. And once a method is compiled, the x86 instructions are
saved and reused each time that method is called for the duration of the
application. You can create and distribute a native compiled image of your
application if you so desire.
All .NET assemblies can be disassembled and your MSIL code can be viewed by
anyone with the freely downloadable .NET SDK. If this is truly a concern,
there are obfuscators available.
> 3) Do the DLL's have to be registered by an install/regsvr32
> when ported to another station?
No, unless you are installing an assembly into the global assembly cache.
It is entirely possible to simply XCOPY an application onto a machine if you
design it properly. In fact, this is the recommended way to create .NET
apps. If you want to expose your .NET app as an ActiveX server, then you
will have to register those interfaces in the registry.
> I know its early, but does anyone else have any thoughts, plus &
> minuses, as to what this might hold in store?
In short .NET is going to give you much of the power of C++ combined with
the ease of VB and much much more.
That's my 0.02 for the day.
--
Bobby C. Jones
