467,074 Members | 921 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,074 developers. It's quick & easy.

Do I still need those .aspx page if I choose "Merge all outputs toa single assembly" in Web Deployment Project?

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.
Jan 23 '07 #1
  • viewed: 2858
Share:
2 Replies
re:
do I still need to deploy the .aspx page
What happens if you don't upload the aspx pages ?

Try it.

If the application runs without aspx pages, you don't need to upload them.
If the application doesn't run without aspx pages, you need to upload them.

Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"john sun" <js***********@gmail.comwrote in message news:ON**************@TK2MSFTNGP05.phx.gbl...
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.

Jan 23 '07 #2
hi JW,
yes you need the aspx pages. 'outputs' in terms of a web project refers to
compiled outputs, e.g. code behind and assemblies, so in that sense it does
merge all the outputs. without the aspx pages, IIS cannot respond to
requests for a given URL.
good luck
tim
"john sun" <js***********@gmail.comwrote in message
news:ON**************@TK2MSFTNGP05.phx.gbl...
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.
Jan 23 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Sean Dettrick | last post: by
1 post views Thread by mcmreddy@gmail.com | last post: by
7 posts views Thread by Randy Paez | last post: by
2 posts views Thread by Nils Magnus Englund | last post: by
5 posts views Thread by Mark Chambers | last post: by
2 posts views Thread by =?Utf-8?B?UGF1bCBMaW52aWxsZQ==?= | last post: by
1 post views Thread by mrpetegroups@yahoo.com | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.