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.
Related
I had a previously running ASP.NET Core MVC application working fine on local IIS in Visual Studio when I hit the PLAY button, however some other sites and applications I was working on, on the same computer, did not run on IIS Manager when browsing directly to them from IIS manager or running them in Visual Studio.
Most applications that uses HTTPS for example mentioned that the "Remote Certificate is invalid for the validation procedure message". Yet for some other sites that used IIS Express, it worked fine.
What I have done to try to fix this is:
Removed the original IIS Self Signed Certificate from IIS Manager
Then deleted the website that was working fine
I then used GIT to clone the repository the application is located in
When I opened the solution again that previously worked in Visual Studio it gave me the following message about creating a new IIS Certificate:
Message I get when opening visual studio after deleting the already Self Signed IIS Express Certificate for Local development
Initially I hit YES to this which may be the cause of the problem
Now when I run the application that previously was working and seemed to be using LOCAL IIS, it keeps defaulting to IIS EXPRESS I can see beside the play button
Is there anyway I can put this back to running on LOCAL IIS for my ASP.NET Core MVC application? I cannot see it listed even in the IIS Manager on my computer.
Thanks
Henry
How can I configure Web Deploy on Windows 10? Should it work?
I found information about Web Deploy on Windows 8, there it isn't working.
How is it in Windows 10?
Microsoft is being super sneaky about this, but it appears they have removed the ability to use web deploy remotely from ALL non server os's. Even in Windows 7, if you do all of the newest updates, the deploy menu vanishes in IIS. So if you want to use web deploy it seems like your only option is to shell out some bucks for a server os.
HOWEVER, I was able to get FTP publishing configured and working on my Windows 10 machine, which works almost as well. Just install the FTP server under control panel => programs and settings => install windows components. Then open iis mgr and right click on your site and a configure FTP publishing option should pop up. The configuration is a pain and not straightforward, but if you mess with it you'll figure it out.
Then in Visual Studio right click on your project, hit publish, then in the first screen in the drop down there is the good old fashioned ftp option. Good luck!
EDIT
From OP's response, another solution is to simply share the root folder on the server, so for example
C:/inetpub/www
Then mount that share on your development box, I mounted it as the P:\ drive for production, and Q:\ drive for qa. Then in visual studio on the publish screen just select deploy to file system and deploy to that mapped drive, works like a charm and is far simpler than setting up FTP.
Ok, I did this (in Windows 10):
Uninstalled Web Deploy 3.6 from control panel(didn't help).
Downloaded Web Deploy 3.6 installer, then ran uninstall from the installation menu.
Downloaded Microsoft Web Platform Installer 5.0.
From the Web Platform Installer 5.0, I installed Web Deploy 3.5 + Web Deploy 3.5 without bundled SQL Support
I seem to have the deploy context menu back when I right click a site.
Make sure you do the following:
Install web Deploy 3.6
Go to Server Manager > IIS
Under Server Roles go down to Web Server (IIS), expand this tree and select Management Tools.
Make sure "Management Service" is checked
Go to Services, Make sure "Web Management Services" is started. (go ahead and make it automatic while you're in there).
Now you'll see the "Configure Web Deploy Publishing" option under the Deploy menu on IIS. From there make sure you have port 8172 open from the IP you are publishing from.
Installing WebDeploy 2.1 (available from the Web Platform Installer) gives you a 'Deploy' option on your website in Windows 10
See: https://serverfault.com/questions/253292/why-dont-i-have-deploy-actions-available-in-iis-7-manager
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 trying to host a asp.net razor v3 website to IIS, but it is not working. I tried multiple options including first creating the website then publishing to IIS, or directly creating a new website under IIS using visual studio 2013. It gives me HTTP Error 503. The service is unavailable.
Methods to reproduce Error:
Option 1
1) Create a new asp.net web site (razor v3) in visual 2013, and click publish to publish to a directory. Then, add that directory as a website in IIS.
Option 2
1) On the new website window, in visual studio 2013, go to browse and select IIS, and create a virtual directory directory under IIS to save the site.
Then, go to the browser and try to access the hosted site: localhost/sitename, it always produces some kind of errors. Like 503. What am I missing? Please help, looks like I am missing some steps or some configuration changes.
Also, I am trying this with the default razor v3 webiste content and without modifying anything. So, I have not touched any files or anything, I am just trying to upload to IIS.
The correct answer I found was that for some reason you must use the IIS Express 8.5 to test/host that site.
Even the installations on the fresh copies of Windows with Full IIS prior to version 8 did not work on my test machines.
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/