asked on

.Net component deployment

I have a .Net component, which is a DLL file, that support .Net 1.1, 2.0, 3.0, 3.5 and 4.0, that's 5 dlls.

This component is, well, as a component is, for developers.
As a developer, do you expect the .Net being deployed to the GAC?
Also.... all of them?
Or they should be kept in the component directory and let the developer install or move it himself?

uanmi

Hi,

you should have one dll that includes five assemblies where each assembly would support one of the dotnet frameworks. Each assembly can then be registered into the GAC and will be available to developers as a registered set of components.

The location of the dll does not matter generally, so long as it is visible to the development environment, so you may have to include the path in the environment variables.

regards, mark

lenordiste

i d avoid registering those assemblies to the GAC, since the GAC causes more headaches than it solves problems.
Also, since it's intended for developpers let them choose how they are going to use the dll: developpers hate it when things are forced on them. Do include a readme file if you have no documentation and need to provide some important details.

fischermx

ASKER

uanmi:

Could you elaborate a little more about that idea of having "one dll that include five assemblies"?
How does that work? What's the name for that arrangement?
Just let me know where do I start to read more about that.

SOLUTION

uanmi

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

ASKER CERTIFIED SOLUTION

lenordiste

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer