Messages
Reply
Edit
Delete
I guess I don't understand what your problem is exactly. You're not really helping by not describing a) what you're trying to do exactly and b) what your setup is like.
I'd like to help but I'm fishing in the dark here...
If your problem is IIS configuration then either run the configuration wizard(s) or check the documentation in the help file for your specific server that explains all the configuration settings required for IIS configuration.
Another simple option too is IIS Express which is a self contained Web server that requires minimal configuration - that functionality is also available for auto-configuration in the various configuration wizards.
+++ Rick ---
Rick,
At this point I am attempting to use script files ... I have not done this with your earlier versions of wconnect. I see a real advantage to using the scripts. Having said that ...
The first script map i set up was accessed directly by typing the URL: "localhost\myweb\myscript.wcs " I found that the only way this would run, based on my current configuration, was to place the script file in the inetpbub\wwwroot\myweb folder. Further, the compiled prg was also placed in the "myweb" folder. Which led me in search of where to store the WCS files.
I truly don't know how I'm going to implement the script maps as I am just starting it. But what I am attempting to do is to ensure the files are not located physically located with the wwwroot folder.
I am wondering if the iis was set up correctly during initailization of the project. I instructed the process to create script maps ... however, I am not sure if there was a virtural folder set up. I looked at the configuration via iis manager and there was none. I have created a virtural map and pointed it to the location where I want to store the wcs files. this process was not sucessful.
Thanks in advance.
What are you doing exactly? You didn't answer the questions I had in my previous email? How are you accessing the WCS files?
If the WCS files are directly accessed without any code in methods, then the .wcs script map will automatically route to the file and process it. As long as the WCS script map is configured in IIS this will just work.
If you use a method to route, then you will have to do something like:
Request.ExpandTemplate(Request.GetPhysicalPath()) && if the page name is the same as the request name
or
Request.ExpandTemplate(Request.GetPhysicalPath() + "MyPage.wcs")
+++ Rick ---
Rick ... I'm, just not getting it. I've gone through the help file and can't seem figure this out.
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
West Wind Technologies
Making waves on the Web