Skip to content

Codepolice

  • ⤫

Visual Studio Intellisense / “Go To Definition” issues

Posted by Judy Alvarez Posted on February 28, 2022March 3, 2022
0

I’m not sure how common this is but I had some issues with Intellisense and the “go-to definition”-feature in the new Visual Studio 2013, it just didn’t work. This was only happening in one of my projects/solutions (well, at least it didn’t happen in another project I tested).

Everything worked fine except this, I could debug/build my project and everything.  I’ve tried the “Clean Solution” thing and other stuff but nothing worked. I had no issues with the same project in VS 2012.

At last, I tried to delete all my *.pdb files (debug info files), I just searched for Windows at the root of my project. Found all PDB files and ctrl-x them to a temp folder. After that, i restarted Visual Studio 2013 and everything worked.

Categories: JavascriptTagged: .net core mvc form, .net framework mvc tutorial, angular net mvc, asp net core mvc grid example, asp net core mvc vs razor pages, asp net mvc 6 download, asp net mvc component, asp net mvc dashboard template free, asp net mvc form, asp net mvc hosting providers, asp net mvc layered architecture example, asp net mvc net core, asp net mvc paging, asp net mvc performance, asp net mvc pivot grid, asp net mvc programming test, asp net mvc project download, asp net mvc read csv file, asp net mvc step by step, asp net mvc tutorial pdf, asp net mvc vs asp net web forms, asp net mvc web developer, difference between asp net core and mvc, dot net mvc developer, generate barcode in asp net mvc, kendo ui asp net mvc, login .net core mvc, mvc framework .net, net mvc 6, remote asp .net mvc developers

Post navigation

Previous Previous post: Remote Desktop Connection (RDP) becomes extremely slow after installing “Intel Smart Connect Technology” update
Next Next post: New Relic and runAllManagedModulesForAllRequests flag in .net

Related Posts

  • What’s next for JavaScript frameworks in 2026

    #​770 — January 27, 2026 Read on the Web JavaScript Weekly Introducing LibPDF: PDF Parsing and Generation from TypeScript — LibPDF bills itself as ‘the PDF library TypeScript deserves’ and supports parsing, modifying, signing and generating PDFs with a modern API in Node, Bun, and the browser. GitHub repo. Documenso JavaScript Frameworks – Heading into 2026

    Posted by Posted on January 27, 2026
    0
  • require(esm) now stable in Node 25

    #​608 — January 22, 2026 Read on the Web Node.js 25.4.0 (Current) Released — Another gradual step forward for Node with require(esm) now marked as stable, as well as the module compile cache, along with a variety of other minor tweaks. Joyee Cheung of the Node team has written a thread on Bluesky going deeper

    Posted by Posted on January 22, 2026
    0
  • A big week for jQuery

    #​769 — January 20, 2026 Read on the Web JavaScript Weekly jQuery 4.0 Released — 20 years on from its original release, the ever-popular (in terms of actual usage) library reaches 4.0 with a migration to ES modules (compatible with modern build tools) along with dropping support for IE 10 and older. With jQuery being

    Posted by Posted on January 20, 2026
    0
  • A new guide to configuring Node packages

    #​607 — January 15, 2026 Read on the Web ⚠️ The Node.js January 13, 2026 Security Releases — Originally expected in December, these releases (of Node.js 25.3.0, 24.13.0, 22.22.0, and 20.20.0) finally landed this week, largely due to their complexity and the scope of the vulnerabilities they tackle. More on that in the next item! The Node.js

    Posted by Posted on January 15, 2026
    0
  • Can we ever fix the web dependency mess?

    #​768 — January 13, 2026 Read on the Web JavaScript Weekly Web Dependencies are Broken; Can We Fix Them? — Lea, who has worked at the heart of Web Standards for years, delivers a compelling (and educational) call to action about a problem every JavaScript developer has encountered: why is managing dependencies and introducing them

    Posted by Posted on January 13, 2026
    0
  • The story of how require(esm) became stable

    #​606 — January 8, 2026 Read on the Web 🎉 Happy New Year! Also, a quick reminder that Node Weekly is now sent every Thursday as part of a reshuffle for many of our newsletters. __Your editor, Peter Cooper npm to Implement ‘Staged Publishing’ After Turbulent Shift Off Classic Tokens — 2025 was a tricky year

    Posted by Posted on January 8, 2026
    0
Judy Alvarez

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Codepolice

  • Github
  • Atlassian
  • Flatlogic
  • Xero
  • Jetbrains
  • Figma
  • What’s next for JavaScript frameworks in 2026
  • require(esm) now stable in Node 25
  • A big week for jQuery
  • A new guide to configuring Node packages
  • Can we ever fix the web dependency mess?
https://flatlogic.com/generator
COPYRIGHT © 2026 - Codepolice