To view parent comment, click here.
To read all comments associated with this story, please click here.
Quote" - I want to create an new ASP/.NET project: If my projet is not located in <inetpub/wwwroot> it will failed to open a web projet! I have to manually edit the solution file.
- I want to edit one of my projet's file and this project is a web application projet: he needs a communication with IIS to open the FILE by default which take ages to open! But I just wanted to open a simple file!!! "
Your statements clearly shows your inexperience in this environment... and I'm suprised that after 11 months, you could not figure this out!!! Anyone who has little experience with IIS (4,5,6) knows that inetpub/wwwroot is the DEFAULT locacion and NOT the ONLY location to create a virtual directory... If you want to create a web project in a location, you must first create the virtual directory to point to that location. You can do this from IIS manager or from the target folder's properties under the "Web Sharing" tab. You notice that I've not mentioned .net because these are simple IIS configuration tasks. You can also run asp.net under any account of your choosing. This stuff isn't magic, you have to do some work as well... my advice to you is get some training.
Edited 2006-05-22 14:49
You are right! Not that hard to get it working, but in defense of the GP with VS2003 it is a huge pain to get it to open a web project when you start moving the directories around. Sometimes it just doesn't want to work. Thankfully this has been fixed in VS2005 which has a MUCH more intuitive way of opening projects (right off the filesystem).




Member since:
2005-10-27
Honestly, your replay, and all other comments makes me wonder if you really ever developed ready-for-production application under .NET.
Let me give you an insight on how much my 11 month project using lastest .NET Framework was a nightmare as a developer.
The first things you have to know is that we are using entirely Microsoft products to do this job. So I use the visual studio development suite to code and visual source safe as a versionning system. Don't know if you noticed but, IIS is closely related to .NET to an extended where it doesn't do what you want anymore!
The common people will use IIS to server pages right? Now to Microsoft concept IIS has become more than that: it is not a web page server anymore, it has long became an application server. Thanks to this nice functionalty as an application server you end up with REALLY UGLY software designs:
- I want to create an new ASP/.NET project: If my projet is not located in <inetpub/wwwroot> it will failed to open a web projet! I have to manually edit the solution file.
- I want to edit one of my projet's file and this project is a web application projet: he needs a communication with IIS to open the FILE by default which take ages to open! But I just wanted to open a simple file!!!
- I want to deploy my application, deploying is made easy with web app because you only deploy on the server: great advantage. Ow gosh! Because my deployement machine ASP credential are under the NETWORK_SERVICE account and those on my development machine are handeled by ASP_NET (worker process) (this difference is due to the OS: Windows XP uses ASP_NET, windows 2003 uses NETWORK_SERVICE, my files access permissions settings are now wrong
- I want to get a web projet from VSS, I need to install it into <inetpub>/wwwroot again, even if it not this way in the VSS hierarchy: it automatically modifies the hierarchy according to your IIS configuration
- Seriously I plenty of other exemple like that: HTML mode edition not working, file permission problem with the ASP worker account when tryin to access ORACLE, etc
Microsoft has been trying too much to do a all-integrated solution.... IT'S TOO MUCH Please also distribute a heavily slimmed down version of IIS and your development environement.