Private assembly?

  • Thread starter Thread starter Peter Rilling
  • Start date Start date
P

Peter Rilling

I am not sure what they mean by "private assembly", but there are several
issues to consider.

An assembly can either be in the GAC or can be located along with your site.
Public and private might be used to identify the location for these. The
private assembly might be one that should be located in the same area as
your application and only your application can reference it whereas
assemblies in the GAC are publicly available to all applications regardless
of where they are located.

Or they might be talking about security. Items in an assembly can be marked
with "internal" which means only items within the assembly can call those
operations.

Or an assembly can be attributed in such a way that only certain signed
assemblies can access the operations.

Having said all that, I think they probably are just referring to the need
to place the assembly with your application. If they include the source
code, there is no way that they can then protect it in such a way that you
would not be able to use it because all protects would be defined within the
code.
 
Hi, can someone please tell me what a private assembly is? I am thinking of
buying a ASP.NET component which includes all the source code but also says
something about there being a private assembly.

I want to be able to modify the component for my needs (hence the reason I
will pay more for the source code) but am worried that the included private
assembly might stop me from doing this.

Thanks in advance
Mark
 
Hi Peter, thanks for your help :)
Cheers
Mark
Peter Rilling said:
I am not sure what they mean by "private assembly", but there are several
issues to consider.

An assembly can either be in the GAC or can be located along with your site.
Public and private might be used to identify the location for these. The
private assembly might be one that should be located in the same area as
your application and only your application can reference it whereas
assemblies in the GAC are publicly available to all applications regardless
of where they are located.

Or they might be talking about security. Items in an assembly can be marked
with "internal" which means only items within the assembly can call those
operations.

Or an assembly can be attributed in such a way that only certain signed
assemblies can access the operations.

Having said all that, I think they probably are just referring to the need
to place the assembly with your application. If they include the source
code, there is no way that they can then protect it in such a way that you
would not be able to use it because all protects would be defined within the
code.
Click to expand...
 
Back
Top