I've been able to develop small modules on my local machiene without any problems.

However, now my company asked me to create a module for a site, and I have a development server to use. So I installed the latest DNN site on the server, and I created my new Module (using the VB Template). However I seem to have an issue when I add an ASP control to any page.  I get the following error on the very first line of the ASCX markup file:

Namespace or type specified in the Imports 'System.Web.UI.WebControls.Expressions' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases.

Now, if I double click a control on the toolbar (ie: Panel control), it then adds a web.config file to my project and the error than vanishes! But I know that having a web.config file inside the DesktopModules' folder (ie: Project) can cause other problems. But if I delete the web.config file, the error appears again.  Anyone have any ideas how to fix this?

Using:
    Visual Studio 2010 (VB.Net) on Windows 7 (32Bit)
    IIS7.5 On Windows Server 2008 R2 (64Bit)
    In "My Project" I have "Web > Servers" set to:
        "Use Custom Web Server"
        Server URL: http://DataCentralTest

Steve:

I am at the end of my workday here, and swamped with another project.  I will try as you suggest first thing tomorrow morning and post my results.  Thanks for the input!

Crud,

I think I spoke too soon.  The previous error has indded vanished...HOWEVER...registered tag's aren't working.  For example:

<%@ Register TagPrefix="DNN" TagName="Label" Src="../../controls/LabelControl.ascx" %>
<%@ Register TagPrefix="DNN" Namespace="DotNetNuke.UI.WebControls" Assembly="DotNetNuke.WebControls" %>

<DNN:Label ID="lblTest" runat="server" Text="LabelText" HelpText="This is the helptext" />

When I hover over the text "Label" I see:
     Element 'Label' is not a known element. This can occur if there is a compilation error in the Web site, or the web.config file is missing.

Again...I am having issue with Web.config.  For some reason it's as if the project refuses to see the Web.config file that is located in the parent website.

Help!