PC Review


Reply
Thread Tools Rate Thread

How to Deploy WinSxS assemblies as Private assemblies?

 
 
immi
Guest
Posts: n/a
 
      4th May 2009
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.
 
Reply With Quote
 
 
 
 
Jochen Kalmbach [MVP]
Guest
Posts: n/a
 
      4th May 2009
Hi immi!

> 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.


You need to remove the "publicKeyToken" from the manifest.
http://blog.kalmbach-software.de/200...redist_x86exe/

By the was: This is a german newsgroup

Greetings
Jochen
 
Reply With Quote
 
Jochen Kalmbach [MVP]
Guest
Posts: n/a
 
      4th May 2009

> By the was: This is a german newsgroup


Upps.. this was wrong... sorry

Greetings
Jochen
 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Large assemblies/fewer quantity or Smaller assemblies/Larger quantities. milop Microsoft Dot NET Framework 0 26th Mar 2010 08:05 PM
Deploy satellite assemblies spp Microsoft Dot NET Framework 0 23rd Dec 2008 11:39 AM
Deploy satellite assemblies spp Microsoft Dot NET Framework Forms 0 23rd Dec 2008 11:38 AM
How to deploy private Assemblies with VC2005 SP1 Joerg Toellner Microsoft VC .NET 2 2nd Jan 2007 11:04 AM
Re: What is the best approach to deploy shared assemblies ? Dave Sexton Microsoft C# .NET 0 13th Dec 2006 10:12 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 07:31 PM.