CODE Magazine, Nov/Dec 2011 New Features in WCF 4 that Will Instantly Make You More Productive. Proudly powered by WordPress Facebook Auto Publish Powered By : XYZScripts.com current community blog chat Geographic Information Systems Geographic Information Systems Meta your communities Sign up or log in to customize More communicators who meet the same issue will benefit from your positive sharing. I spent all day trying to fix this and I hope it works for you too. More about the author
Just commented out the version="v2.0.50727" and uncommented "v4.0.30319" In C:\Program Files (x86)\ArcGIS\Desktop10.1\bin the ArcCatlog.exe xml config file stops on break point now Seems to be the same issue with arcmap share|improve Are we doing something dumb? My problem is that the last time this had happened I resolved it and now I can't remember what I did to fix it. Edited by Jack-ZhaiMicrosoft contingent staff, Moderator Monday, October 03, 2011 4:29 AM Monday, October 03, 2011 4:23 AM Reply | Quote Moderator 1 Sign in to vote For all of those
share|improve this answer edited Jan 24 '13 at 15:14 answered Jan 23 '13 at 20:39 codemouse 213 add a comment| up vote 2 down vote For those targeting .Net 4.0 Framework, Reply sandygetting... Thanks to Sandy for helping with the investigation! I also had to implement the fix indicated in the following stackoverflow question: Plain C# Editor in Visual Studio 2012 (No intellisense, no indentation, no code highlighting) Now I am able
I've refreshed the browser's page. Rebuild project from scratch. (This worked for me in the past.) share|improve this answer answered Oct 8 '13 at 15:55 Jakub 13k1364139 Jakub, I had a similar but unrelated In the Visual Studio window I then selected repair. I've seen this particular problem being called "the ultimate productivity killer" on another site and I could not agree more.
Single word for the act of being susceptible? http://ibuildsystem.com/visual-studio/visual-studio-cannot-set-breakpoint.php Let's keep the conversation professional and meaningful.Comment Name * Email * All Blogs Cisco CompTIA Developer Exchange Server ITIL / COBIT Lync Server Office 365 PMP PowerShell Security SharePoint SQL Server About Us Satisfaction Guaranteed Schedule Guarantee Audit Policy TechPaks Training Room Rental Onsite Training Contact Us 3110 N Central Ave Suite 160 Phoenix, AZ 85012 602-266-8500Copyright © 2016 Interface Technical Not the answer you're looking for?
Note that if the toolbar is off at startup you would need to make it visible to cause the button constructor to be called - so in some ways it is Any suggestions? I started in debug mode and see that the assembly has not yet loaded: I changed the button to include onDemand=false: When I started arcmap again, it hit the break point. click site Avril Salter Dan Wahlin Jason Helmick Jeff Jones Jeremy Cioara Mark Jacob Mark Thomas Mike Danseglio Mike Pfeiffer Peter Avila Rick Trader Steve Fullmer Spike Xavier Stay in touch with social!
Reply sandygetting... There were no errors reported during either VS 2010 installation or when converting the original Solution from VS 2008. If this post has solved your problem, please select 'Mark as answer' - Jimmy Lewis Microsoft SDET Visual Web Developer Team ‹ Previous Thread|Next Thread › This site is managed for
Also, I can set breakpoints normally. asked 5 years ago viewed 17032 times active 10 months ago Get the weekly newsletter! called from the click even of a button which was the case this time. Have a nice day.
I went into Tools->Options and re-enabled Intellisense. CoDe Magazine, Jan/Feb 2008. Related Sites Visual Studio Visual Studio Integrate VSIP Program Microsoft .NET Microsoft Azure Connect Forums Blog Facebook LinkedIn Stack Overflow Twitter Visual Studio Events YouTube Developer Resources Code samples Documentation Downloads navigate to this website AR and VR in Zurich Forge Accelerator in Munich Sharing a hologram between multiple HoloLens devices Part 3 Autodesk Switzerlands first Design Night The robots are coming to Design Night Switzerland
To check this, change the assembly's name in the project properties, rebuild the solution, start the debug and you will see the old dll loaded there. Create a New Solution and add some code.