I recently added the new version of the UCS powershell toolkit and do all my scripting using PowerGUI. I import the module and I am able to see that it is there and has exported cmdlets using the get-module command. I can even run the commands and access the help topics for each command but the ability for intellisense seems to have been lost. I know I was able to do this with the previous release. I have tried every way I can think of to add the module including placing the DLLs directly in C:\Windows\System32\WindowsPowerShell\v1.0\Modules. The only thing I can think is something changed in how yall put together your DLL that might be preventing PowerGUI from compiling this information. I figure PowerGUI is pretty widely used, has any one else seen this issue and found away around it?

So a coworker just installed the new version of the UCS cmdlets and he didn't have the issue. I did some digging and it seems PowerGUI caches the help XML files in a path like "C:\Users\%user%\AppData\Local\Quest Software\PowerGUI\Commands\2.4.0.0". In here I saw previous version for my DataONTAP cmdlets and UCS cmdlets so I figured it might be a conflict but that wasn't the face. I opened the XML file inside CiscoUCSPS_x86__en-US_1.1.0.0.xml.gz and all it had was:




Obviously we are missing something in here. I replaced this with the working file from my coworker's computer and PowerGUI loaded and recognized the UCS cmdlets. Hope this helps any one else that might have the issue after upgrading the cmdlets.