Powershell and DevForce

 

Jason

I'm using the Enterprise version of Devforce 3.6.0.2 and with VS2008 on a 64bit version of Windows Vista Business.

 

I have created various commandlets in powershell to interact with devforce business objects - and when running using the .Net runspace (System.Management.Automation) to host these objects - all works fine.

 

However - when attempting to do the same tasks from powershell - the command fails as there is a problem with the probing path. The ideablade assemblies are looking for the ibconfig file in the powershell directory rather than in the directory in which they reside.

 

I've tried using reflection to load the dll containing the commandlets from a specific directory and also tried creating various app.config files for my assembly and also for the ideablade dll's... I can't see a way to get the third party dll's to look in their own directory (or any other directory)  to get the ibconfig file / write trace logs.

Following the devforce troubleshooting guide, I have added an assembly attribute in my assemblyinfo.cs to request unrestricted access.

 

Has anyone tried to do a similar thing before - or does anyone have any ideas?

 

Thanks,

Jason