Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / October 2006

Tip: Looking for answers? Try searching our database.

GAC dependencies

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Richard - 04 Oct 2006 07:40 GMT
Hi,

I'm in a situation where I have to deal with a huge number of dependencies
in the GAC. We have tons scehmas that all exists in their seperate dll. They
are then referenced by other assets that all exists in the GAC. This is
starting to get out of hand and we need an easy way of handling the
dependencies documentation between the different assets.

One idea is to have a application that reads the dll:s in the GAC and tells
us what assets are referencing on specific asset. For example: we update one
specific schema. We give this schema name to the application we like to
develop and this gives us a full list over the dll that reference this
asset. This would give us enough inforrmation on what assets to update.

Is there something like this out there? Is there a better approach? All
anseres ideas are highly appricated. I'm fairly new to this ...

Richard
Petar Repac - 04 Oct 2006 22:07 GMT
Hi Richard,

1) I suppose that by "asset" you mean assembly ?
2) Are those "schemes" possibly datasets ?

Each assembly in .NET has a version number that is usually defined in
the AssemblyInfo.cs file by the AssemblyVersion attribute.
Let's say this is your assembly A.

When an other assembly B reference assembly A in B's manifest are
embedded A's name and version (+ public key and culture I think).

Now, if you don't change A's name and version you can change classes in
A, but they must retain their class names, property names, method
signatures, etc. You can change method implementations, add methods, ...

When you install new A assembly in GAC, B assembly won't note any
difference.

So, maybe you don't need to take care of assemblies that are referencing
 your assembly.

This is specially true if you build an library that will be used by many
developers.

Regards,
Petar Repac

> Hi,
>
[quoted text clipped - 14 lines]
>
> Richard

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.