J
john sun
Hi, Dear gurus,
In the web deployment project, there is one option called "Output
Assemblies page".
The first choice is "Merge all outputs to a single assembly", According
to MSDN,
"Merges all the output assemblies from the compiler into a single
assembly. This setting is equivalent to the -o assemblyname option of
the aspnet_merge.exe command. This results in the same behavior that
Visual Studio .NET 2003 supports, where one assembly is generated for
each Web project."
I assume it means all the .aspx page are already compiled into that dll,
so do I still need to deploy the .aspx page.
My experiment is "yes", but MSDN seems suggests I just need to deploy
the dll. Asp.net will generate the right .aspx page for me automatically.
thanks,
J.W.
In the web deployment project, there is one option called "Output
Assemblies page".
The first choice is "Merge all outputs to a single assembly", According
to MSDN,
"Merges all the output assemblies from the compiler into a single
assembly. This setting is equivalent to the -o assemblyname option of
the aspnet_merge.exe command. This results in the same behavior that
Visual Studio .NET 2003 supports, where one assembly is generated for
each Web project."
I assume it means all the .aspx page are already compiled into that dll,
so do I still need to deploy the .aspx page.
My experiment is "yes", but MSDN seems suggests I just need to deploy
the dll. Asp.net will generate the right .aspx page for me automatically.
thanks,
J.W.