Avatar of dgloveruk
dgloveruk
 asked on

Visual Studio Custom Controls All stop being known elements?

I have a visual studio project with about 20 custom controls and a dozen or so aspx files to boot.
They are referenced in my web config file.
I added another custom control and soon after every custom control in my code and markup became 'X' is not a known element.
I had seen similar behaviour before in visual studio so closed the program and restarted but to no avail.  I also tried, cleaning and rebuilding.
I tried upgrading the project to a later version of Visual studio (2010 up to 2013) again no avail.
Something I noticed though, if I changed the namespace on the controls to something else the markup references changed from 'is not a known element' to 'is not registered' which suggests that the original references in the web config are being detected in some way.
Has anybody experienced something like this who might be able to offer a suggestion on how to bring the solution back into a 'buildable' state?
ASP.NET.NET ProgrammingVisual Basic.NET

Avatar of undefined
Last Comment
dgloveruk

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
dgloveruk

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes