Author Topic: One reason not to use Web Expression?  (Read 1764 times)

Offline goserver

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
One reason not to use Web Expression?
« on: March 08, 2011, 09:54:37 AM »
Hallo,
I have a customer with an intranet. This runs now on a W2003 Server with the Frontpage Extensions installed. There are more than 100,000 pages and more than 200,000 Hyperlinks. 99% of the pages are ASP pages with includes etc. ... everything works really nice and fast for more than 10 years.

Right now we use Frontpage, SharePoint Designer 2007 and/or WebExpression 4.0 to do the page editing (as I said, no problems, very happy)  :)

Now we have a new server W2008R2 with IIS 7.5. (No more Frontpage Extensions!)
Access to the webs ist working with WebExpression and WEBDAV.

Now the big drawback:
When we move a single image from one folder to another one, we get broken links. Ok this is because the frontpage extensions are missing. But when I open a page in WE and move the file, the opened page is changing the hyperlink (but only the open file).

Also, only when you connect via file share, you can get broken Hyperlink-Report, right?

The feature of automatically updating hyperlinks is so essential that I might go back to IIS 7 where the frontpage extension are still available.

I am wondering very much that we see rarely any comments on this essential feature. To check the integrity of the Hyperlinks afterwards is not of much use. Nobody uses this?

Question: Is there any other add-in available, which automatically updates hyperlinks?

Thanks for a comment/tip!!!
 

Offline Cheryl D Wise

  • Forum Mom
  • Administrator
  • Hero Member
  • *****
  • Posts: 1312
  • Karma: +3/-0
    • View Profile
    • by-expression.com
Re: One reason not to use Web Expression?
« Reply #1 on: March 08, 2011, 10:56:52 AM »
FYI, Web Expressions is not a program owned by Microsoft.

If you mean Expression Web then you need to go to Site > Site Settings and use the checkbox to manage the site using meta data. That is what allows Expression Web to update pages not open when you are working in a locally defined site. I do not think it will do so if you are working live on a server since Expression Web needs access to the temp directory on the machine that is hosting the site. You rarely have that when working directly.

I do not use WebDav so have little knowledge of how it works so if using meta data is either not available to you or doesn't work and you have to work live on the server I'd suggest asking on a group dedicated to WebDav.

Personally, I have no desire to ever work live on a site and avoid it like the plague. I much prefer to work locally and if multiple people will be working on a site either use a CMS (content management system) or a versioning application like Subversion or Team Foundation Server.
Cheryl D Wise
MS MVP Expression Web
by-expression.com for tutorials & blog

Offline goserver

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: One reason not to use Web Expression?
« Reply #2 on: March 08, 2011, 11:15:16 AM »
Thnaks for your comment (and I am sorry - did not know that Web Expression is another product).

In the Site settings there is this nice feature "Use Microsoft Expression Development Server" ... I will test this one, maybe this has also some CMS features ... or most likely will show me the ASP pages also locally.

Actually the customer has 2 websites, 1 Live Website and 1 for production. Then he puplishes from the the production to the Live website. But about 5-10  people have access to the the production site. ... I will check out the CMS (Team Foundation Server) ... but all of the webpage authors are very happy with MS Expression Web 4 ...

Also I read now that they are working on the Frontpage Extensions for IIS 7.5 ...
« Last Edit: March 08, 2011, 11:20:15 AM by goserver »

Offline Cheryl D Wise

  • Forum Mom
  • Administrator
  • Hero Member
  • *****
  • Posts: 1312
  • Karma: +3/-0
    • View Profile
    • by-expression.com
Re: One reason not to use Web Expression?
« Reply #3 on: March 08, 2011, 11:30:22 AM »
Expression Web doesn't have CMS features - that would be something like Drupal, Joomla, DotNetNuke. TFS is version control so people can get the latest version from the site to work on locally.

The local development server only runs ASP.NET, PHP (when installed), HTML & JavaScript. So if you are using Classic ASP you would need to preview using the production server and a custom url.
Cheryl D Wise
MS MVP Expression Web
by-expression.com for tutorials & blog