Using GACUTIL for patches to report failures and not successes




We currently use gacutil as part of our patch process to remove all current
assemblies from the GAC and then re add them back ( presumably some will
have later versions and we don't want to have references to mulitple
versions in the GAC ).

However we have nearly 100 assemblies and a lot of output is generated from
gacutil which means finding errors is difficult. regasm provides the /silent
option which only suppresses success messages rather than failure messages
which are always reported. Is there no equivalent option or other tool you
know of which would allow us to do this. We've noticed some failures have
been missed this way because the amount of output is off putting and often
not read in detail.

Obviously the ideal approach is to use an installer package for our patch
process however this is not an option in the short term.







.



Relevant Pages

  • Re: Using Custom Assembly Installed in GAC
    ... bin folder should I set the copy local=false? ... whether or not it is in the GAC. ... allow the app to use the one in bin over the GAC, if assemblies exist in both ... >> Using the GacUtil I created a SNK and deployed my assembly to the GAC ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: COM Interop - Using a COM object from C#
    ... I'm sure this is a stupid question but how do I remove it from the GAC? ... gacutil /u STControl.dll ... "No assemblies found that match: ... >> Grant Schenck ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: VS.NET 1.1 Command Line Compile Problems
    ... GAC without any issues. ... receive an error when using gacutil to install it in the GAC. ... gacutil for .NET 1.1 won't work with 2.0 assemblies and vice versa. ... difference whether you use Visual Studio or CSC to compile your assembly. ...
    (microsoft.public.dotnet.general)
  • Re: Adding Assembly to Global Assembly Cache
    ... that to put a 2.0 assembly into the GAC. ... gacutil is part of the framework, it is not part of the SDK. ... is v2.0 and will produce v2.0 assemblies. ...
    (microsoft.public.dotnet.general)
  • Re: .NET versioning
    ... >> If this isn't dll hell then it's awfully close. ... > xcopy deployment, which thus means avoid the GAC if possible. ... > 2) if required, and if you really have to, copy the files to the GAC. ... If you overwrite assemblies in the GAC ...
    (microsoft.public.dotnet.framework)