Trying to integrate Expression Web project with Visual Studio .Net project, EW for design, VS for coding.
Master pages seem to be the approved model for 'consistent design' including nav bar etc., but a master
page in root with navbar containing relative path
when applied to a child page in
generates a composite path:
result: a href:[siteroot]/register/news/default.htm
vs intended result:
intended: a href:[siteroot]/news/default.htm
Rather defeats the object of master pages, if we can't use them 'down' the site tree, and manually building xml sitenode maps and using or coding providers seems overkill, especially since 'consistent look and feel' (including navigation) is precisely what master pages are already supposed to provide.
~/ application roots don't seem to work either (yet I used them profusely previously in custom controls for precisely this function) with web sites located under a server virtual directory
Bad enough needing ExpressionWeb dwt + master pages for a single site, but can't imagine relying on master pages (at all) until we get this basic functionality resolved. Trying hard to like Expression Web and MasterPages, and to learn to do things 'the proper way', but all th
View Complete Post