Debugger problem “The breakpoint will not currently be hit. No symbols have been loaded for this document”

I just experienced the infamous “The breakpoint will not currently be hit”. After reading several posts in various websites in reference to this issue, I found few solutions which I thought of sharing :

• Check if the debug=”true” in your aspx page.

Debug is disable

<%@ Page Language=”C#” MasterPageFile=”~/MainMasterPage.master” AutoEventWireup=”true” CodeFile=”Facility.aspx.cs” Inherits=”_Facility” debug=”false”%>

Debug is enable

<%@ Page Language=”C#” MasterPageFile=”~/MainMasterPage.master” AutoEventWireup=”true” CodeFile=”Facility.aspx.cs” Inherits=”_Facility” debug=”true”%>

• Removing all the references in the project and re-inserting them taking care of the version used.
  Manually deleting the bin/release and bin/debug sub-directories in every project in the solution.
  De-installing and reinstalling .net framework (any version) and VS-2005
  Taking a close look at the target platform in the projects.
  Breakpoints Should come back !!

  It can be caused as the .PDB and the assembly of one of the controls would  not have been referenced at the     right place, resulting in a desync between the sources and binaries.
  By re-referencing all, and killing the bin subdirs problem will be solved.

• Goto Tools menu and select Options; check the “Show advanced build configurations” checkbox.  Now the build configurations show in the Project Properties dialog;  display will be the Project Properties dialog (Project menu/Properties).  We can now see the Configuration dropdown box.  Select “Active(Debug)” item. Check the “Define DEBUG constant” checkbox.  Rebuilt the project.  Now there is a symbols file ([project].pdb) in the current output directory. When debugged, the symbols file is loaded and breakpoints will now hit.

• Other options than can be tried are  1).  rebuilding the application many times. 2). completely deleting and redoing it from scratch (though thats not a good idea !!  ). 3).  Check whether the .pdb file is in the same location as the DLL with the same name and time. 4). Check whether project is running on the debug version of the DLL and associated files. 5).  ensured there was only one instance of the DLL, project, etc. on the machine. 6).  right clicked on a DLL that is within the Modules window, selected Symbol Settings, selected Debugging | Symbols and manually added the directory with the .pdb file – even though confirmed that this is the default location used by the project. 7).  checked that Enable Just My Code is not selected within the Symbol Settings | Debugging | General menu. 8).  tried placing the DLL in the C:\Windows32\ directory just to see if the Modules Window would “see” it. 9).  adjusting a few other things to match suggestions regarding optimization settings, etc. 10). selecting Load DLL exports within within the Symbol Settings | Debugging | Native menu (although I am not familiar with what this may actually be doing..needs some research in the weekend); this caused most of the DLL’s in the Modules window to have a listing of Exports Loaded, but did not appear to affect my issue in any way – again my DLL is not within the Modules window.

• Select the Solution node in your Solution Explorer… Select Properties from the context menu… Select Multiple Startup Projects…For each project you want to debug, select Start from the action drop down.

Microsoft Visual Studio Gallery – Products and Extensions for Visual Studio

Are you to looking to find products, extensions, and add-ins for Visual Studio.

 

Your search ends at Microsoft Website. Microsoft is providing Gallery with

Tools  (Build, Coding, Data, Documentation, Modeling, Performance, Programming Languages, Reporting, Security, Setup & Deployment,Source Control, Team Development, Testing and  Web )

Controls (ASP.NET Controls, Silverlight Controls, Sharepoint Controls, Windows Forms Controls, WPF Controls and Framework & Libraries)

Templates (ASP.NET, Office , Mobile Device, Silverlight, SQL Server, WCF, Windows Forms, Workflow and WPF)

click here to access all the above mentioned  Tools, Controls and Templates.

Happy Coding !!!

 

 

Controls

• ASP.NET Controls

  261
• Silverlight Controls

  54
• Sharepoint Controls

  36
• Windows Forms Controls

  145
• WPF Controls

  63
• Framework & Libraries

Beta 1 of Visual Studio 2010 and .NET Framework 4.0 on MSDN

Visual Studio 2010 Screenshot

Microsoft has posted Visual Studio 2010 Beta 1 and .NET Framework 4.0 Beta 1 downloads on MSDN. The public will get Beta 1 on May 20th,2009.MSDN subscribers now have access to the Beta 1 releases of both Visual Studio 2010 and .NET Framework 4.0. If you have MSDN access, go ahead and start downloading. You may also want to check out the Visual Studio 2010 MSDN Library. From what I’ve heard, performance is supposed to be significantly improved over the CTP and earlier interim builds. Also, the releases seem to work just fine with the Windows 7 Release Candidate build. Here is a list of all the downloads that subscribers now have access to:

• Visual Studio 2010 Professional Beta 1 (x86) – DVD (English)
  Includes: Professional;
• Visual Studio 2010 Remote Debugger Beta 1 (x64) – (English)
  Includes: Additional Resources;
• Visual Studio 2010 Remote Debugger Beta 1 (x86) – (English)
  Includes: Additional Resources;
• Visual Studio Team Foundation Server 2010 Beta 1 (x86 and x64) – DVD (English)
  Includes: Team Foundation Server;
• Visual Studio Team System 2010 Team Suite Beta 1 (x86) – DVD (English)
  Includes: Team System;
• Visual Studio Team System 2010 Test Load Agent Beta 1 (x86) – (English)
  Includes: Additional Resources;
• Visual Studio Team System 2010 Test Load Controller Beta 1 (x86) – (English)
  Includes: Additional Resources;
• .NET Framework 4.0 Beta 1 (ia64) – (English)
  Includes: Additional Resources;
• .NET Framework 4.0 Beta 1 (x86 and x64) – (English)
  Includes: Additional Resources;
• .NET Framework 4.0 Beta 1 (x86) – (English)
  Includes: Additional Resources;
• .NET Framework 4.0 Client Profile Beta 1 (x86 and x64) – (English)
  Includes: Additional Resources;
• .NET Framework 4.0 Client Profile Beta 1 (x86) – (English)
• Includes: Additional Resources;

On Wednesday(May 20, 2009), Microsoft will be giving out Beta 1 downloads for public consumption on the Microsoft Download Center.

Happy Coding !

Visual Studio 2010 and .NET Framework 4.0 Overview

Microsoft has released information on Visual Studio 2010 and .NET Framework 4.0, the next generation of developer tools from Microsoft.

Visual Studio and the .NET Framework deliver key innovations in the following pillars:

• Democratizing Application Lifecycle Management
• Enabling emerging trends
• Inspiring developer delight
• Riding the next generation platform wave
• Breakthrough Departmental Applications