I can build DNN 4.8.2 successfully in Visual Studio 2005, but there are nevertheless a lot of annoying errors, warnings and information level messages in the Error List which ideally I'd like to clean up.

I think the reason is possibly due to the decision of DNN core developers to place import directives in web.config using the <namespaces> tag? I'm not very familiiar with this technique and I'm sure there's a good reason for using it (presumably to save typing??), but I normally like to put 'using' statements (working in C# - or Imports in VB of course) at the top of each code module and add references to each project when working in ASP.NET, and as a consequence the Error List stays nice and clean. As a result, I found the apparant errors listed to be confusing as a newcomer to DNN, thinking that something was wrong when, probably, it was not.

Can anything be done to clean it up, or must we just put up with it - presumably by just closing the Error List or turning off the Errors, Warnings and Messages buttons?

Apologies if this has been covered elsewhere - a link to the relevant posting will be an acceptable response.