Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4119460
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T23:05:35+00:00 2026-05-20T23:05:35+00:00

I have a number of XSLT files in my ASP.NET Web Application solution. Should

  • 0

I have a number of XSLT files in my ASP.NET Web Application solution. Should these go in the App_Data folder?

The MSDN ‘Project Folder Structure’ article suggests that the App_Data folder is for ‘data files’. As XSLT files are not strictly ‘data files’ then should they go elsewhere?

I do not want end users to be able to access the XSLT files from their browsers, so App_Data seems like an obvious location for this, but I am not sure.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-20T23:05:36+00:00Added an answer on May 20, 2026 at 11:05 pm

    The App_Data folder is a perfectly reasonable; however a better option may be to “embed” the XSLT into your assemblies as a resource. This way you don’t have to worry about deploying more files. It also makes it harder for a client to look at your XSLT code (if this bothers you).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a number of xml files that should follow this format: <root> <question>What
I have a number input that should trigger jQuery on every change. To do
I am using about a dozen XSLT files to provide a large number of
Question We have a large number of xml configuration files that we want merged
I have a number of different xml files that I need to edit from
I have the following XML for my XSLT stylesheet (take note of the table-number
I have a number data-driven web based applications that serve both internal and public
I have a number of XML files containing lots of overhead. I wish to
I have used XSLT for a number of years but have never come across
I have a large number of HTML files that I need to process with

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.