Front Page 2003 code view formatting.

[John Sitka]

In this case all was fine on an XP Client until I tried a OneNote Beta that
fubarred
my FP install. Now I can't remember the settings I had that would gaurentee
no changes "at all" to code formatting. Rarely do I go into HTML view.
But even then I had things running sweet with no changes, now tabs
dissappear etc.
With a large amount of hand coded ASP JSCRIPT this is super destructive.
And blows versioning all to hell.

I run into this about once every six months.
all of a sudden empty space starts being removed on save.
Why is this and how to prevent?
In other words I need Page Options>Code Formatting> don't touch!!
Where is that?


Specifically FP2003, behaviour is removing all blank/space tab after closing
..asp tag%>

so
<%else%>
some html

<%end if%>

becomes

<%else%>some html

<%end if%>


there should be a baseline article on this from MS, should have been for
years actually. It has always been a guess. I know I'm not alone.

Thanks

 

[Dennis Blondell]

Sorry, I don't have an answer but I am responding just to support what you
are saying. I have has similar problems with FP2003. I backed up my site by
publishing to my local machine edited the old one then published it to the
net. The site failed terribly with 'if' statements and other things
disappearing I lost all my include pages <!-- #Include virtual... I went to
use the back up site and found it was the same! - Arrrgh!

When publishing in FP2003 the 'Remote Web Site Properties' has the tab
'Optimise HTML' and a check box to, what looks like an enable / disable
function. There are other options there too for optimisation. I know for
myself, the next time I publish, I will make damn sure it is not checked.
Could that be your problem too?

Dennis

 

[John Sitka]

Thanks for responding Dennis.
'Optimise HTML' yeah that rings a bell. I'm going to look for it again.
Swear to gosh I had this thing locked down and I was a clappy ham
just a few days ago. My plea is to MS to baseline these settings in a couple
articles.
The interactions of these settings is tough to understand sometimes. But I
understand
being a fringe target user for FP. The MVP response in general is that the
code is incorrect.
So, sometimes stuff is left incorrect. It's called development for a reason.
Pretty tight box when handling gigs of legacy applications. Many on mapped
shares... "tweaked live"

 

[Dennis Blondell]

Sorry, I don't have an answer but I am responding just to support what you
are saying. I have has similar problems with FP2003. I backed up my site by
publishing to my local machine edited the old one then published it to the
net. The site failed terribly with 'if' statements and other things
disappearing I lost all my include pages <!-- #Include virtual... I went to
use the back up site and found it was the same! - Arrrgh!

When publishing in FP2003 the 'Remote Web Site Properties' has the tab
'Optimise HTML' and a check box to, what looks like an enable / disable
function. There are other options there too for optimisation. I know for
myself, the next time I publish, I will make damn sure it is not checked.
Could that be your problem too?

Dennis

 

[John Sitka]

Checked it out today Dennis and really I don't publish.
I have a dedicated development webserver which is mapped as local
and the live server is mapped as local to. Basically I can just copy files
around the networks to get things done. Sucks going back to FP2002
and the main reason is I got used to looking at Arial font in code view.
Darn you MS for reneging on the finely developed neuropathways
honed other the last couple months ;-)

 

[chris leeds]

don't give up yet john, I'm sure someone in this group will know how to do
what you want to do. I'd re-post if you don't get an answer shortly. I can
think of several of the mvp/ frequent contributors that are definitely using
asp.net.