see inline
> When I attempt to debug the PLK, the log says that the PLK was invalid,
> yet it continues to load the package even w/ the NoVSIP flag. In the log,
> there are 2 entries saying the pkg is invalid, followed by 2 more lines
> successfully loading the pkg.
[Chris] My log indicates :
<source>Microsoft Visual Studio Appid Stub</source>
<description>CheckPackageSignature failed; invalid Package Load
Key</description>
<guid>{0F22D68D-E46D-11DA-99A1-00132016887F}</guid>
> When I attempt to register on a non-VSIP machine, it never gets loaded at
> all.
[quoted text clipped - 5 lines]
> time
> the pkg doesn't load at all.
[Chris]
I have MSDN and under the Visual Studio SDK Visual Studio Integration there
is this note:
In How to Obtain a PLK
Each VSPackage to be loaded in a deployed application must have a valid
package load key (PLK). The PLK is uniquely related to the VSPackage and
cannot be used to load any other VSPackage. PLKs are obtained from the
Visual Studio Industry Partner (VSIP) Affiliate home page.
Note
Although the PLK request form refers to your product name, description, and
version, it actually means your VSPackage name, description, and version.
> I've emailed MS (vsipinfo@microsoft.com) but no one has responded. The
> "email" that was supposed to get sent out when a PLK request is
[quoted text clipped - 4 lines]
> don't seem to be responding to emails. Seems like the affiliate version of
> VSIP is useless if the PLK's don't work right.
[Chris] I have a Microsoft rep helping me (my company has a support
contract). I will pass on any information they give me to you. They
thought my key was defined properly, but it still doesn't load without a
VSIP license.
Bobby DeRosa - 27 May 2006 02:24 GMT
Sounds great Chris. I appreciate the help.
> see inline
>
[quoted text clipped - 44 lines]
> thought my key was defined properly, but it still doesn't load without a
> VSIP license.
Bobby DeRosa - 30 May 2006 04:40 GMT
After trying tons of different things w/ my 3 previous keys, I decided to
just request a new key w/ the package class name [ClipboardManagerPackage] as
the product name. MS just approved the PLK request and this one finally
works. The only odd thing is that when running VS w/ the /log switch, it
still says "Invalid Package Load Key" in the log twice - but it loads fine
and works fine in all VS instances, even non VSIP.
Dear Microsoft,
Please provide better documentation and information to affilate/all members
of the VSIP program for registering PLK's. The 1 article I could find on MSDN
was for 2002/2003 packages. Please also fix the email issue when PLK's are
requested. No email is ever sent. Also, please update the VSIP members area.
We should be able to update our company name and we should be able to see
what information we have submitted in a PLK request per product.
Ed Dore - 07 Jun 2006 06:22 GMT
Hi Bobby,
We're pushing to get that website overhauled as soon as possible. It
definitely went from bad to worse with that latest design. I've had to debug
a good number of PLK problems, and in every instance it's been due to either
a bad (or wrong) PLK, someone changed one of the registry keys that
invalidate the PLK, or changed the package guid.
Having debugged through that code (more often that I care to admit) it
appears that we actually scan the 7.0 and 7.1 hives as well, and that's why
you're seeing those two failures. This seems to be a bug in my opinion, but
one that you can safely ignore.
Sincerely,
Ed Dore [MSFT]
This post is 'AS IS' with no warranties, and confers no rights.