2

I'm having some trouble with namespacing for a web application project - front-end files are being compiled into separate assemblies under the ASPX.directory1_director2_directoryn_filename namespace format and I want everything in one dll.

I found this question and setting the -o flag would appear to be exactly the solution I'm looking for. However I build my code in VS2010 using the standard Build menu option and I can't find anywhere I can set it. Can anyone point me in the right direction?

Community
  • 1
  • 1
immutabl
  • 6,857
  • 13
  • 45
  • 76

2 Answers2

2

I suppose you meant aspnet_compiler. Here is a tutorial. It's related to Visual Web Developer 2008. But the basic idea is the same - use the External Tools dialog to create you desired action.

Andrei Schneider
  • 3,618
  • 1
  • 33
  • 41
  • Thanks for the link - I *did* mean the aspnet_compiler :-o I took a look at the available options in the MS documentation - would I be right in thinking its the `-fixednames` option that is doing this and that it is set by default in Visual Studio? – immutabl Feb 19 '12 at 23:28
  • I don't know exactly. Create a little project in VS and compile with aspnet_compiler it will take not more that 5 minutes. Also this http://stackoverflow.com/questions/2702111/aspnet-compiler-fixednames-does-not-work can be useful for you – Andrei Schneider Feb 19 '12 at 23:42
  • That works pretty well, thanks! It seems to pick up errors in the front-end (markup files) that the regular build process misses. eg. example badly formed tags. – immutabl Feb 21 '12 at 14:34
1

If you're using a Web Site Project, the ASP.NET compiler options can be used from the Publish dialog. For a Web Application Project, you can use Web Deployment Projects to enable pre-compilation (technically, WDP should work for WebSites as well).

Jimmy
  • 27,142
  • 5
  • 87
  • 100