I've added a new control to my aspx files and noticed that not only was the new control not added to the designer file but that it was also missing quite a few other controls that were added by other members of the team. I've tried deleting the designer.cs file and using "Convert to Web Application" with no success. Some other things i've tried have been excluding the aspx from the project, building, and then re-including with no success. I've also manually entered in a control that was missing in the designer into the designer. When I run after do so an error appears saying the control isn't defined, even though it actually is, and that I should check if I'm missing a directive.
The first control I added was copy and paste from a similar control and made necessary changes. But, i've also tried manually creating the control with the same results.
Any ideas?
Close Visual Studio, then delete Temporary ASP.NET Files from
C:\Windows\Microsoft.Net\Framework\Your_.Net_Version\ProjectName
Delete the folderProjectName
and re-start Visual Studio. I had a similar issue some time ago and it was solved by these actions.If you use IIS, you may need to stop the server/site to be able to delete the temp files.
I've been suffered this problem in my work.
The surest thing is you regenerate your .designer.cs file, and here is the solution:
I did this in VS2012:
That's it.
I was able to solve the problem only manually adding the control declaration inside the code behind file. Every time I tried to regenerate the design.cs file, VS 2013 would write the same lines without the missing control.
The declaration needs to be added in the code behind, NOT in the design.cs, because it would be deleted each time the .aspx is changed.
Just add the declaration like you would do for any other variable, something like this:
Just to add to the list of possible solutions: These lines in my markup file, although seemingly valid, were apparently causing a disconnect with the designer file:
I simply commented them out, saved, and the designed file began working correctly. I then uncommented both lines, saved, and was able to add new controls to the page without issue. I found this strange, and it's still unclear to me what the initial cause of the problem was. I can only speculate that it's a Visual Studio bug.
Point being, there may be perfectly valid code that's causing an issue, in which case, a possible solution would be to go through commenting HTML sections out in your markup file until the designer file resolves itself, and then you can undo all your commenting and resume working as normal.