> Or you might just change it back later.
No, there IS a difference.
For example, if you taken a file out of project, the "Copy Project" button
on the solution panel won't copy that file to the new location. Similar
things happen when you try to add the project to the source safe.
Although you can still view to file on the local web server, the excluded
file is no longer considered as part of the project when you attempt to do
any action targeted to "the project".
"Gabriel Magaña" <no-spam@no-spam.com> ¼¶¼g©ó¶l¥ó·s»D:O4GWafwPGHA.4044@TK2MSFTNGP15.phx.gbl...
>> Or you might just change it back later.
>
[quoted text clipped - 3 lines]
> Projects extension), so there is no such thing as excluding the file and
> then renaming back to the original name without including it again.
Evian Spring - 17 Mar 2006 15:56 GMT
For your coment:
Actually I think "renaming when a file is taken out of a project" is a
right
We have a "build.props" file for our NANT script.
This prop is different for every developer because they all have a
different working directory on their machine.
We do not want to include this file in the solution but it needs to be
at the root of the project.
Now if you rename it to .exclude, NANT will give you a compilation
error that builds.prop doesn't exists.
So it's not a good idea to rename....it's a catch 22
They should create a .exclude file that list all the files to be
excluded.......not renaming the actual file
Also you rename an image for an example.....How can a browser know a
.exclude is a jpg for example?