Organizing file resources in VS 2003 / VSS environment

[Sandor Palfy]

I have a VS solution with 3 c# class library projects and an "asp.net
web application" project. The whole stuff is under integrated source
control provided by VSS. The application is under development, I use
copy project/[only files needed to run this application] frequently to
deploy and test it.

I need to store different external resources (text files, documents,
etc.) in a separate folder. These should not be accessible via http at
all, they're only used by the application. Question is: where should I
put this folder whitin the solution so that it is deployed with copy
project but can't be accessed from the web.
If I just put it into the web app project, it's going to be served via
http. I tried different web.config settings like putting the following
into the web.config:
<httpHandlers>
<add verb="*" path="ResourceDir/*"
type="System.Web.HttpForbiddenHandler" />
</httpHandlers>
Didn't work.
I'd prefer a solution which would completely prevent accessing these
files from the web, like somehow moving this folder outside the virtual
directory, but I don't know how to do that without sacrificing the
simple deployment.
What's the best way to handle this problem?

Regards,
Sandor

[Kevin Spencer]

Put them into a web directory that has all HTTP permissions removed.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.

"Sandor Palfy" <go**********@netchan.cotse.net> wrote in message
news:11**********************@c13g2000cwb.googlegr oups.com...

I have a VS solution with 3 c# class library projects and an "asp.net
web application" project. The whole stuff is under integrated source
control provided by VSS. The application is under development, I use
copy project/[only files needed to run this application] frequently to
deploy and test it.

I need to store different external resources (text files, documents,
etc.) in a separate folder. These should not be accessible via http at
all, they're only used by the application. Question is: where should I
put this folder whitin the solution so that it is deployed with copy
project but can't be accessed from the web.
If I just put it into the web app project, it's going to be served via
http. I tried different web.config settings like putting the following
into the web.config:
<httpHandlers>
<add verb="*" path="ResourceDir/*"
type="System.Web.HttpForbiddenHandler" />
</httpHandlers>
Didn't work.
I'd prefer a solution which would completely prevent accessing these
files from the web, like somehow moving this folder outside the virtual
directory, but I don't know how to do that without sacrificing the
simple deployment.
What's the best way to handle this problem?

Regards,
Sandor

[Sandor Palfy]

Hi Kevin,

Could you elaborate this a bit more? Where can I set HTTP permissions
on folders in a VS 2003 solution?

Regards,
Sandor