I'm using visual studio 2012 and i have a windows form app. the iis express server is configured by default with visual studio 2012.
I have to publish my windows form app. For that, i have create a storege object on azure platform.
But when i try to publish the project using clickonce i have that issue :
Error 83 The Web server does not appear to have FrontPage Server Extensions installed. If FrontPage Server Extensions are installed, this error can occur because the _vti_bin virtual directory is not marked as executable. To correct this problem, run Internet Information Services Manager, select the Web server that has the problem, and then use the Check Server Extensions command.
Screen shot :
https://docs.google.com/file/d/0B-aV0dsLT4CaemZuQV93Ymt4UVE/edit?usp=sharing
I had no issue during the creation of my storage object on azure, and the URL is good !
I have installed de FrontPage Server Extension several times and normally it's good.
i really need to publish my project, if someone can help me ...
Thanks for help.
You are trying to do HTTP publish to a server that doesn't have FPSE installed. FPSE was no longer available after Server 2008 (I'm guessing here, I just know it's not available for newer versions of Windows Server).
Instead of doing HTTP, use FTP. So you FTP the files to the web server, and use an HTTP link for the customer to access them.
For example, your publishing file location might be
ftp://myserver.com/myfolder/
and your installation URL would be something like
http://myserver/thefolder/
Related
I have two machines: Windows 10 Pro, and Windows 10 Home. I have enabled IIS on both of them. From both machines, going to IIS -> File -> About shows this dialog:
One might assume that I'm dealing with the full version of IIS simply due to the lack of the word "Express".
Is there any simple way to confirm if a machine has full or express installed?
IIS Express is normally installed into your 32-bit Program Files folder. So, to see if it's there you can try:
C:\>cd "\Program Files (x86)\IIS Express"
C:\Program Files (x86)\IIS Express>iisexpress /?
Full IIS is normally installed as a service called "World Wide Web Publishing Service" or "w3svc" for short. So, to see if it's there you can try:
C:\>net start w3svc
You opened IIS Manager to see such a dialog and IIS Manager is only part of full IIS, while IIS is part of Windows.
If you want to check that in code, then there are other ways such as checking Windows CBS data, or reading registry key.
IIS Express is completely another software, which is an MSI package to be installed either with Visual Studio or individually. To test its installation, you either check the Programs dialogue as the comment said, or query MSI data or registry keys.
If you have IIS manager installed, you have full IIS.
IIS Express is part of Visual Studio and appears in the Windows system tray when you run a web application/web site from within Visual Studio.
I have a multi site Azure based web application. One site contains the web pages (with the view functionality driven through jQuery, Raphaël, and HTML) and a thin WCF service. The second site contains a more functional WCF service which in turn calls the data objects that call the database. We stopped development on the site a few years ago but it is still live for the few people who still enjoy using it.
Yesterday I had to fix an cross-site scripting vulnerability someone had reported on the site.
I was alarmed to find that I can no longer run the sites on my local machine under Visual Studio to test and debug any changes before deploying them to Azure.
Because of the interaction between the two WCF sites I had the local debugging set up as follows:
In the Internet Information Services Manager tool (InetMgr) I add additional websites with their physical path set to the location of the source code in the TFS local path on my machine.
I edit the host name in the site's binding to mimic the Azure location, i.e. the main site is projname.cloudapp.net:80 on Azure and projnamelocal.cloudapp.net:80 in my local IIS and the data WCF site is projname-wcf.cloudapp.net:8080 on Azure and projname-wcflocal.cloudapp.net:8080 in my local IIS. (N.B. The main site has a HTTPS binding too.)
I edit C:\Windows\System32\drivers\etc\hosts to include the lines
127.0.0.1 projnamelocal.cloudapp.net
127.0.0.1 projname-wcflocal.cloudapp.net
In Visual Studio I edit the web properties for the main site's project so that it uses the local IIS and project URL http://projname.cloudapp.net/ and I have a switch (in the code to say whether to call the local WCF or the live Azure one.
In the past when the project was under active development this set-up worked fine for locally testing and debugging. Yesterday it failed, one one machine http://projnamelocal.cloudapp.net/ gave a 503 error on another a 404. (N.B. I can ping each URL from the command line so the hosts redirect is working.) Visual Studio complains that it is "unable to start debugging on the web server" and that it "could not start ASP.NET debugging".
I've tried all the suggestions and some:
Running without debugging
Running Visual Studio as administrator (I was already)
Re-registering ASP
Changing the app pool
Giving everyone full permissions to the code directory
Running as my own domain account that is an admin on the local machine
Changing IE to not auto-detect proxies
Adding the sites to IE's list of trusted sites
Turning off IE's protected mode
Restarting Visual Studio
Restarting the PC
Restarting the PC again
How should I set-up this style of running, testing, and debugging local sites work in IIS under Visual Studio?
Got it.
I had forgotten to go to Control Panel > Programs > Turn Windows features on or off > .Net Framework 4.5 Advanced Services > WCF Services > HTTP Activation
Now that I have that installed the local sites start
I am very new to web development and so I am also very new to Aptana Studio and IIS. I just installed both on my computer today. I read instructions on Aptana Studio's help system about adding a web server, but it does not seem to work for IIS.
I have IIS 7 running locally on my machine. In Aptana, I went to Servers --> Add Server --> Simple Web Server. Then I gave it the following parameters in the dialog:
Name: IIS
URL: http://localhost:80
Document Root: C:\inetpub\wwwroot
The server then appeared in the Servers View, but status was N/A and the preview of any website would still use the built in web server included with Aptana.
My Google searching has not found any more specific instructions for configuring Aptana with IIS.
I have had some success by going to the Debug Configurations, from there you can switch the launch location (and browser executable) with a combination of radio buttons. To access the menu, click on the pull down next to the debug button.
I am working on getting web deploy set up on IIS 7.5. I have followed the steps exactly in this article:
http://www.iis.net/learn/publish/using-web-deploy/configure-the-web-deployment-handler
I have tested importing and exporting applications on the server and all work perfectly. Now I would like to set up remote access to ms deploy so I can install web applications by publishing in visual studio 2012 with publish profiles.
Here is where I am confused, what is the url I include in this for the service url (ie. msdeploy.axd)? Where I can find it on the servers iis (server is located on different machine than visual studio)? I have read about access is over port 8172, how can I check that this is open for communication?
Thanks for any help
First up, the installation instructions you want are Installing and Configuring Web Deploy in the "Install" section of the site. The instructions you linked are from 2008.
Once you've installed MSDeploy v3 as per the newer instructions, the MSDeployServiceURL value will be https://webserver:8172/msdeploy.axd. You'll also probably need to set <AllowUntrustedCertificate>true</AllowUntrustedCertificate> if you don't have a cert on the server.
The user in question will need to be an administrator unless you have setup non-administrator deployments (instructions in the same link).
I'm using IIS 7.5 on Windows Server 2008 R2 x64 Enterprise Edition. In the project we have developed with ASP.NET 4.0 we used WCF Service. But it doesn't run over domain when the software is running from local computer. Otherwise, I am getting the following error:
HTTP Error 404.3-Not Found
The page you are requesting cannot be served because of the extension
configuration. If the page is script, add a handler. If the file should
be downloaded, add a MIME map.
You should install IIS sub components from
Control Panel -> Programs and Features -> Turn Windows features on or off
Internet Information Services has subsection World Wide Web Services / Application Development Features
There you must check ASP.NET (.NET Extensibility, ISAPI Extensions, ISAPI Filters will be selected automatically). Double check that specific versions are checked. Under Windows Server 2012 R2, these options are split into 4 & 4.5.
Run from cmd:
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir
Finally check in IIS manager, that your application uses application pool with .NET framework version v4.0.
Also, look at this answer.
In my case, along with Mekanik's suggestions, I was receiving this error in Windows Server 2012 and I had to tick "HTTP Activation" in "Add Role Services".
In windows server 2012, even after installing asp.net you might run into this issue.
Check for "Http activation" feature. This feature is present under Web services as well.
Make sure you add the above and everything should be awesome for you !!!
I was having trouble accessing wcf service hosted locally in IIS. Running aspnet_regiis.exe -i wasn't working.
However, I fortunately came across the following:
Rahul's blog
which informs that servicemodelreg also needs to be run:
Run Visual Studio 2008 Command Prompt as “Administrator”.
Navigate to C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation.
Run this command servicemodelreg –i.