Hi!I'm trying to get custom activities to work on a new ILMserver (RC0). The ILM server works fine except fo this problem.I've installed the activity library (my own, Cortego.ILM.Workflow.Activities) to the GAC and it shows up without problems and I've also tried withthe Ensynch Diagnostics Activity with the same result and both have worked as expected on the ILM2 RC0 VHD. I've added the ActivityInformationConfiguration objects, restarted ILM service and executed IISResetbut noneof the activities shows upin theactivity pickerwhen creating or editing workflows.I've checked many times that the assembly name, typenamesandworkflow typesare correct in the Activity Information Configuration, even installed Reflector to get the exact type namesand assembly name.I've tried using both debug and release versions of the assembly.I've tried installing it to the GACusing both using drag and drop and GacUtil and it have worked every time.The assembly resides in the C:\Windows\assembly\GAC_MSIL directory.I've been checking the assembly binding and it seems the assembly gets bound successfullywhen I open the Workflow object from within the portal...=== Pre-bind state information ===LOG: User = **********'LOG: DisplayName = Cortego.ILM.Workflow.Activities, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b88d7150cfc8f36b(Fully-specified)LOG: Appbase = file:///C:/inetpub/wwwroot/wss/VirtualDirectories/80/LOG: Initial PrivatePath = C:\inetpub\wwwroot\wss\VirtualDirectories\80\binLOG: Dynamic Base = C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\d8019b2bLOG: Cache Base = C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\d8019b2bLOG: AppName = 175ae297Calling assembly : (Unknown).===LOG: This bind starts in default load context.LOG: Using application configuration file: C:\inetpub\wwwroot\wss\VirtualDirectories\80\web.configLOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Aspnet.configLOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\config\machine.config.LOG: Post-policy reference: Cortego.ILM.Workflow.Activities, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b88d7150cfc8f36bLOG: Found assembly by looking in the GAC.LOG: Binding succeeds. Returns assembly from C:\Windows\assembly\GAC_MSIL\Cortego.ILM.Workflow.Activities\1.0.0.0__b88d7150cfc8f36b\Cortego.ILM.Workflow.Activities.dll.LOG: Assembly is loaded in default load context....But still it doesn't show up.My next plan is to download andinstall Visual Studio on this machine to try to find out what happens but until then...Does anyone have any ide why this doesn't work?//Henrik Henrik Nilsson - Cortego http://blog.softconstruction.se

I made it work by installing Visual Studio and run a build with this post build action..."C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\gacutil" /i "$(TargetPath)"copy $(TargetPath) C:\inetpub\wwwroot\wss\VirtualDirectories\80\_app_binnet stop identitymanagementservicenet start identitymanagementserviceiisresetI don't know why, the only difference from what I'vetried beforeis that there nowis a copy of the dll in C:\inetpub\wwwroot\wss\VirtualDirectories\80\_app_bin directory but maybeit didn't workbecause I've only been restarting the "Microsoft Identity Lifecycle Manager Service" from within the Services console.Anyone got a clue?Henrik Nilsson - Cortego http://blog.softconstruction.se

Was there a referenced assembly that didn't exist on the machine before you installed VS? When you opened the assembly in Reflector, did it have problems finding a reference assembly? I've seen similar problems when you compile the assembly for x86, but you already confirmed that it was MSIL.

Hi Joe!No, there was only pure .Net assemblies, .Net Framework 3.0and 3.5 was installedand as I've said I had the same problem with your diagnostics activity (the stand alone one) and there was no questions in Reflector to open additional assemblies.Anyway, I managed to solve theproblem installing VS and making a build,unless anyone knowsif a "net stop/net start identitymanagementservice" differs from restarting the service from the service console or if the assembly has toreside in the "C:\inetpub\wwwroot\wss\VirtualDirectories\80\_app_bin directory" any moderator can close this thread (I don't want o take credit for solving my own problem).Henrik Nilsson - Cortego http://blog.softconstruction.se