-
Posted to
IIS 7.0 - PowerShell
by
daemonoid
on
03-10-2009, 5:36 AM
Hi, forgot about this help request. Thanks for the reply, my understanding has moved on a lot now.
My problem was not the powershell command, but the registering of the COM object itself. It turns out that powershell was caching the dll meaning when i did:
.\gacutil.exe /u MyDll
.\RegAsm.exe /u MyDll.dll
.\RegAsm.exe ...
-
Posted to
IIS 7.0 - PowerShell
by
daemonoid
on
02-16-2009, 3:53 AM
Thanks Paul, but it's not really the problem I have. I actually have to use regasm rather than regsvr32 as my dll is managed .Net code.
My problem comes after the registering of the .dll - a quick registry search shows that my classes within the .dll are registered. It's the powershell step:$yourProviderConfig = new-object ...
-
Posted to
IIS 7.0 - PowerShell
by
daemonoid
on
02-15-2009, 6:25 PM
Probably...
I'm completely new to powershell, I just need to perform a simple set of commands to get my dll installed and integrated with my server ( http://msdn.microsoft.com/en-us/library/bb802799.aspx ).
I'm stuck on the first powershell step:$yourProviderConfig = new-object –ComObject
...