So I've used the upgrade wizard and successfully upgraded a couple of modules.  Now I have one that I've tried to upgrade twice but it's not building.  It's odd, after building it shows errors/warnings for the GLOBAL.ASAX.VB for some reason which is preventing the build.  If I delete the folders for the new WSP module I'm trying to add to the solution and take it out of the web.config build order then the errors/warnings go away.  Any ideas?

The "errors" I get in the Global.axax.vb file:

Type 'EventArgs' is not defined.

Name 'Config' is not declared.

Name 'ServerName' is not declared.

Name 'Initialize' is not declared.

Type 'HttpApplication' is not defined.

Type 'HttpRequest' is not defined.

The (3) warnings I get in the Global.asax.vb file:

Namespace or type specified in the the Imports 'Dotnetnuke.Security.Roles' doesn't contain any public member or cannot be found.  Make sure the Namespace or type is defined and contains at least one public member.  Make sure the imported element name doesn't use any aliases.

This warning above is also shown for "Imports Dotnetnuke.Services.Log.EventLog" and "Imports DotNetNuke.Services.Upgrade"

This is now happening on other modules that are very simple.  It seems I am no longer able to convert modules over.

It's the exact same errors/warnings even with trying to port over a new module.

Thanks Mike.

Sometimes you have to close and re-open Visual Studio...