Hello, I am writing an extension for Forefront Identity Manager. I am using Visual Studio 2010 local to the FIM box. When I attach the debugger to miiserver.exe process I cannot set a break point with out getting "The Breakpoint will not currently be hit" message. I know the breakpoint is being hit because the breakpoint is being hit because I put in a simple stream writer in the agent and its logging eveything to my test log file. Therefore I must be doing somthing incorrectly with Visual Studio 2010. I know this error can occur when symbols files are not properly loaded. I have previously used Visual Studio 2005 and 2008 to write extensions. Can anyone clue me in. Thanks Bill

Are you doing remote debugging? If you open the Modules window (from the Debug menu) and manually load the symbols for your extension, do things work?My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Make sure you copied the pdb file along with your dll. Also in the properties tab for configuring the MA in Sync Service Manager, untick the "Run this management agent in a separate process" option

... "The Breakpoint will not currently be hit" ... This is almost always due to the fact that your code is in deifferent version from the builded dll Make sure that when you build the dll, the version in .../Visual Studio Project/.../Bin/your.dll is the same than .../2010/Synchronization Service/Extensions/your.dll Hope this helps Fabrice

Wow - so many possible reasons :). Make sure that you've compiled your extension in DEBUG mode, that the generated PDB file is located in the correct Extensions folder along with the (correct) corresponding DLL, and that you DON'T have the MA checkbox set which says to run the MA in a separate process (must run only in the main FIMSyncService process).Bob Bradley, www.unifysolutions.net (FIMBob?)

Hello, I had already done this: In visual studio 2010 Options->Debugging->Symbols I have added C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions as a symbols location. This has not changed the results. Bill

Hi, The MVExtension.dll and MVExtension.pdb files were both copied to C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions which is part of the build template for the MVExtension. The versions of the file in the visual studio build directory (C:\Users\MyAccount\Documents\MVExtension\obj\Debug) and those in the C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions are the same. I am running the management agent in the miiserver.exe process in other words I don't have the "Run this rules extension in a separate process" box checked. Thanks Bill

The two files are exactly the same in every way that I can test. Same date/time version. Bill

Hi, Compiled in Debug Mode, The PDB file is right with the DLL. I have done a Build->Clean Solution and then checked the Extensions directory (empty now). Then did a Build->Build Solution. New version of MVExtension.dll and MVExtension.pdb appear in the: C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions directory. Restarted the FIM Sychronization service. When I attache to the miiserver.exe process I still get: "The breakpoint will not currently be hit. No symbols have been loaded for this document" When attaching to the miiserver.exe process I receive a Attach Security Warning Dialog Box. I have chosen to Attach. I'm not sure what I am missing. Bill

When you attach to the process miiserver.exe, check the type, it should be Managed (v2.05...), if it is Native, it won't break. You don't need be concerned about "The breakpoint will not currently be hit. No symbols have been loaded for this document". I get that too I still can debug when the breakpoint is hit. Add a breakpoint on the constructor just to make sure your code hasn't crash out somewhere. BTW you don't have to restarted the FIM Sychronization service.

When you attach to the process miiserver.exe, check the type, it should be Managed (v2.05...), if it is Native, it won't break. You don't need be concerned about "The breakpoint will not currently be hit. No symbols have been loaded for this document". I get that too I still can debug when the breakpoint is hit. Add a breakpoint on the constructor just to make sure your code hasn't crash out somewhere. BTW you don't have to restarted the FIM Sychronization service.

Hi, Thanks I had everything set correctly. After waiting (as you suggested) for the breakpoint to actually be hit it did. In previous cases using Visusal Studio 2005 I never received the message "The breakpoint will not currently be hit". I had seed that message in other instances and in those it really didn't get hit. Hence my apprehension. Thanks Everyone.

I usually do Debugger.Launch() in the code

Hello, when i read this thread i came to another question: Is the usage of Visual Studio 2010 official supported or does is just work. hope its ok to ask this here. Thank Peter

A Happy New Year! To my limited knowledge, it should work because FIM 2010 is looking for a .Net assembly DLL which can be compatible with .Net Framework 3.0 or 3.5. Visual Studio 2010 has no problem producing that. I am considering a one time "conversion" of any Visual Studio 2008 projects into 2010 and sticking to 2010 afterwards (no mixing back with 2008). Nevertheless, it would help a lot to get a more "authoritative" (no pun intended) opinion regarding the official support for the usage of Visual Studio 2010. Any thoughts? Thanks, Radu

Visual Studio 2010 is not yet supported. Cheers, MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Thanks Markus! Can you expand if possible? Any timeframe? Any major issues or is it just a matter of not being fully tested together (similar to the SQL Server 2008 R2 process)? Best regards, Radu

It is just a matter of not being fully tested. I doubt a bit that it is VS version related - I have seen similar issues with VS2005. When you search on the ILM forum for something like "debugger" you will find similar posts. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

It is just a matter of not being fully tested. I doubt a bit that it is VS version related - I have seen similar issues with VS2005. When you search on the ILM forum for something like "debugger" you will find similar posts. Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation