How to maintain css , image , js linking even if we follow folder structure ?

Question

1.00/5 (1 vote)

See more:

Hii ,

I am developing webapplication , have css , js , fonts folder structures ..

now the problem here is .. when i create webforms within same project . all css , js gets applied well ..

But now i want to maintain folder structure for authorization and now all the css , js gets out of reach in that folder .. so i have to go for ../ pattern which is very hectic .. and even not sure will that be all working as many js are there and images are coming from there as well ..

Please suggest on this

Posted 29-Sep-14 6:58am

Torakami

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2014-09-29T07:19:00

Solution 1

There is no such things as miracle. If you put some files in separate directories, say, the share them in other directories, the file names have to come with some path. Use relative paths, or paths relative to the site's root directories, or mix both ways, and consider the implications, as it is done in case of nearly all kinds of software and informational products.

I never saw anyone complaining about having to take care about this basic thing before, not even anyone calling this trivial kind of decision a "pattern". I would only warn you against one thing: avoid trying to find some "site-global" pattern by using some configuration files, etc. I would only make your solution less portable and maintainable.

—SA

Posted 29-Sep-14 7:19am

Sergey Alexandrovich Kryukov

Updated 29-Sep-14 7:22am

v2

Comments

Torakami 29-Sep-14 13:40pm

ha ha ha ... lolzzz ... yehh man you are ryt . I was just reying to find the solution here ..

well what do u mena by

Use relative paths, or paths relative to the site's root directories, or mix both ways, and consider the implications

Can you please give me this details more elaborately way that would help me to solve ..

thanks SA

Sergey Alexandrovich Kryukov 29-Sep-14 14:40pm

I have no idea what else could be a problem here.
Something like "../styles/menu.css". What's wrong with that?
—SA

Torakami 29-Sep-14 14:56pm

i got confused between ~/ and ../

i thought you are talking about this differnces

Sergey Alexandrovich Kryukov 29-Sep-14 15:01pm

'~' means the root of the site, '..' means parent directory, '.' means "this very directory", like in "./rightHere.css".
So, relative to the root it would be like "~/styles/menu.css". And so on...
Sorry if you expected anything more from the answer, but I see nothing wrong with that.
—SA

Torakami 30-Sep-14 1:08am

yes thanks for clearing my doubt .

Sergey Alexandrovich Kryukov 30-Sep-14 1:47am

Sure. Will you accept the answer formally?
—SA