|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Assembly version detecting utility?Hi:
Can anyone suggest an utility to detect specific assembly versions that are required by an exe? I find that, sometimes, I update some assemblies in the GAC and forget to update the client installation. When I execute the new exe file it unceremoniously exits. I then start looking at the assemblies in the GAC for different versions. It would be nice to have a utility that read the expected versions from my exe and report if any where missing. Does such a utility exist? TIA, Martin. Why are you *updating* assemblies in the GAC?
You should really replace them with a new version, so that older versions of software still work. A few questions then : Is there any reason you cannot re-distribute the exe with the GAC assemblies? How many exe's are using the GAC assemblies? Do the assemblies really need to be in the GAC? -- Show quoteGed Moretta www.appsense.com ----------------------------------------------------------------------- This signature isn't automatic. I have to type it manually every time. "Martin Hart" <"martin dot hartturner at gmail dot com"> wrote in message news:u0qhJsCMIHA.3940@TK2MSFTNGP05.phx.gbl... > Hi: > > Can anyone suggest an utility to detect specific assembly versions that > are required by an exe? > > I find that, sometimes, I update some assemblies in the GAC and forget to > update the client installation. When I execute the new exe file it > unceremoniously exits. I then start looking at the assemblies in the GAC > for different versions. It would be nice to have a utility that read the > expected versions from my exe and report if any where missing. > > Does such a utility exist? > > TIA, > Martin. Ged:
> A few questions then : The assemblies that are being updated are minor builds, not major new > > Is there any reason you cannot re-distribute the exe with the GAC > assemblies? versions, so I don't want 4-5 different versions of an assembly in the GAC, I want to update the old assembly. There may also be new assemblies that are in the application folder, and it would be nice to know if these are outdated also. > How many exe's are using the GAC assemblies? Depends, some 5 or 6 currently.> Do the assemblies really need to be in the GAC? The main shared dll's, yes. I am talking about reporting assemblies that are updated with very minor fixes on a monthly basis. I don't want lots of very minor versions in the GAC. See point number 1. So, my question reiterated: Are there any such utilities available? TIA, Martin. I'm not sure if there are any utilities available to do what you want.
However, there is another solution If you go to the properties for your referenced assembly, there is a property "Specific Version", which is set to True. If you set this to False, then, *I believe*, your app will always use the latest version in the GAC. Also, setting this value does mean you will have to redistribute the exe, but only this once. HTH -- Show quoteGed Moretta www.appsense.com ----------------------------------------------------------------------- This signature isn't automatic. I have to type it manually every time. "Martin Hart" <"martin dot hartturner at gmail dot com"> wrote in message news:OsT0K3DMIHA.4684@TK2MSFTNGP06.phx.gbl... > Ged: > >> A few questions then : >> >> Is there any reason you cannot re-distribute the exe with the GAC >> assemblies? > > The assemblies that are being updated are minor builds, not major new > versions, so I don't want 4-5 different versions of an assembly in the > GAC, I want to update the old assembly. There may also be new assemblies > that are in the application folder, and it would be nice to know if these > are outdated also. > >> How many exe's are using the GAC assemblies? > > Depends, some 5 or 6 currently. > >> Do the assemblies really need to be in the GAC? > > The main shared dll's, yes. I am talking about reporting assemblies that > are updated with very minor fixes on a monthly basis. I don't want lots of > very minor versions in the GAC. See point number 1. > > So, my question reiterated: Are there any such utilities available? > > TIA, > Martin. Ged:
Yes, you are right. I use the "Specific Version" for local assemblies, but this can't be used for the GAC. Thanks for your help. Regards, Martin. Ged escribió: Show quote > I'm not sure if there are any utilities available to do what you want. > However, there is another solution > > If you go to the properties for your referenced assembly, there is a > property "Specific Version", which is set to True. > If you set this to False, then, *I believe*, your app will always use > the latest version in the GAC. > > Also, setting this value does mean you will have to redistribute the > exe, but only this once. > > HTH > That's pretty much what the .NET Reflector does.
-- Show quotePhil Wilson [MVP Windows Installer] "Martin Hart" <"martin dot hartturner at gmail dot com"> wrote in message news:u0qhJsCMIHA.3940@TK2MSFTNGP05.phx.gbl... > Hi: > > Can anyone suggest an utility to detect specific assembly versions that > are required by an exe? > > I find that, sometimes, I update some assemblies in the GAC and forget to > update the client installation. When I execute the new exe file it > unceremoniously exits. I then start looking at the assemblies in the GAC > for different versions. It would be nice to have a utility that read the > expected versions from my exe and report if any where missing. > > Does such a utility exist? > > TIA, > Martin.  |
|||||||||||||||||||||||
Other interesting topics