As there anything wrong with the following approach:
I originally developed two separate modules. Module 1 can be on a page by itself but Module 2 should always include Module 1 on the same page.
Instead of placing two separate modules on the same page, I simply included module 1 as a user control within module 2. I was considering converting module 1 to a user control by it appears that this is unnecessary.
It seems to work the same whether it is 2 separate modules on same page or single module with Module1 as an embed control.
If module2 should always be accompanied with module1 view-able on same page then this embedded approach appears to be simpler.
<%@ Control Language="VB" AutoEventWireup="false" Inherits="Module2" CodeBehind="Module2.ascx.vb" %>
<%@ Register Src="Module1.ascx" TagName="Module1" TagPrefix="uc5" %>
<uc5:Module1 id="Module1" runat="server" />
I would like to know if there is any potent problem with this approach. It appears to work fine on a test system.