"Fetching schema" message when no database code is being exercised
I was working with a short piece of C# code, and when I ran the code, a "fetching schema" message was displayed that took a really long while to time-out. After several tries, I realized that I had an invalid (out of date) connection (to a long-lost database that I no longer used). Deleting the connection fixed the problem, and the C# code ran fine afterwards. (And yes, it was the first time I had invoked LINQpad in a while.)
My question: Why is LINQpad even trying to fetch a schema when the C# code does not make use of any database?
I am running the very latest release.