How useful is it to use Aspnet_compiler.exe instead of conventional Publish via Visual Studio? And what about resource (resx) files?
Asked
Active
Viewed 2,515 times
3 Answers
6
Precompilation, as opposed to simple xcopy gives you two main advantages:
The filesystem will not have all the code in
.aspxfiles and all the code behind is compiled into an assembly.There is no ASP.NET compilation delay the first time you visit a page after the server starts up.
Having said that, my precompilation knowledge is a bit rusty these days, last time I touched it was a while back.
Paul Mignard
- 5,824
- 6
- 44
- 60
Igor Zevaka
- 74,528
- 26
- 112
- 128
-
When you say no code in .aspx files, you mean any inline code in render tags are removed? – Steve Mar 03 '10 at 20:21
-
From memory the aspx file becomes just an empty placeholder - no markup and no code. Everything is compiled into an assembly. – Igor Zevaka Mar 03 '10 at 21:50
3
By pre compiling the site your server won't have to compile the site on the first visit. You have probably noticed that the first time you view an asp.net page there is a noticeable delay.
In addition you don't have to ship all your files since the code is already compiled. This can be useful if you don't trust whoever is hosting your pages.
Rune Grimstad
- 35,612
- 10
- 61
- 76
0
Visual Studio's "Publish" feature is actually just a nice frontend to aspnet_compiler.exe. Publish has the advantage of being very easy to execute, where aspnet_compiler.exe requires some tweaking to get the results you're after.
Paul Turner
- 38,949
- 15
- 102
- 166
-
aspnet_compiler.exe seems to also compile the resource files. The resx files are compiled to dll. – Bastien Vandamme Jan 08 '10 at 13:24
-
2It's all about the arguments passed to aspnet_compiler. Unfortunately, Visual Studio doesn't make those calls public. – Paul Turner Jan 08 '10 at 13:31