You can "de-couple" individual folders in Microsoft Expresson by right clicking the site and selecting Convert to Folder.Īn additional concern is that Expression always tracks the full path for publishing so if we want to publish a file from \\IISDEV\what you actually end up with is your file being published to \\IISTEST\The whole idea of working in your Development server and then publishing to your Testing server only works for subsites as long as the full path is identical.ĭuring our testing our support engineer and I noticed that Expression was slow when editing and manipulating files. We discussed writing a script that recursively descended through the directories deleting the FPSE metadata files however there is the danger that the sites still depended upon code and other other information stored on them. As I understand it, if somewhere further down the directory tree from Development_Intranet\Unrelated_Site there are leftover files, publishing to your site at Development_Intranet\Site_I_Actually_Care_About will fail since the whole thing is contained in a single IIS Site.
![microsoft expression web for windows 10 microsoft expression web for windows 10](https://imag.malavida.com/mvimgbig/download-fs/microsoft-expression-web-4448-3.jpg)
The FPSE metadata files are not just limited to one "site" in the sense of your folder path. Here's what was going on:Īt some previous point FrontPage was used to manage a site or sites within the main IIS directory ( W:\This causes Expression to detect that the site or a portion of it is managed by FrontPage and therefore invalidates it as a File System Publishing target however we can't publish to the directory using the FrontPage Server Extensions (FPSE) because while the metadata files are still there the actual FPSEs are not installed since FrontPage has been depreciated since 2006. I ended up going to Microsoft's support for this. How can I setup our web servers so our development teams can work on a website in Development and then publish it to Testing or Production without resorting to manually copying files or running a script? As someone who is not terribly familiar with Windows and IIS am I "just doing it wrong"? I would rather avoid the other connection methods (WebDAV, FTP, SFTP and Frontpage Extensions if possible). I have tried looking through the Event Log on the server and compared the IIS configuration between the two server groups and cannot find anything immediately obvious. I'm not really sure how to interpret this error but I'm going to go with "the directory the file share is exposing to Expression is already being used by IIS as the location for a web site" which if that is a correct interpretation makes this feature pretty useless (wouldn't every website you'd want to publish to also be served by IIS?). When we try to publish from the Development server to the Testing server we get the following error: This works for one group of servers but not for another. We are connecting with the web servers by exporting the IIS drives as file shares that the developers can then map or use in Expression. The goal is for the developers to check out their source code to their workstation, then publish to Development, then Testing and then finally to Production using Expression.
![microsoft expression web for windows 10 microsoft expression web for windows 10](https://www.shoplack.com/upload/detail/20140909003521.gif)
Our web servers are all built on Windows Server 2008 R2 and IIS 7.5 and come in a group of separate Development, Testing and Production servers.
![microsoft expression web for windows 10 microsoft expression web for windows 10](https://www.majorgeeks.com/content/file/3640_enable+or+disable+save+passwords+with+microsoft+edge+in+windows+10.jpg)
Some of our developers use Microsoft Expression Web to author their ASP and ASP.NET web applications.