Posting this in case anyone else runs into this because I'm not sure
if this is a bug or expected behaviour.
I'm updating a plug-in installer to work with a new product which will
be imminently released. After (at least) 4 years of complaining the
developers of said product have caved in
On 3/31/2010 6:06 AM, Pally Sandher wrote:
gives the same error (as expected). I can work around this simply by
adding a RegistryValue to each component setting it as the KeyPath for
those components but does anyone know if this is expected behaviour or a
bug with these types of components?
2 matches
Mail list logo
