Is Delta Publish & Deploy for ASP.NET 2.0 Possible?

[Douglas J. Badin]

I am using VS 2005 to Publish my ASP.NET 2.0 Website with the following:

- Not allowing this precompiled site to be updatable
- Use fixed naming and single page assemblies
- Not Enable strong naming on precompiled assemblies

As it is, I get around 300 files in the bin directory and it takes almost 10
minutes to copy them.

I am using code-behind and was wondering if I change the code-behind of only
1 page, can I copy only a subset of the bin files, ie. the assembly of the
page that changed and the associated .compiled file. I have tried it
without success. Maybe I am missing another file?

I prefer not to make the publish updateable so I don't have to copy the
extra .aspx files and I want to keep the code-behind and use the precompiled
performance increase.

Thanks,

Doug

 

[S. Justin Gengo [MCP]]

Doug,

Yes, you should be able to deploy just the subset of .dll files you need.
The file you are most likely missing is the application's main .dll file
which will change as you change each page. That file should bear the same
name as the web project itself.

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche

 

[Steven Cheng[MSFT]]

Hi Douglas,

For the ASP.NET 2.0 precompilation, if you choose the "non-update" and
"fixed name", the compiler will precompile all the page's aspx template
file as well as the codebehind code files. So the resulting aspx file is
just a placeholder(no html markup or code directives in it). And after such
precompilation, there will results to some precompiled assemblies together
with some xxxx.compiled files in the bin dir. These files are used to mapp
the aspx page to their precompiled assembly. We need to make sure these
files are also updated when we update the assembies. In addition, make sure
the page your modified or updated does not have relation or reference to
other assembly which require recompilation of other page/component.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)