Re: Exclude from Project not available for VS2005 web projects
- From: v-schang@xxxxxxxxxxxxxxxxxxxx (Steven Cheng[MSFT])
- Date: Fri, 06 May 2005 03:28:17 GMT
Thanks for Brock's inputs,
Hi Brad,
Also thanks for sharing your user experience and feeling with us. As for
the missing "Exclude from / Include in project" in VS2005 , and different
behavior when open web project in VS.NET from IIS, here are some of my
understanding:
1. In VS.NET 2003 when we developing ASP.NET web project, we'll have a
csproj /vbproj file associated with each project. This file contains all
the files(as well as the files' info ) contained in the project. And since
asp.net 1.x project developed with VS.NET2003 rely on the IIS server,
there'll also exist the url path of the project in IIS within the
csproj.webinfo/ vbproj.webinfo. When we include/exclude file in project,
the project file will be updated. However, this project file will become
an unnecessary item when we deploy the project into product server. Also
when we are dealing with Team development which use source control
tools(vss/ cvs...), this additional project file(also those webinfo .... )
become rather useless and may cause many problems when checking in/checking
out sources.
So in asp.net 2.0, VS.NET 2005, we have changed the compilation mode and
the project structure. When developing asp.net 2.0 project in VS.NET2005,
we no longer need project file, we just make use of a well-known folder
structure when dealing with a web project. For example, the "app_data"
sub folder in asp.net 2.0 project's root folder just contains all the
database files. And "app_code" will contains the code files(for components
or utilities) need to be compiled at runtime.
One important thing is since we no longer have project file, all the files
in the project folder(it's a normal folder on file system) are treated as
an item in the project. If we don't want it or want to exlude it, we can
just remove it from the project's folder ( for example delete it or move
to other disk folders).
2. As you also mentioned that when we open a project in IIS which contains
sub applications in the sub folder, it will display all the sub projects.
This is also because the ASP.NET 2.0 project are all based on folder
structure, so project file to indicate which files are included in the
project. However, since we no longer need IIS when developing project, we
can just developing separate web project in separate physical disk folders.
We can put all the project files into a normal folder and then open it in
VS.NET 2005 , developing pages and run it in the buildin test server.
Only at the deploy time do we need IIS. And since the new compilation mode,
what we need is just copy all the stuffs in our project's root folder into
the IIS's virtual dir. If we use the procompiled feature, we also need to
copy the procompiled assembly and resources into the "bin" folder.
So I think these new features will make the asp.net developing more
flexible , not restricted to the environment( require IIS available).
Also, we will no longer encounter erros when opening project because of the
project files(csproj/vbproj or .webinfo file) 's content are corrupt for
any reason.
How do you think of this? If you have any other questions or ideas, please
feel free to post here.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
.
- Follow-Ups:
- References:
- Exclude from Project not available for VS2005 web projects
- From: Brad
- Re: Exclude from Project not available for VS2005 web projects
- From: Brock Allen
- Exclude from Project not available for VS2005 web projects
- Prev by Date: too logn viewstate
- Next by Date: Re: too logn viewstate
- Previous by thread: Re: Exclude from Project not available for VS2005 web projects
- Next by thread: Re: Exclude from Project not available for VS2005 web projects
- Index(es):
Relevant Pages
|
