.NET Conflict
Softgrid 4.2
Rightnow Smart Client 10.2 (Virtualised)
Rightnow Smart Client 10.5 (present on host PC)
DotNet 3.5 SP1
Hi, I'm new to app virtualization and I have a client that needs two particular versions of an application due to a bizarre back end configuration. So I decided to virtualize one of them (the other is already in production).
When the non virtualized version is installed on the host PC the virtualized version will fail on launch with a CLR 80004005 error, which I understand is related to .NET. Both applications make changes to the .NET security.config file and I've included the security.config and security.config.cch files in the bubble.
Is there something else I need to do in order to isolate the .NET configuration for the virtualized app?
Thanks in advance.
Rightnow Smart Client 10.2 (Virtualised)
Rightnow Smart Client 10.5 (present on host PC)
DotNet 3.5 SP1
Hi, I'm new to app virtualization and I have a client that needs two particular versions of an application due to a bizarre back end configuration. So I decided to virtualize one of them (the other is already in production).
When the non virtualized version is installed on the host PC the virtualized version will fail on launch with a CLR 80004005 error, which I understand is related to .NET. Both applications make changes to the .NET security.config file and I've included the security.config and security.config.cch files in the bubble.
Is there something else I need to do in order to isolate the .NET configuration for the virtualized app?
Thanks in advance.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Spyderizer
13 years ago
Update:
Been experimenting. I reran the sequence and deleted the security.config and security.config.cch before clicking "stop monitoring". I then used the .NET Framework Security tool in Wise to add the security settings to the MSI (effectively deploying them to the local machine at install time.)
This has resulted in the desired effect, I can now run the locally installed 10.5 client at the same time as the virtualized 10.2 client. However in the interest of consistency I would like to know if there is a way to properly isolate the .NET security configuration inside the bubble. Updating the local .NET config for a virtual app bugs me.
Update: Scratch that, fails with the same error after the first launch. Looks like the new version has a different PublicKeyBlob.
Been experimenting. I reran the sequence and deleted the security.config and security.config.cch before clicking "stop monitoring". I then used the .NET Framework Security tool in Wise to add the security settings to the MSI (effectively deploying them to the local machine at install time.)
This has resulted in the desired effect, I can now run the locally installed 10.5 client at the same time as the virtualized 10.2 client. However in the interest of consistency I would like to know if there is a way to properly isolate the .NET security configuration inside the bubble. Updating the local .NET config for a virtual app bugs me.
Update: Scratch that, fails with the same error after the first launch. Looks like the new version has a different PublicKeyBlob.
Posted by:
Spyderizer
13 years ago
Ok, found a RightNow settings file hiding under %appdata% that only appears after first launch. Tried adding that to the bubble.
Still no good, there's still a conflict somewhere with the local application and the virtualized version. Happens even if you remove the local version after installing. Suspect it might have something to do with RightNow.SiteInstaller.exe, which is run by custom action after the local Right Now is installed.
Still no good, there's still a conflict somewhere with the local application and the virtualized version. Happens even if you remove the local version after installing. Suspect it might have something to do with RightNow.SiteInstaller.exe, which is run by custom action after the local Right Now is installed.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.