I
immi
Hi,
I am using an application built in Visual C++. The application is
using shared WinSxS assemblies, which require these assemblies to be
placed in C:\Windows\WinSxS folder. But, in order to avoid any
conflict of these assemblies with assemblies having same name but
different versions, I want to use these as Private Assemblies. For
this purpose, I have placed these assemblies and their required
manifest files in application’s local folder instead of C:\Windows
\WinSxS and C:\Windows\WinSxS\Manifests folders respectively. However,
the required Policy files are still placed in C:\Windows\WinSxS
\Policies folder. It works fine but redirects some earlier versions of
same assemblies causing the associated applications not working
properly. I want my policy files to be private as well (placed in
application’s local folder). Is there any way to implement same
security policies but without putting these in C:\Windows\WinSxS
\Policies folder?
I have also read about use of Application Configuration files in place
of Policy files. I have used so but it did not work. Is there any
special settings done inside the application for Application
Configuration Files? Can anyone help me in this regard or send me some
sample Application Configuration Files which can serve me in this
regard.
Another thing I would like to ask in this regard is that if any
application has certain policy file placed in C:\Windows\WinSxS
\Policies folder. Now, If another policy file with same name but
higher version is also present there having redirection for all the
earlier versions. Can any one tell me that the application would be
using its own policy file or will be redirected to the higher version
policy file? What is the searching mechanism/hierarchy for Policy
Files?
Thanks.
I am using an application built in Visual C++. The application is
using shared WinSxS assemblies, which require these assemblies to be
placed in C:\Windows\WinSxS folder. But, in order to avoid any
conflict of these assemblies with assemblies having same name but
different versions, I want to use these as Private Assemblies. For
this purpose, I have placed these assemblies and their required
manifest files in application’s local folder instead of C:\Windows
\WinSxS and C:\Windows\WinSxS\Manifests folders respectively. However,
the required Policy files are still placed in C:\Windows\WinSxS
\Policies folder. It works fine but redirects some earlier versions of
same assemblies causing the associated applications not working
properly. I want my policy files to be private as well (placed in
application’s local folder). Is there any way to implement same
security policies but without putting these in C:\Windows\WinSxS
\Policies folder?
I have also read about use of Application Configuration files in place
of Policy files. I have used so but it did not work. Is there any
special settings done inside the application for Application
Configuration Files? Can anyone help me in this regard or send me some
sample Application Configuration Files which can serve me in this
regard.
Another thing I would like to ask in this regard is that if any
application has certain policy file placed in C:\Windows\WinSxS
\Policies folder. Now, If another policy file with same name but
higher version is also present there having redirection for all the
earlier versions. Can any one tell me that the application would be
using its own policy file or will be redirected to the higher version
policy file? What is the searching mechanism/hierarchy for Policy
Files?
Thanks.
