You searched for the word(s): userid:629622

More Search Options

RSS Available

• Re: "http://schemas.microsoft.com/.NetConfiguration/v2.0"

  Scott, Thanks very much. That's solved the deployment problems. Ewan

  Posted to Configuration and Deployment (Forum) by ewanc on 4/24/2006

• Re: "http://schemas.microsoft.com/.NetConfiguration/v2.0"

  ScottGu: 2) The issue that you have above ewan is at runtime, and is caused because you are deploying a V2.0 application in an application directory configured to use V1.1 instead. That is why it isn't recognizing any of the new schema tags in V2.0. To fix #2, go into the IIS admin tool (inetmgr) and pull up the properties for the application you are deploying the app into. You can then click on the "ASP.NET" tab in the properties window and map the application to use V2.0 instead of V1.1. This error

  Posted to Configuration and Deployment (Forum) by ewanc on 4/21/2006

• Re: "http://schemas.microsoft.com/.NetConfiguration/v2.0"

  This is not good advice. The problem is that IIS defaults to .NET 1.1 (even if .NET 2 is installed after IIS) - this error is generated from the 1.1 framework. Removing the xmlns tag gives you: Parser Error: Unrecognised configuration section 'connectionStrings' This error message may change depending on what .NET 2.0 features are in the web.config file. The footer of the error page specifically mentions 1.1.4322 The answer needed is: How can you programmatically change the default .NET version for

  Posted to Configuration and Deployment (Forum) by ewanc on 4/20/2006

• Re: Using VS2005 to deploy ASP.NET applications

  It's not the publishing step that's a problem, it's creating a setup.exe with an associated MSI file. This installs a web-application as a version 1.1 application. There are no obvious VS options that can change this behaviour. I cannot ask my end users to configure their IIS installation (this is a medical application, so computer knowledge among the end users has to be assumed to be very low.) I need a "single-click" deployment solution. Ewan

  Posted to Configuration and Deployment (Forum) by ewanc on 1/18/2006

• Using VS2005 to deploy ASP.NET applications

  I'm in the process of writing a web application that uses ASP.NET 2.0. I've been using a web-deployment project (as seen on your home page) to create the precompiled output which then goes into a web setup project. This seems to build the required MSI file, but when I try to install this on a server with both .NET 1.1 and 2.0 on it, the setup program always creates an ASP.NET 1.1 application. The only way I can get the application to work is by hand-configuring IIS to use 2.0 with that virtual directory

  Posted to Configuration and Deployment (Forum) by ewanc on 1/17/2006

• Specifying "serializeAs" with a custom ProfileBase

  I've been attempting to implement some simple Profile code by inheriting from "ProfileBase", e.g.: public class Settings : ProfileBase { /// <summary> /// Get the list of tab pages for this user /// </summary> public List<TabPageBase> TabPages { get { List<TabPageBase> result = base["TabPages"] as List<TabPageBase>; if (result == null) { base["TabPages"] = result = new List<TabPageBase>(); } return result; } set { base["TabPages"] = value; } } The class "TabPageBase

  Posted to Getting Started (Forum) by ewanc on 10/21/2005