ASPX: Get path of cs file_问答_开发者_运维开发者技术经验分享

开发者 https://www.devze.com 2023-01-14 03:32 出处：网络

How can I get the path of a cs file in aspx? Here\'s the issue: I\'ve created a property class in a property.cs file which is used in an EPiServer admin module. Server.MapPath() will hence return the

How can I get the path of a cs file in aspx?

Here's the issue: I've created a property class in a property.cs file which is used in an EPiServer admin module. Server.MapPath() will hence return the path of the executing file, which is in a totally different place than my code. I need to get the path of the property.cs file (from inside the property.cs file) in order to dynamically set some relative paths to css and js files. How can this be done?

I hence want to be 开发者_开发知识库able to include .js and .css files in this cs file, all files located in the same directory, but the cs file is accessed from the EPiServer UI.

I would highly recommend not doing what you are trying to do. You'll be constructing a brittle dependency on files that should not even by deployed with your project.

If you have web classes that rely on resources like javascript and css, you should use the ClientScriptManager (or ScriptManager for ajax apps) to register the script files onto the page, and the scripts and css should be deployed into their own regular web directory.

If deployment location is a problem, and you're creating some kind of reusable, redistributable module, then I would recommend that you embed the .js and .css files as WebResources in your assembly, and use the script manager to register the scripts to the page that way, with ClientScriptManager.RegisterScriptResource().

I think you should go with including your CSS, JS and other static files as embedded resources.

That will include the files inside the DLL, which makes deployment easier. You can then set up a HTTP handler which will serve you the contents of the embedded files - or use the aforementioned RegisterScriptResource() method.

By embedded the files you don't have to know any file paths.

ASP.NET is compiled, you should never need to read settings from source files at runtime, you should read from configuration files (*.config), if they need to be dynamic, these too can be injected during the page lifecycle via a variety of methods.