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 / September 2007

Tip: Looking for answers? Try searching our database.

PLK Fails to load without much help

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
VistaDB - 07 Sep 2007 17:40 GMT
I have walked through all the debugging I can think of (and read about
on MSDN).  There were a number of small problems with the PLK at
first, but I am almost positive I have them all corrected now.

    [ComVisible(true)]
    [PackageRegistration(UseManagedResourcesOnly = true)]
    [DefaultRegistryRoot(@"Microsoft\VisualStudio\8.0")]
    [ProvideService(typeof(VistaDBProviderObjectFactory), ServiceName =
"VistaDB Provider Object Factory")]
    [ProvideMenuResource(1000, 1)]
    [InstalledProductRegistration(false, "#100", "#102", "3",
IconResourceID = 400)]
    [ProvideLoadKey("Standard", "3", "VistaDB 3", "VistaDB Software,
Inc.", 1)]
    [Guid("f01fb7e1-221a-4b0b-b5c7-b95cec7cdd41")]
    internal class VistaDBDataProviderPackage : Package

This is the top of my DataProviderPackage - The data is all identical
to what was given in the PLK, and identical to what is in the
registry.  The registry was giving me errors at first with invalid /
missing keys until I figure out the names had to have the spaces
removed.  EG:  MinEdition rather than "Min Edition".  And the ID field
in the registry is a DWORD 0x01 (and it is a 1 above and in the
resource file).

VSIP: Can not load package
'VistaDB.VisualStudio.Data.VSPackageBasedProvider.VistaDBDataProviderPackage',
invalid key authentication. ( GUID = {F01FB7E1-221A-4B0B-B5C7-
B95CEC7CDD41} )

The GUID is correct for the internal class
VistaDBDataProviderPackage : Package.
This is the only PLK you need, correct?

The PLK is installed in the resource file.

Using the package load analyzer this is the only thing it tells me:

Package Load Key(PLK) verification failed for package
{f01fb7e1-221a-4b0b-b5c7-b95cec7cdd41}.
Plk verification was based on the following entries in the registry -
CompanyName - VistaDB Software, Inc
ProductName - VistaDB 3
ProductVersion - 3
MinEdition - Standard
ID - 1

The ProductVersion does not match the "version" stamp in the
Assembly.  Does that matter?  It would seem to me to be strange to
require it to be the strongly named version (3.2.1.26) because we
change that for each BUILD and I would need a new PLK per build at
that point.  Is that what you are supposed to do?

Very, very frustrating with no way to debug this...
VistaDB - 07 Sep 2007 18:36 GMT
I finally found my own answer...

In the assemblyinfo.cs file:

// DO NOT CHANGE:  This MUST match the PLK value of 3 EXACTLY
[assembly: AssemblyVersion("3")]
// This version is allowed to change and is not used by the PLK
[assembly: AssemblyFileVersion(VistaDB.Build.Settings.MajorVersion + "." +
VistaDB.Build.Settings.MajorBuildVersion + ".1." +
VistaDB.Build.Settings.MinorBuildVersion)]

So it appears you can change the AssemblyFileVersion, but NOT the
AssemblyVersion.

Rate this thread:







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.