Hi All,
In getting a Package load error when I try to run my package on a clean computer without VSIP installed. When I run the package on my machine with the /noVSIP switch, it works. Is there any diagnostic utils that I can run to help me determine the source of the problem
As a side note / change enhancement can the authorization rountine give more information as to why the package was not autorized to load examples: unable to load dll, can't find resource #xxx, company / product name missmatch, invalid VS version... etc)
Thanks,
Drew
PLK Diagnostics
Frances83
Hi Drew,
If it's a managed package, use the fuslogvw.exe utillity to see if you are missing a dependency or have an older version of a dependency installed on the target machine. If the package loads successfully on the development machine when you launch the IDE with the /noVSIP switch, it's a pretty good indicator that your PLK is working properly. The only other thing is to ensure the registry keys are properly set up.
Currently there is no diagnostic utility, but I have the beginings of one. We're also working to revamp the VSIP website so that you can view all the data submitted with the PLK request (something that was lost when we revamped the site previously). Once the data is visible, I've got a small utility program that can be used to pull the registry and PLK info for a particular package on a specific hive, and you'll be able to cross check it. Right now though, it's still pretty ugly.
Sincerely,
Shadowsoul
Hi Drew,
If your package is written using MPF you should also install the ProjectAggregatory2.msi.
In my case that was a root of the evil :) See details in another post here.