New names of the protected directories in ASP.NET

New names of the protected directories in ASP.NET

  • /Bin becomes /Application_Assemblies
  • /Code becomes /Application_Code
  • /Resources becomes /Application_Resources
  • /WebReferences becomes /Application_WebReferences
  • /Data becomes /Application_Data
  • /Browsers becomes /Application_Browsers
  • /Resources becomes /Application_GlobalResources
  • /LocalResources becomes /Application_LocalResources
  • /Themes becomes /Application_Themes
Published Tuesday, August 31, 2004 4:46 AM by sanjeebsarangi

Comments

Tuesday, August 31, 2004 5:18 AM by Lorenzo Barbieri

# re: New names of the protected directories in ASP.NET

Why not Microsoft_DotNet_Framework_ASP_NET_Application_Assemblies...
It seems that the marketing genius that has created the name Microsoft Office Word 2003 has something to do again... :-)
Tuesday, August 31, 2004 6:22 AM by TrackBack

# re: ASP.NET 2.0 System foldere

Tuesday, August 31, 2004 8:27 AM by Paul Wilson

# re: New names of the protected directories in ASP.NET

While I'm thrilled that the new directories (like Code) have more obtuse names now (so fewer conflicts), I can't at all comprehend why the Bin folder has been renamed. Not only is this changing something that's already been a standard part of .NET, its also something that has long been accepted practice in many other platforms.
Tuesday, August 31, 2004 9:37 AM by Christian Romney

# re: New names of the protected directories in ASP.NET

+1 MSDN Camp, -1 Raymond Chen Camp.

These names are horrible. At the very least just drop the Application part and leave it:

_Assemblies
_Code
_Data

+1 on the sentiment that bin was just fine - these are developers we're talking about not can't-double-click-users. We know bin is short for binaries...
Tuesday, August 31, 2004 9:47 AM by TrackBack

# ASP.NET Proposed Directory Name Changes

This is just retarded. The best thing to do would be to leave the directory names as is - especially for the bin directory so that moving sites to Whidbey will be as painless and familiar as possible. This gratuitous name changing is retarded. Sure, it may seem innocuous all...
Tuesday, August 31, 2004 10:49 AM by Jeff Julian

# re: New names of the protected directories in ASP.NET

Dumb, just dumb.
Tuesday, August 31, 2004 12:25 PM by J. Ambrose Little

# re: New names of the protected directories in ASP.NET

I agree; these names are unusable.
Tuesday, August 31, 2004 1:13 PM by Jerry Pisk

# re: New names of the protected directories in ASP.NET

I don't understand why the names can't be spelled out in web.config. That way everybody could have their own, some would use simple names (/bin, /code, /data and so on) and some would use complicated ones (possibly versioned, and so on). Why does it have to be hardcoded?
Tuesday, August 31, 2004 3:36 PM by John W

# re: New names of the protected directories in ASP.NET

Why...why...why? From simple to complicated.
Tuesday, August 31, 2004 7:06 PM by Douglas Reilly

# re: New names of the protected directories in ASP.NET

I imagine that the /bin folder will still be supported, to allow backward compatibility.
Thursday, September 02, 2004 10:03 PM by TrackBack

# .Net 2.0 -

.Net 2.0 -
Sunday, September 19, 2004 2:06 AM by Dean Stelow

# re: New names of the protected directories in ASP.NET

Dumb.
Saturday, December 27, 2008 4:48 PM by nick_eltlir

# re: New names of the protected directories in ASP.NET

http://www.message_varerc.com/

Friday, April 10, 2009 11:49 AM by nick_noouro

# re: New names of the protected directories in ASP.NET

www.message_orsittrouca.com

Leave a Comment

(required) 
(required) 
(optional)
(required)