Everyone is at a directory below your project root where some of your html pages live.
So is the other directories.
To access a directory below your project root from another directory that is below your project root then you first must move upwards to the project root, in a similar way that you navigate the folder structure in a dos prompt.
So, to navigate to the CSS directory from the Everyone directory use ../css/file-name.css the same would be true for the images and scripts directories. (note the double dot (..) to move up a single level in the directory structure)
Hi Richard, thanks for responding. I have already tried what you've suggested even before posting this question and it did not work. I tried it again just to be certain and sure enough it did not work.
The project folder I mentioned above is my project folder in Visual Studio. Basically I am using form authentication and I wanted to allow everyone to have access to certain files. So I created the Everyone folder in my project folder and configured the Web.Config file for this new folder so that all the files put in it can be accessed by everyone.
This task would generally be undertaken by a graphic designer. But if you don't have that skill then the best way is to look at lots of different websites and see which colours give a pleasing look and which ones just look wrong. You can also look at Microsoft recommendations[^].
If you're interested in the graphic design portion, I would suggest taking some Graphic design classes; even the analog design classes can give you a good grasp on the use of complementary palettes and white space.
Some schools even offer UX courses, but that's often in the CIS or even Art catalog rather than the CS one.
Or, as everyone else suggests, if you prefer to be closer to the metal you should pass that work on to someone else.
There is NO perfect way to pick colors. My advice is to make friends with some artists, join some art forums like Behance or deviant art and make use of some of these talented people, because color sense is something you have, not something you can get.
I usually ask my wife who is a Virgo and she can look at a strip of cloth or sample, go shopping and come back with an exact match. It's something they are born to do naturally.
The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file. Add <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=184.108.40.206, Culture=neutral, PublicKeyToken=89845dcd8080cc91"> to the system.web/httpHandlers section of the web.config file, or add <add name="ReportViewerWebControlHandler" precondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=220.127.116.11, Culture=neutral, PublicKeyToken=89845dcd8080cc91"> to the system.webServer/handlers section for Internet Information Services 7 or later.
I am getting the above error while I try to run RDLC report.
The following things I have added to the solution:
I have a problem running our RemoteApp from a Windows 7 client, using a non admin user account. It's fine from Windows 8, and its fine if we run it under an admin user account.
Installed remote desktop gateway under Windows Server 2012 R2 on a VirtualBox VM. The server manages a sub-domain under our company domain e.g. megabuck.com so the subdomain is WIN094263478.megabuck.com. (I'm not allowed to mess about with our domain server, for obvious reasons.)
Installed our app on the server PC, and published it as a remote app. I made sure there was an external manifest file to disable virtual store, which otherwise screws our app. Note that our app is a C++ one.
The app can be run remotely (as a remote app) from a Windows 7 client using an admin user account. It fails with a non admin account, as our app tries to create files in the program files folder, but the server prevents this.
Ideas? What is going on? Our only workaround is to set the users group as the owner of the program files installation folder.