Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Extensibility / June 2006

Tip: Looking for answers? Try searching our database.

Package Load Key Not Working

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bobby DeRosa - 25 May 2006 02:31 GMT
I've got a package load key that is not working correctly (this is actually
the third one i've tried).

I recieve this error in my log when I try to run VS Exp w/ NoVISP.

------------------

<entry>
  <record>77</record>
  <time>2006/05/24 20:58:10.510</time>
  <type>Warning</type>
  <source>Microsoft Visual Studio Appid Stub</source>
  <description>CheckPackageSignature failed; invalid Package Load
Key</description>
  <guid>{4360C53B-9811-4C8D-B85E-32404FA36575}</guid>
</entry>
<entry>
  <record>78</record>
  <time>2006/05/24 20:58:10.526</time>
  <type>Warning</type>
  <source>Microsoft Visual Studio Appid Stub</source>
  <description>CheckPackageSignature failed; invalid Package Load
Key</description>
  <guid>{4360C53B-9811-4C8D-B85E-32404FA36575}</guid>
</entry>

------------------

My package class attributes look like this:

      [MsVsShell.ProvideToolWindow(typeof(ClipboardWindowPane), Style =
MsVsShell.VsDockStyle.Tabbed, Window =
"3ae79031-e1bc-11d0-8f78-00a0c9110057")]
      [MsVsShell.ProvideLoadKey("Standard", "1.0", "Clipboard Manager",
"NA", 150)]
      [MsVsShell.ProvideMenuResource(1000, 1)]
     
[MsVsShell.DefaultRegistryRoot(@"Software\Microsoft\VisualStudio\8.0Exp")]
      [MsVsShell.PackageRegistration(UseManagedResourcesOnly = true)]
      [Guid("4360C53B-9811-4c8d-B85E-32404FA36575")]

and my Resource.resx file  has this entry:

<data name="150" xml:space="preserve">
<value>JKK3PIR9DZP3R9H3ZMCHHKDHQAR3AEERJHDQA8KHIDMEDTCTDKMQA2KRIZPTK2I1PIK8DZMKQ1JMAJZ9D8QAM2A1ZZQAMAAHQIEAKCD8E9IRJDCDD9MEZ3MCE8ETIEED</value>
</data>

and the registry entries look like this:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0Exp\Packages\{4360c53b-9811-4c8d-b85e-32404fa36575}]
@="CSharper.Net.Packages.ClipboardManager.ClipboardManagerPackage,
ClipboardManager, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null"
"InprocServer32"="C:\\WINDOWS\\system32\\mscoree.dll"
"Class"="CSharper.Net.Packages.ClipboardManager.ClipboardManagerPackage"
"CodeBase"="D:\\Projects
2005\\ClipboardManager\\bin\\Debug\\ClipboardManager.dll"
"ID"=dword:00000096
"MinEdition"="Standard"
"ProductVersion"="1.0"
"ProductName"="Clipboard Manager"
"CompanyName"="NA"

________________

Any help regarding this PLK issue would be greatly appreciated.

Cheers
Chris - 26 May 2006 23:44 GMT
Check your information in these attributes for your package class.  They
must match exactly the information that you gave Microsoft when you
submitted your information to create the PLK.

  [ProvideLoadKey("Professional", "1.0", "TdVSPackage", "NCR", 104)]

Professional is the minimum VStudio version
1.0 is the version
TdVsPackage is the package name.
   Check the docs, this entry is actually the product name, but they REALLY
mean package name.
   Yours is Clipboard Manager, which cannot possibly be a package name,
    so you may try subsituting your package name here ( the class that
derives from package).
NCR is the company name.  Yours is NA?  This field is used to generate a
PLK.
104 is my resource id - yours is 150 that points to the package load key.

If this information matches, then it's time to send Microsoft an email and
ask for assistance.  I am also having problems with my PLK.

Hope this helps

Chris Cuciak
NCR .NET Data Provider for Teradata

> I've got a package load key that is not working correctly (this is
> actually
[quoted text clipped - 65 lines]
>
> Cheers
Bobby DeRosa - 27 May 2006 00:39 GMT
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.

When I attempt to register on a non-VSIP machine, it never gets loaded at all.

So the Product Name is actually the Package Class name? That's odd - where
did you find this out? When I change the Product Name to the pkg class name
and run in debug mode, it complains of invalid PLK like before, but this time
the pkg doesn't load at all.

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
denied/approved NEVER gets sent. This adds to the confusion of trying to get
the exact information correct that was submitted to MS. On top of that, they
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 - 27 May 2006 01:44 GMT
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.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.