Hello Guys,
This issue has given me an headache since yesterday so please do help !
Environment: SharePoint 2010 with Visual Studio 2012 Premium
I have created 3 Different Site Collection which is http://win500 - http://win500:1000 - http://win500:5252
As per our branding requirements, I have customized the publishing masterpage and the navigation settings while adding a class library (Navigation.cs) and mapped the control in the masterpages like below:
<%@ Register TagPrefix="LeftNavMenu" Namespace="Company.Layout.Pages.NavProvider" Assembly="Company.Layout.Pages, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3af295326c973f73" %><asp:ContentPlaceHolder id="PlaceHolderLeftNavBarTop" runat="server"><!-- Left Menu--> <LeftNavMenu:Navigation ID="leftnavigation1" runat="server"> </LeftNavMenu:Navigation><!-- Secondary Navigation Data Source --><PublishingNavigation:PortalSiteMapDataSource ID="SiteMapDS" runat="server" EnableViewState="false" SiteMapProvider="CurrentNavigation" StartFromCurrentNode="true" StartingNodeOffset="0" ShowStartingNode="false" TrimNonCurrentTypes="Heading"/></asp:ContentPlaceHolder>
The deployment was working fine since yesterday morning. (to all 3 above site collections).
However I had to modify some code in the Navigation.cs therefore redeploy the solution to the Site Collection - http://win500 - and wanted to debug it - thereafter my bad time started - I was not able to debug the navigation.cs...
Will elaborate:
- Within visual studio, I am still able to attach all the process w3wp and no error like The breakpoint will not currently be hit. The source code is different from the original version"" was coming...
- I tried to Clean - Rebuild - Delete the pdb and dll files in the bin folder and redeploy it...
- I uninstalled manually the dll from the assemblhy folder and drag it manually...
- Within visual studio, I checked all the debug settings possible...
- While reading some blogs, I disable Enable Just My Code in debugger options...
- For isolation, I deploy the same solution to the site collection http://win500:1000 and it behaves similarly...
Still the issue persists as of now and I am really stuck :(