GAC and Source Safe

[Guest]

Hi,

I have a question regarding the Global Assembly Cache (GAC) and Source
Safe. We have some common dlls which we would like to put in GAC so that they
can be used in different applications. We are using Source Safe as a Version
Control. Let's say I have created a data access library( one of common dll)
and put in the source safe. I have created one web application which needs
to access this data access dll. Can I put this data access library in GAC and
refer it from there in my web application? If I need to deploy this web
application, how should I do that? If one of the other developers added some
functions to this data access library and checked in to source safe and if I
need to access these new functions what are the steps involved? Please let me
know.

Thanks,

 

[bruce barker \(sqlwork.com\)]

the best approach is to not use the gac. just build the shared code and
include the dll with your project. then you always have the version of the
library that matched your code. you can also change and distribute a new
version of libary with your app and not break anyone else. all using the
gac does is save some disk space.

-- bruce (sqlwork.com)

 

[Alvin Bruney]

There are performance issues associated with not using the gac. For
instance, each time the appllication is loaded, the CLR will touch every
function in this new library for code verification purposes. However, this
is just a one time startup cost. I've not measured this expense so I cannot
give an estimate on how bad it is.

--

________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------

 

[Guest]

Hi Alvin,

Thanks for the reply. I didn't understand your answer correctly. You
are saying that if I don't put an assembly in the GAC, every time when an
application loads, it will check for code verification in all the dlls. Is
that right? In that case, using GAC would be better option.

Thanks,
Sridhar

There are performance issues associated with not using the gac. For
instance, each time the appllication is loaded, the CLR will touch every
function in this new library for code verification purposes. However, this
is just a one time startup cost. I've not measured this expense so I cannot
give an estimate on how bad it is.

--

________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------

the best approach is to not use the gac. just build the shared code and
include the dll with your project. then you always have the version of the
library that matched your code. you can also change and distribute a new
version of libary with your app and not break anyone else. all using the
gac does is save some disk space.

-- bruce (sqlwork.com)

 

[Jan Hyde]

Sridhar <[email protected]>'s wild thoughts
were released on Wed, 17 May 2006 12:48:01 -0700 bearing the
following fruit:

Hi Alvin,

Thanks for the reply. I didn't understand your answer correctly. You
are saying that if I don't put an assembly in the GAC, every time when an
application loads, it will check for code verification in all the dlls. Is
that right? In that case, using GAC would be better option.

You should also condider that .NET allows you to avoid 'dll
hell' by following Bruce's suggestion, however you can have
both the advantages and disadvantages of dlls by using the
GAC.

The 'startup' cost others have mentioned I have noticed in
windows forms apps, but I've yet to notice it in my ASP app,
but I guess we're all used to slight delays when using the
web.

Thanks,
Sridhar

There are performance issues associated with not using the gac. For
instance, each time the appllication is loaded, the CLR will touch every
function in this new library for code verification purposes. However, this
is just a one time startup cost. I've not measured this expense so I cannot
give an estimate on how bad it is.

--

________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------

the best approach is to not use the gac. just build the shared code and
include the dll with your project. then you always have the version of the
library that matched your code. you can also change and distribute a new
version of libary with your app and not break anyone else. all using the
gac does is save some disk space.

-- bruce (sqlwork.com)



Hi,

I have a question regarding the Global Assembly Cache (GAC) and Source
Safe. We have some common dlls which we would like to put in GAC so that
they
can be used in different applications. We are using Source Safe as a
Version
Control. Let's say I have created a data access library( one of common
dll)
and put in the source safe. I have created one web application which
needs
to access this data access dll. Can I put this data access library in GAC
and
refer it from there in my web application? If I need to deploy this web
application, how should I do that? If one of the other developers added
some
functions to this data access library and checked in to source safe and
if I
need to access these new functions what are the steps involved? Please
let me
know.

Thanks,

Jan Hyde (VB MVP)