Home ›
ASP.NET Forums » Visual Studio » Visual Web Developer 2005 Express » How Do I configure VWD 2005 Express to be compatible with DOTNET 1.1 ?

How Do I configure VWD 2005 Express to be compatible with DOTNET 1.1 ?

Last post 01-08-2007 1:11 PM by Mikhail Arkhipov (MSFT). 4 replies.

Sort Posts:

  • How Do I configure VWD 2005 Express to be compatible with DOTNET 1.1 ?

    01-08-2007, 5:50 AM
    • Member
      point Member
    • seanstanley
    • Member since 01-07-2007, 8:02 PM
    • Posts 7

    HI -

     I have built a simple site using VWD 2005 Express in Visual Basic and I believe it is using DotNet2.0 (ASPNET 2.0?).

    The package I have subscribed to on the host site (Pipex) only accepts websites that run in DotNet 1.1 according to technical support.

    If I want them to give me DotNet 2.0 privalleges my monthly subsciption will triple in cost. 

    Is there a way to tell VWD 2005 that my website should run in DotNet 1.1?

    This is all I know - it is a long road of discovery with many brick walls.  Please can you help?

  • Re: How Do I configure VWD 2005 Express to be compatible with DOTNET 1.1 ?

    01-08-2007, 7:45 AM
    • Member
      point Member
    • seanstanley
    • Member since 01-07-2007, 8:02 PM
    • Posts 7

    Me again -

    Is this the problem?  When I installed VWD 2005 I also installed ASP.NET 2.0.  When I create a new website is the code automatically configured as ASP.NET 2.0?  I have enclosed my web.config code for your review.

    <

    add key="dotnet" value="1.1" />

    I thought that this line in my web.config file should be compatible with the pipex server. 

    Note the line :

    <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

    is giving me 50+ messages that read/:

     "could not find schema information for the element" (as above)

    Here is my web.config code: - CAN YOU HELP?

     

    <?xml version="1.0"?>

    <!--

    Note: As an alternative to hand editing this file you can use the

    web admin tool to configure settings for your application. Use

    the Website->Asp.Net Configuration option in Visual Studio.

    A full list of settings and comments can be found in

    machine.config.comments usually located in

    \Windows\Microsoft.Net\Framework\v2.x\Config

    -->

    <

    configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

    <

    appSettings>

    <

    add key="dotnet" value="1.1" />

    </

    appSettings>

    <

    connectionStrings/>

    <

    system.web>

    <

    trust level="Medium" processRequestInApplicationTrust="true" />

    <

    customErrors mode="Off"/>

    <!--

    Set compilation debug="true" to insert debugging

    symbols into the compiled page. Because this

    affects performance, set this value to true only

    during development.

    Visual Basic options:

    Set strict="true" to disallow all data type conversions

    where data loss can occur.

    Set explicit="true" to force declaration of all variables.

    -->

    <

    trace enabled="true" localOnly="false" mostRecent="true" pageOutput="true" />

    <

    compilation debug="false" strict="false" explicit="true" />

    <

    pages>

    <

    namespaces>

    <

    clear />

    <

    add namespace="System" />

    <

    add namespace="System.Collections" />

    <

    add namespace="System.Collections.Specialized" />

    <

    add namespace="System.Configuration" />

    <

    add namespace="System.Text" />

    <

    add namespace="System.Text.RegularExpressions" />

    <

    add namespace="System.Web" />

    <

    add namespace="System.Web.Caching" />

    <

    add namespace="System.Web.SessionState" />

    <

    add namespace="System.Web.Security" />

    <

    add namespace="System.Web.Profile" />

    <

    add namespace="System.Web.UI" />

    <

    add namespace="System.Web.UI.WebControls" />

    <

    add namespace="System.Web.UI.WebControls.WebParts" />

    <

    add namespace="System.Web.UI.HtmlControls" />

    </

    namespaces>

    </

    pages>

    <!--

    The <authentication> section enables configuration

    of the security authentication mode used by

    ASP.NET to identify an incoming user.

    -->

    <

    authentication mode="Forms" />

    <!--

    The <customErrors> section enables configuration

    of what to do if/when an unhandled error occurs

    during the execution of a request. Specifically,

    it enables developers to configure html error pages

    to be displayed in place of a error stack trace.

    <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">

    <error statusCode="403" redirect="NoAccess.htm" />

    <error statusCode="404" redirect="FileNotFound.htm" />

    </customErrors>

    -->

    </

    system.web>

    </

    configuration>

     

     

     

     

     

     

     

  • Re: How Do I configure VWD 2005 Express to be compatible with DOTNET 1.1 ?

    01-08-2007, 7:45 AM
    • Member
      point Member
    • seanstanley
    • Member since 01-07-2007, 8:02 PM
    • Posts 7

    Me again -

    Is this the problem?  When I installed VWD 2005 I also installed ASP.NET 2.0.  When I create a new website is the code automatically configured as ASP.NET 2.0?  I have enclosed my web.config code for your review.

    <

    add key="dotnet" value="1.1" />

    I thought that this line in my web.config file should be compatible with the pipex server. 

    Note the line :

    <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

    is giving me 50+ messages that read/:

     "could not find schema information for the element" (as above)

    Here is my web.config code: - CAN YOU HELP?

     

    <?xml version="1.0"?>

    <!--

    Note: As an alternative to hand editing this file you can use the

    web admin tool to configure settings for your application. Use

    the Website->Asp.Net Configuration option in Visual Studio.

    A full list of settings and comments can be found in

    machine.config.comments usually located in

    \Windows\Microsoft.Net\Framework\v2.x\Config

    -->

    <

    configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

    <

    appSettings>

    <

    add key="dotnet" value="1.1" />

    </

    appSettings>

    <

    connectionStrings/>

    <

    system.web>

    <

    trust level="Medium" processRequestInApplicationTrust="true" />

    <

    customErrors mode="Off"/>

    <!--

    Set compilation debug="true" to insert debugging

    symbols into the compiled page. Because this

    affects performance, set this value to true only

    during development.

    Visual Basic options:

    Set strict="true" to disallow all data type conversions

    where data loss can occur.

    Set explicit="true" to force declaration of all variables.

    -->

    <

    trace enabled="true" localOnly="false" mostRecent="true" pageOutput="true" />

    <

    compilation debug="false" strict="false" explicit="true" />

    <

    pages>

    <

    namespaces>

    <

    clear />

    <

    add namespace="System" />

    <

    add namespace="System.Collections" />

    <

    add namespace="System.Collections.Specialized" />

    <

    add namespace="System.Configuration" />

    <

    add namespace="System.Text" />

    <

    add namespace="System.Text.RegularExpressions" />

    <

    add namespace="System.Web" />

    <

    add namespace="System.Web.Caching" />

    <

    add namespace="System.Web.SessionState" />

    <

    add namespace="System.Web.Security" />

    <

    add namespace="System.Web.Profile" />

    <

    add namespace="System.Web.UI" />

    <

    add namespace="System.Web.UI.WebControls" />

    <

    add namespace="System.Web.UI.WebControls.WebParts" />

    <

    add namespace="System.Web.UI.HtmlControls" />

    </

    namespaces>

    </

    pages>

    <!--

    The <authentication> section enables configuration

    of the security authentication mode used by

    ASP.NET to identify an incoming user.

    -->

    <

    authentication mode="Forms" />

    <!--

    The <customErrors> section enables configuration

    of what to do if/when an unhandled error occurs

    during the execution of a request. Specifically,

    it enables developers to configure html error pages

    to be displayed in place of a error stack trace.

    <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">

    <error statusCode="403" redirect="NoAccess.htm" />

    <error statusCode="404" redirect="FileNotFound.htm" />

    </customErrors>

    -->

    </

    system.web>

    </

    configuration>

     

     

     

     

     

     

     

  • Re: How Do I configure VWD 2005 Express to be compatible with DOTNET 1.1 ?

    01-08-2007, 1:04 PM
    Answer
    You can't. VS 2005 and VWD only work with .NET 2.0. For 1.1 there is VS 2003 or Web Matrix.
    Thanks

    ------------------------------------------------------------

    This posting is provided "AS IS" with no warranties, and confers no rights.

  • Re: How Do I configure VWD 2005 Express to be compatible with DOTNET 1.1 ?

    01-08-2007, 1:11 PM

    You technically can do it to an extent, but you have to understand that you are on your own there. If you only use 1.1 features, what you create in VWD Express will work on 1.1. However, this assumes that you know what exactly can and cannot be used. Some tips can be found here:

    http://blogs.msdn.com/mikhailarkhipov/archive/2004/07/27/199312.aspx

    Again, this practice is not supported and if what you make in VWD won't work in 1.1, you'll have to figure out what is broken and why on your own.

    Thanks

    ------------------------------------------------------------

    This posting is provided "AS IS" with no warranties, and confers no rights.
Page 1 of 1 (5 items)
RSS Available

Contact | Advertise | Ads by BanManPro | Running IIS7
All Rights Reserved. | Terms of Use | Trademarks | Privacy Statement
© 2009 Microsoft Corporation.