PDS Extender Registry Entry Access Problem

[Boni]

hi,

I have registered the PDS Extender successfully and it is working fine. It
has an entry in the registry on the virtual path. But if an entry is already
present on the same path for another extender and that extender has some
problem, then Project Server does not reach/recognize my extender and returns
from the registry entry having problem. For example i have registry entry
"PDSExtensionEx2" value "Microsoft.ProjectServer.Extension.General" on the
path "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\MS Project\WebClient
Server\ProjectServer]" and having no problem. There is already an entry:
"PDSExtensionEx1" value "ProjectRenamer.CMain" on the same path and that
extender having some problem (i.e. extender not configured properly or no DLL
is present against that entry etc.) then Project Server returns from the
entry "PDSExtensionEx1" and does not reach to my extender entry
"PDSExtensionEx2". During installation, it is not wise to rename or delete
the registry entry for other extender.
Is there any workaround of this problem?

Thanks

 

[Dale Howard [MVP]]

Boni --

I would recommend you post this message in the
microsoft.public.project.developer newsgroup, as you are more likely to get
a response there. Hope this helps.

 

[Hugues Perron]

I'll try an explanation,

In fact, it's probably due to how the PDS Extensions work. It's kind of
a loop in the PDS itself. It checks if there the function exits in the
PDS. If not, it checks if there is an extension. If it's the case it
checks if the function is in the extension. If not it checks if another
extension exists and so on.

The problem is when a problem occurs in one of the extensions the PDS
gets out of the loop and doesn't check the other extensions.

As you stated, you have an extension that has problem in it, and it's
the firts one called (PDSExtensionEx1), so it's probably the problem.

Hope this helps

Hugues Perron
http://hperron.net

Boni a écrit :