We recently obtained a set of PLKs, but need to refresh the information due to some changes (need to switch from VS 2005 to VS 2002 as minimum level) and obtain a new set. How would we go about achieving that
Maybe that is the case. That would, however, imply that there is no way to retain a product's name beyond a single version, no For example, how would you go from version 1.0 to 2.0 of the same plugin if there is no way to refresh the PLKs
(Note: for users of our old website www.vsipdev.com, you'll be redirected to the above location. Things are very different in the new site, but all the old functionality is there. It's just been rearranged.)
Actually, the PLK's that I am working with were retrieved from that site already. Either the website script failed or I accidentally chose the wrong version, but the keys that were given to me after the request only function for VS 2005. I went back to the site you gave above in order to attempt to correct the issue, but there does not appear to be a way to wipe out the old keys and retrieve a new one. Nor is there a way to modify the existing information to refresh the data.
So, what I'm trying to determine is how one would go about cleaning out the old keys and obtaining new ones (against new information) using the current system
Refreshing PLKs
Inc
Saso
You can obtain a new PLK at the following location: http://affiliate.vsipmembers.com/affiliate/myProducts.aspx
(Note: for users of our old website www.vsipdev.com, you'll be redirected to the above location. Things are very different in the new site, but all the old functionality is there. It's just been rearranged.)
I've blogged some on the topic PLK's and multiple VS versions if that's what anyone is trying to do.
I hope my blog helps you to get your package working in all the versions of VS that you need.
T-boy
Actually, the PLK's that I am working with were retrieved from that site already. Either the website script failed or I accidentally chose the wrong version, but the keys that were given to me after the request only function for VS 2005. I went back to the site you gave above in order to attempt to correct the issue, but there does not appear to be a way to wipe out the old keys and retrieve a new one. Nor is there a way to modify the existing information to refresh the data.
So, what I'm trying to determine is how one would go about cleaning out the old keys and obtaining new ones (against new information) using the current system
Juan Gabardini