Messages
Reply
Edit
Delete03:56 pm
3PW0Y5KVX
| From: | Roy M |
| To: | Rick Strahl |
I agree that I don't want my code in the inetpub\wwroot. So, how do I tell the application as to the location of the wcs files?
Do I first set up a virtual directory in IIS ... and point it at the physcial location ...
Then do I have to configure the application to know where to grab the template files. Which file do I modify? The 'Cutsom'.ini file? The web.config file that was created in the intepub\wwroot\myapp folder?
Thanks in advance
Your virtual folder can live anywhere as long as IIS and the account running it has access to the folder. So if you want your program files (your EXE and data) and the virtual Web files in a single directory structure you can certainly set it up that way by pointing the virtual at that folder.
Personally I never store anything in \inetpub\wwwroot - my own applications usually have their own self contained structure with Web and Code folder where Web is the virtual path and the code folder is where all the code and data live. Makes the whole thing a bit more portable for backup and copying if needed as well as finding stuff when somebody not familiar with Web Connection tries to figure out where things live.
+++ Rick ---
+++ Rick ---
Rick,
For backing up the code created, along with any scripts created, I want to make sure when I do a backup that everything is included in the backup. For instance, I have the development stuff on D Drive and have placed the code for a specific web application into sub folder. I want to place the wcs files also into a subfolder for that application
Should I create a virtual folder ( Via IIS) and point it to the d drive subfolder where the wcs files are located?
Thanks
Hi Roy,
Not sure I understand your question.
WCS files can be anywhere in the application's virtual path - as long as you reference them properly in your code, or your scriptmap is set up properly for direct referencing without any code in a process class.
Direct accessed WCS files (no code in process class) are found based on the script map for the virtual (or root app). Process class mapped .wcs links are mapped to methods which in turn find WCS files either via physical path or by explicitly mapping to the Config.cHtmlPagePath folder - but in either case your code specifies the path.
+++ Rick ---
It appears that the WCS files need to be stored in the root of the inetpub\wwroot\(yourwebsite) folder.
I would like to place the wcs in the root of the applicaiton folder ... so that I can make sure I've got all files I need under one directory for a particular application.
What's the best way to handle this.
Thanks in advance
Roy