RE: DLL vs Dynamic Compile


IMHO I'd store the compiled .DLL. 700 users grabbing an updated .DLL a few
times a years seems like a small price to pay in order to keep source code
out of sight. If bandwidth is that big of an issue then perhaps you could
compress/decompress the .DLL - there are freeware compression APIs - I think
one is called "ZipLib"??

Also I'm assuming that your compiled C# .DLL contains IL, not native
compiled code. If so then .NET will version check the IL and recompile it
before executing if you replace a .DLL with a newer one...

"John F" wrote:

> Currently I'm working on a C# app for a large organization (700 users
> nationwide). This App is still under development. I have setup code in my
> App to pull C# source code from a database and dynamically compile it at
> runtime. All source code stored in the database will be of Type Form and all
> forms will load as children of an MDI. Once I compile the code I store it on
> the local machine as a DLL. I do this so that the next time a user on that
> local machine elects to use a form, I check to see if that form exists
> locally in a DLL first. If it does I load it from the local DLL and cut down
> on both load time and network traffic. I also check to see if there are
> newer versions of the code in the DB and will pull/recompile as needed.
>
> My question is: Can anyone give me pros/cons to storing either the C# code
> in the database or the already compiled DLL's? I could circumvent the need
> to compile on the fly if I stored the DLL's direct, but I'm not sure I
> recognize all the pros/cons to doing it either way. I do know that the DLL's
> are larger than the raw source code so network traffic would be up slightly.
> I think this would be nominal at best though.
>
> Any thoughts/suggestion on storing raw source or a DLL would be greatly
> appreciated.
>
> Security?
> Speed?
> Preference?
>
> Thanks,
> John F
>
>
.

Relevant Pages

  • Re: getting access to classes in separate vb files
    ... about the timing of the compile. ... > execute without assemblies (.dll or exes). ... >> to access methods in those classes from the webform source code ... I upload files in the same directory but errors ...
    (microsoft.public.dotnet.framework.aspnet)
  • DLL vs Dynamic Compile
    ... This App is still under development. ... All source code stored in the database will be of Type Form and all ... Once I compile the code I store it on ... the local machine as a DLL. ...
    (microsoft.public.dotnet.languages.csharp)
  • DLL vs Dynamic Code
    ... This App is still under development. ... All source code stored in the database will be of Type Form and all ... Once I compile the code I store it on ... the local machine as a DLL. ...
    (microsoft.public.dotnet.general)
  • Re: How do I compile a c++-program as assembly?
    ... Sapphira wrote: ... > I have to compile it? ... If you have the source code to the DLL, ... If you have a DLL as an executable code and you want to convert ...
    (comp.lang.cpp)
  • Re: DLL vs Dynamic Code
    ... Seriously, though, I'd rather store an obfuscated DLL than the source. ... Once I compile the code I store it ... > local machine elects to use a form, I check to see if that form exists ...
    (microsoft.public.dotnet.general)
Loading