This particular error is due to a BIN deployed component that doesn't exist in my newly created application and the app is expecting the namespace which of course isn't actually there.
So this is a brand new project why these errors? Well, the problem is that the newly created app automatically inherits the root web's config settings. So if you use any custom modules, handlers, or as above even add a namespace, references that are not used in a new project down the virtual directory you'll get errors because those settings usually don't make sense in the lower virtual directories.
he slew of 'default' configuration settings that a .NET 3.5 app requires
his effectively exposed two separate server pipelines, one for native ISAPI filters and extension components, and another for managed application components
ASP.NET components would execute entirely inside the ASP.NET ISAPI extension bubble and only for requests mapped to ASP.NET in the IIS script map configuration.
With the architecture change in IIS 7, your application that was developed for IIS 6 may not function properly using the default Integrated Application Pool Pipeline Mode
Integrated Mode Benefits:
Allowing services provided by both native and managed modules to apply to all requests, regardless of handler. For example, managed Forms Authentication can be used for all content, including ASP pages, CGIs, and static file
For example, a managed module providing request rewriting functionality can rewrite the request prior to any server processing, including authentication, takes place.
For example, single module and handler mapping configuration, single custom errors configuration, single url authorization configuration.
IIS 7 has two application pool pipeline modes: Classic and Integrated. Using Integrated mode is the ideal since it allows forms authentication for all types of page requests—not just ASP.NET pages—has tighter integration with the entire pipeline, and will be leveraged by more native and 3rd party apps over time.
IIS 7's classic mode behaves in the same manner as IIS 6 and uses two pipelines to process requests, one for native-code application components and theother for managed code application components.
ntegrated pipeline mode handles all requests through a unified pipeline
Pipeline mode refers to how a Web server processes client request
IIS 7's classic mode behaves in the same manner as IIS 6, using two pipelines to process requests--one for native-code application components and the other for managed code application components.
Classic mode is where IIS only works with ISAPI extensions and ISAPI filters directl
Using classic mode, ASP.NET is simply an ISAPI extension (aspnet_isapi.dll) and an ISAPI filter (aspnet_filter.dll). When using classic mode the server uses two piplines to handle requests, one for native code and the other for managed code. In this mode the application doesn't take full advantage of everything IIS 7.X has to offer.
Integrated mode handles all requests through a unified pipeline for IIS and is tightly integrated with ASP.NET through that same pipeline
With integrated mode ASP.NET runs much more efficiently in IIS and will yield greater performance for your site.
Some legacy code may require that you run in classic mode to execute without error. To take full advantage of IIS we strongly encourage you to review your code if your application throws an error in Integrated but runs fine in Classic.