Thank you. The new tagprefix, namespace and assembly attributes are a nice addition to config.web so that attributes can be defined globally and far away from the the web form level. I can see it being useful when upgrades to the Mere Mortals web controls, with a tagprefix of mm, necessitates updating the mm tagprefix’s on every page in an entire solution.

I did have to go back into all of my web forms and comment out (via ctrl-k-c) all of the @Register directives that contained the “mm” tagprefix definitions. In this way, all of my mm web controls could inherit the tagprefix, assembly and namespace defined in the new web.config. Without the commenting-out, the compiler reports an ambiguous definition for tagprefix "mm".

Also…. I finally had to uninstall mm.net 1.4 because the compiler was reporting multiple definitions for the Mere Mortal Assemblies. No biggy! Now I am in VS2005, mm.net 2.0 and ready for mm 2.1 and…. Life is beautiful once again.

PLEASE, PLEASE, PLEASE include this material in Getting Started or What’s new.

Regards and enjoy the holidays,
Neil Gorin

>Neil,
>
>>Please provide us with a snippet of what the web.config should look like before and after the vs2003 to vs2005 migration. Do web form @page directives have to be changed or is all in the web.config.
>
>Here's a good example of a web.config:
>
>

<?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">
>	<configSections>
>		<section name="databaseSets" type="System.Configuration.NameValueSectionHandler, 
         System, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
>		<section name="databases" type="System.Configuration.NameValueSectionHandler, 
         System, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
>	</configSections>
>	<connectionStrings/>
>	<system.web>
>		<!--
            Set compilation debug="true" to insert debugging
            symbols into the compiled page. Because this
            affects performance, set this value to true only
            during development.
        -->
>		<compilation debug="true">
>			<assemblies>
>				<add assembly="Mere Mortals Framework 2005, Version=2.0.0.0, Culture=neutral, PublicKeyToken=511BD18E16C7F771"/>
>				<add assembly="Mere Mortals Framework Interfaces 2005, Version=2.0.0.0, Culture=neutral, PublicKeyToken=2312FEFB461DBB0E"/>
>				<add assembly="Mere Mortals Framework Web Forms 2005, Version=2.0.0.0, Culture=neutral, PublicKeyToken=E35DC9DDAD261220"/>
>				<add assembly="System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/></assemblies>
>		</compilation>
>		<pages>
>			<namespaces>
>				<add namespace="OakLeaf.MM.Main.Web.UI.WebControls"/>
>			</namespaces>
>			<controls>
>				<add tagPrefix="mm" namespace="OakLeaf.MM.Main.Web.UI.WebControls" assembly="Mere Mortals Framework Web Forms 2005, Version=2.0.0.0, Culture=neutral, PublicKeyToken=e35dc9ddad261220"/>
>			</controls>
>		</pages>
>		<!--
            The <authentication> section enables configuration
            of the security authentication mode used by
            ASP.NET to identify an incoming user.
        -->
>		<authentication mode="Windows"/>
>		<!--
            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>
>	<appSettings>
>		<!-- Event Log, Trace Log and Transaction Log settings:
	1. The EventLog Level setting (options are "Error", "Warning", "Info", and "Verbose"
	2. The name of the machine on which the event log resides, default is "." (local machine)
	3. The name of the log
	-->
>		<add key="EventLog\Level" value="Verbose"/>
>		<add key="EventLog\Machine" value="."/>
>		<add key="EventLog\Name" value="Application"/>
>		<add key="TraceLog\Machine" value="."/>
>		<add key="TraceLog\Name" value="Application"/>
>		<add key="TransactionLog\Machine" value="."/>
>		<add key="TransactionLog\Name" value="Application"/>
>		<!-- If set to false, indicates the application is not localized,
	and uses hard-coded strings for displaying messages and
	for user interface text. If true, specifies the application uses
	mmMessageMgr to data-drive application text.
	-->
>		<add key="LocalizeApp" value="true"/>
>		<!-- Specifies the primary key of the default application language
	(for localization purposes). Only used when LocalizeApp="true"
	-->
>		<add key="DefaultLanguage" value="1"/>
>		<!-- Specifies the database key for application messages
	This key doesn't need to be specified if there is only one
	database in your application specified in the <databases> element.
	Only used when LocalizeApp="true"
	-->
>		<add key="MessageDatabaseKey" value=""/>
>		<!-- Specifies the database key for application security tables
	This key doesn't need to be specified if there is only one
	database in your application specified in the <databases> element
	-->
>		<add key="SecurityDatabaseKey" value=""/>
>	</appSettings>
>	<databases>
>		<add key="Northwind\Connection" value="server=(local);uid=sa;pwd=;database=NorthWind;"/>
>		<add key="Northwind\DataAccessClass" value="DataAccessSql"/>
>	</databases>
></configuration>

>
>Best Regards,