Web Client Software Factory Tip: Changing Module Assembly Names
by David Hayden ( Sarasota Florida .NET Developer ), Filed: Web Client Software Factory
I am developing a Web Client Software Factory Application for the Day of Patterns and Practices Event on Friday, May 25th in Tampa Florida ( Register ) that shows off a number of best practices as well as all the cool features Enterprise Library 3.0 brings to the table in terms of validation, policy injection, etc. I ran across this simple tip during the development process.
At some point during your development you may change the name of your assemblies / modules being built using the Web Client Software Factory. Maybe you decide to change the name of the assembly Shell to MyCompany.CoolApp.Shell.
When you do this, you need to make sure you specify the new assembly name in the <modules> section of the corresponding web.config or you will get an error that the assembly cannot be found during application startup. Hence the default setting of
<compositeWeb>
<modules>
<module
name="Shell"
assemblyName="Shell"
virtualPath="~/" />
</modules>
</compositeWeb>
would need to be changed to:
<compositeWeb>
<modules>
<module
name="Shell"
assemblyName="MyCompany.CoolApp.Shell"
virtualPath="~/" />
</modules>
</compositeWeb>
to reflect the new change in the assembly name.
Source: David Hayden ( Sarasota Florida .NET Developer )
Filed: Web Client Software Factory