ASP.NET Compiler Utility Updated

December 06, 2005 @ 10:28 am

I’ve updated my ASP.NET Compiler Utility to take advantage of the ASPNET_MERGE.EXE utility that’s part of the Visual Studio Deployment projects so you can now merge the compiler output into a single assembly or one assembly per directory. The merge utility provides for repeatable compiles and this tool can now take advantage of it.

While the Web Deployment projects tool mitigates some of the need for this tool and even adds a few additional features like the ability to override web.config settings, it still is handy for compiling Web applications when Visual Studio is not present or if you are using Visual Web Developer (for which the Web Deployment Projects add-in doesn’t work).

Feedback for this Weblog Entry

re: ASP.NET Compiler Utility Updated
by Bob Archer December 06, 2005 @ 11:24 am

How would you add a strong name key to the single assembly file?

BOb

re: ASP.NET Compiler Utility Updated
by Rick Strahl December 06, 2005 @ 11:46 am

Signing is not supported by this wrapper tool, but ASPNET_MERGE does support the key file signing...

My immediate question is - why would you ever sign an ASP.NET application? What do you gain by that?

Adding support for that is easy, but I left it off to not clutter the interface with a feature of questionable value.

re: ASP.NET Compiler Utility Updated
by AsbjornM December 13, 2005 @ 7:58 am

The utility list multiple v2 frameworks, but it looks like it is only iterating the folders, not actually checking what versions is installed.
If you compile the application as updateable, then all norwegian characters are removed from the ascx files.
This also happens when I use the webdeployment tool from ms, so I guess it is Microsoft that still hasn't learned that there still is an world outside usa.. :)

re: ASP.NET Compiler Utility Updated
by Rick Strahl December 22, 2005 @ 3:05 pm

Yes you're right but there's no reliable way to check installed framework versions short of parsing into folders. This is an admin tool so we're assuming you know which version of the framework you'll want to target.

As to the norwegian characters I'm not sure. This is not caused by this tool but by the ASPNET_COMPILER or the ASPNET_MERGE since those are actually doing the compilation.

My guess is that you should make sure that your actual source file documents are saved as UniCode or UTF-8 documents, not just as ANSI text.

Peter Bromberg's UnBlog: Binary XML with your SOAP, Dear?
by Peter Bromberg's UnBlog October 04, 2006 @ 11:47 pm

DotNetSlackers: ASP.NET Compiler Utility Updated
by DotNetSlackers Latest ASP.NET News October 13, 2006 @ 3:11 am

Peter Bromberg's UnBlog: 12/2005 - 01/2006
by Peter Bromberg's UnBlog February 15, 2007 @ 8:14 am