ryan
Posts: 41
|
| Posted: 12/01/2004, 3:46 PM |
|
Before CCS 2.3.2.24 include files generated give no problems
<!-- #INCLUDE PATH="/myfilename.asp" -->
My directory structure for local testing is typically
---------------wwwroot
---------------------|----webfoldername
--------------------------------|----admin
If i bring it on a network drive, the staging server or wherever I want. Same setting applies, no generated code changes.
However CCS 2.3.2.24 changed the generated include files to
<!-- #INCLUDE VIRTUAL="webfoldername/myfilename.asp" -->
That means for every generated VIRTUAL server side includes does not actually point/reference to the path set on the staging server as if CCS 2.3.2.24 just relies on the localhost web server testing. This is tedious because either I will change the Project settings to point to the server I'm working and so on for a number of servers. Or I will manually remove every "webfoldername" for the affected pages.
<!-- #INCLUDE VIRTUAL="webfoldername/myfilename.asp" -->
This isn't exactly cute 
_________________
(\__/)
(='.'=)
(")_(") |
 |
 |
ryan
Posts: 41
|
| Posted: 12/01/2004, 3:47 PM |
|
sorry a typo on my 2nd stament what I meant was before CCS 2.3.2.24 the generated include file was
<!-- #INCLUDE FILE="/myfilename.asp" -->
_________________
(\__/)
(='.'=)
(")_(") |
|
|
|
peterr
Posts: 5971
|
| Posted: 12/01/2004, 4:34 PM |
|
Yes, this was changed since the previous ASP applications may not work with the default configuration of the new IIS 6.
This is described in CCS 2.3 product notes: http://docs.codecharge.com/studio/html/UserGuide/Intro/...WhatsNew23.html
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
peterr
Posts: 5971
|
| Posted: 12/01/2004, 4:46 PM |
|
BTW, this behavior can be changed, again if you refer to the above product notes.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
ryan
Posts: 41
|
| Posted: 12/01/2004, 5:11 PM |
|
so are you saying that users will manually adjust 
_________________
(\__/)
(='.'=)
(")_(") |
|
|
|
peterr
Posts: 5971
|
| Posted: 12/01/2004, 5:16 PM |
|
No, I'm saying that you may complain to Microsoft 
Most people went through enough changes and upgrades due to XP SP2 and other MS security patches, thus looks like you're doing quite good with only one and such minor issue 
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
ryan
Posts: 41
|
| Posted: 12/01/2004, 5:18 PM |
|
nevermind peter i'll play around with the properties on absolute and relative #include setting whatever thanx much obliged
_________________
(\__/)
(='.'=)
(")_(") |
|
|
|
wayner
Posts: 37
|
| Posted: 03/21/2005, 9:19 AM |
|
Peter,
I have a few websites from previous versions of CodeCharge Studios created from the portal sample and they work fine.
How do I go about converting them to CCS 2.3.2.24 and making them work. I have been following links in the forum without any luck. Is there documentation on the conversion process or are there samples created in CCS 2.3.2.24?
I am specifically having problems with "#INCLUDE VIRUAL" and "clsHeader" not defined.
Thanks,
Wayne
_________________
Have it your way, sort of!
1. You can have it fast.
2. You can have it cheap.
3. You can have it accurate.
Pick 2 out of the 3! |
|
|
|
peterr
Posts: 5971
|
| Posted: 03/21/2005, 10:01 AM |
|
Have you read the above product notes and changed the #include type property?
There are no conversion steps needed. You can just load a CCS 2.2 project into CCS 2.3 and regenerate.
The product support can help you resolve any additional issues, which occasionally may occur.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
