The Forum has been Updated
The code has been upgraded to the latest .NET core version. Please check instructions in the Community Announcements about migrating your account.
I had v3.4.05 suddenly break on me and I decided the best bet was to go right to 3.4.07 - I couldn't get to first base on the install due to (IMHO) a quirk in asp.
I had Expression Web 4 set to publish removing all html comments. Of course as asp users know, there are a lot of "Includes" used in the Forum code. Originally our ISP loaded all the 3.4.05 code on the system and I only made a few mods and hence never discovered this problem. After publishing 3.4.07 I found that EW4 was not publishing the #INCLUDE FILE directives (as I had specified without ill effects up to today). Of course with the INCLUDEs stripped out of the code 3.4.07 was DOA. It took me a while to figure this but if anyone else has this problem maybe you'll find this post.
Why is the world is a server side directive like #INCLUDE properly encased within a comment field? Oh well... Dave
I had Expression Web 4 set to publish removing all html comments. Of course as asp users know, there are a lot of "Includes" used in the Forum code. Originally our ISP loaded all the 3.4.05 code on the system and I only made a few mods and hence never discovered this problem. After publishing 3.4.07 I found that EW4 was not publishing the #INCLUDE FILE directives (as I had specified without ill effects up to today). Of course with the INCLUDEs stripped out of the code 3.4.07 was DOA. It took me a while to figure this but if anyone else has this problem maybe you'll find this post.
Why is the world is a server side directive like #INCLUDE properly encased within a comment field? Oh well... Dave
Postet den
Thanks for posting about it 
.
.
Postet den
What would Expression Web have to do with asp includes? asp includes are placed in html text in an asp page, not within the <% asp delimiters. The asp page is processed by IIS and includes are loaded before any asp code begins to execute. Expression Web is a design program, unless there is some web server included in IIS Expression Web won't be in the picture.
#INCLUDE FILE behaviour changed with newer versions of IIS when 'parent paths' were changed to be disabled by default. This could cause any include file using relative paths (i.e., ../../file) to fail in newer IIS when they worked fine in older IIS versions,
#INCLUDE FILE behaviour changed with newer versions of IIS when 'parent paths' were changed to be disabled by default. This could cause any include file using relative paths (i.e., ../../file) to fail in newer IIS when they worked fine in older IIS versions,
Postet den
Doug, it sounds like he was using Expression Web 4 to publish his site, and it was stripping out all the HTML Comments when doing so.
http://www.expression-web-tutorials.com/ew4/ew4-website.html
Looks like it can use any of the below methods to "publish" the site:
FTP, SFTP, FTPS, FrontPage Server Extensions, WebDav, or File System.
http://www.expression-web-tutorials.com/ew4/ew4-website.html
Looks like it can use any of the below methods to "publish" the site:
FTP, SFTP, FTPS, FrontPage Server Extensions, WebDav, or File System.
Postet den
I'd blame Expression Web for not being able to distinguish between comments and includes, it's not exactly difficult.
Search is your friend
“I was having a mildly paranoid day, mostly due to the
fact that the mad priest lady from over the river had
taken to nailing weasels to my front door again.”
Search is your friend
“I was having a mildly paranoid day, mostly due to thefact that the mad priest lady from over the river had
taken to nailing weasels to my front door again.”
Postet den
Oh, so it wasn't about a server issue but a problem with Expression Web incorrectly handling page source. Thanks for the clarification!
ASP includes ARE just an html comment. It's the content of the html comment that the asp interpreter looks at to determine it's an include, but from the html view it's just another html comment block. It wouldn't surprise me at all if any non-MS html editor that stripped html comments would merrily remove asp includes, but it is a little surprising that Microsoft's own html editor would do so.
I have an older copy of expression web kicking around, maybe I should try it out again.
ASP includes ARE just an html comment. It's the content of the html comment that the asp interpreter looks at to determine it's an include, but from the html view it's just another html comment block. It wouldn't surprise me at all if any non-MS html editor that stripped html comments would merrily remove asp includes, but it is a little surprising that Microsoft's own html editor would do so.
I have an older copy of expression web kicking around, maybe I should try it out again.
