http://blogs.msdn.com/francischeung/archive/tags/PLK/default.aspxTags: PLKen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/francischeung/archive/2007/01/14/vsip-product-load-keys.aspxSun, 14 Jan 2007 22:51:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:1466425fcheung0http://blogs.msdn.com/francischeung/comments/1466425.aspxhttp://blogs.msdn.com/francischeung/commentrss.aspx?PostID=1466425<P>I went through the process to <A class="" href="http://msdn2.microsoft.com/en-us/library/bb165795(VS.80).aspx" mce_href="http://msdn2.microsoft.com/en-us/library/bb165795(VS.80).aspx">request and install VSIP PLK's</A> for the Process Editor Tool. The tool actually needs two PLKs: one for the Process Editor VS Package and another for the Work Item Type Editor VS Package.&nbsp;</P> <P>Please note that the new instructions for requesting a PLK are considerably different from the <A class="" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/plkwalkthrough.asp" mce_href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/plkwalkthrough.asp">old instructions</A>. Especially with regards to the information the VSIP system returns back to you. In the new system, the email that is sent simply states that the PLK is ready.</P> <P>Make sure you keep a copy of the values you entered in the PLK request form:</P> <UL> <LI>Product Version</LI> <LI>Package Guid</LI> <LI>Application Residency</LI> <LI>Minimum Product Edition</LI> <LI> <P>Resource DLL Filename</P></LI></UL> <P>Make sure these values match EXACTLY what is specified in your code. I entered "1.0.0" in the PLK request form, but I had "1.0.0.0" in my ProvideLoadKey attribute. Wasted hours tracking that one down.</P> <P>The VSIP site will not provide you with these values that you entered, just the resulting PLK value, which is a hash of your inputs.</P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1466425" width="1" height="1">PLK