GAC - related issues Very Important

[muddasirqdiwai]

There are some GAC related issues

1. if we create assemblies with the help of assemblylinker (dot net tool) it is not getting recognized by InstallAware - but it get regsitered on GAC manually (recognize mean it is not displaying information such as version,
public key etc) even if i try to build installer it gives an error and it wont build untill i remove that assembly from installer assemblies

2. When i run patch, it contain new version of particular assembly which is already in GAC (registered by installer, which is refered as Patch Reference) patch install new version on GAC but it doesn't remove older version

[Gizm0]

There are some GAC related issues

1. if we create assemblies with the help of assemblylinker (dot net tool) it is not getting recognized by InstallAware - but it get regsitered on GAC manually (recognize mean it is not displaying information such as version,
public key etc) even if i try to build installer it gives an error and it wont build untill i remove that assembly from installer assemblies

2. When i run patch, it contain new version of particular assembly which is already in GAC (registered by installer, which is refered as Patch Reference) patch install new version on GAC but it doesn't remove older version

I can't truly understand the first issue, so please give an example or more information.
As for the second , it's not an issue. As a .Net developer you should know that this is a normal behavior and it's being done by .Net by design.That's the purpose of GAC in other words.Older versions REMAIN until the USER removes them or you remove them by using the .net tool by hand on an Installer which is recommended if the assembly is ONLY required by your assembly(executable). Otherwise older versions stay on the GAC as other programs (GAC doesn't know if it a custom assembly or not) may need it to run.You have to remove them by hand if you want.

[muddasirqdiwai]

There are some GAC related issues

1. if we create assemblies with the help of assemblylinker (dot net tool) it is not getting recognized by InstallAware - but it get regsitered on GAC manually (recognize mean it is not displaying information such as version,
public key etc) even if i try to build installer it gives an error and it wont build untill i remove that assembly from installer assemblies

2. When i run patch, it contain new version of particular assembly which is already in GAC (registered by installer, which is refered as Patch Reference) patch install new version on GAC but it doesn't remove older version

I can't truly understand the first issue, so please give an example or more information.
As for the second , it's not an issue. As a .Net developer you should know that this is a normal behavior and it's being done by .Net by design.That's the purpose of GAC in other words.Older versions REMAIN until the USER removes them or you remove them by using the .net tool by hand on an Installer which is recommended if the assembly is ONLY required by your assembly(executable). Otherwise older versions stay on the GAC as other programs (GAC doesn't know if it a custom assembly or not) may need it to run.You have to remove them by hand if you want.

Hi thnx for reply

let me explain me first senario. we have tool al.exe in dot net which help to merger different assemblies. u can get detail information on http://msdn2.microsoft.com/en-us/library/c405shex(VS.80).aspx
so when we generate assembly with the help of this tool it creat asembly withoout manifest. but it have version and strong name so that it can get registered on GAC
but u try to register this assembly( mean generated by the help of al.exe) installer(INstallAware) it wont recognize it as assembly and it will genrerate build error as well . i hope this explain more

OK regarding GAC .. as u mentioned we can regsiter multiple version of assmeblies but when we run uninstall (install aware it removes assemblies from GAC) when i built patch i want to know is there any way that patch will remove previous version of assembly and register new one

[Gizm0]

Without having an assembly manifest, it's possible to read necessary data (As version info etc) which are needed by InstallAWARE. Installing these kind of assemblies is not supported. And actually this is not a "valid" assembly, it's "packaged".