I'm testing migration of websites to a Windows 2012 IIS 8.5. machine and when I create a Web Setup Project in VS2010 I can't find a way to get it to install on IIS 8.5 as a website. It always installs as a Virtual Directory underneath the defaultwebsite.
Is there something I'm missing? Everywhere I've read seems to say a web setup project installs things as a virtual directory. Is there no option anywhere to install as a website?
It's so simple I could kick myself...
Simply setup the website definition in IIS, then when you run the installer, in the section Select Installation Address, select the website in the top field, then blank out the virtual directory field.
This causes the installer to install without creating a virtual directory!
Related
If you see below image, there are two applications deployed to IIS.
QManualDeployment - This is deployed using Visual studio Publish feature.
InstallShieldPOCWebApplication - This is deployed using InstallShield installation tool.
Option 1 is working without any issues, but as you see InstallShieldPOCWebApplication it looks like foder rather than web site. Also it does not work.
How can I deploy application as website using INSTALLSHIELD
Here is my IIS Settings from InstallShield Tool
Default Web Site is a website. QManualDeployment is a virtual directory / application off of Default Web Site.
In InstallShield, it isn't enough to just author all of your directories/files into components. You also have to define the IIS configuration.
I'm not sure if you are using InstallShield Express, Professional/Premier of Limited Edition so I can't give you more direction then that.
I faced same issue with Post owner, after run Install Shield setup file, it show a folder in IIS and I resolved by right click to folder name and convert to Application.
I share for whom concerned.
After that we can select suitable application pool as
The Web Platform Installer fails to install Web Deploy for Hosting Servers on Windows Server 2016.
To fix this, first install the missing components using Server Manager, Manage, Add Role and Features. I think these are the ones required: Logging Tools, Request Monitor, .Net Extensibility, ASP.Net, ISAPI Extensions, ISAPI Filters, Management Service. I ended up with the following for my needs.
Next install Web Deploy 3.6 for Hosting Servers using the Web Platform Installer. (If it fails, note which components it depended on, install as above and try again.)
At this stage if you look for Deploy again in the Platform Installer it won't be installed, even though it says it was successful.
Go to Control Panel, Add or Remove Programs, find Web Deploy and choose Modify, Next, then Change.
Set IIS Deployment Handler to Entire feature will be installed, Next etc.
The Deploy menu will now appear in IIS Manager (restart it first if you already had it open) and Web Platform Installer will see that it's installed.
I tried to follow franzos answer and even though it worked in the end and resolved my issue, there was one detail missing:
At this stage if you look for Deploy again in the Platform Installer
it won't be installed, even though it says it was successful.
Go to Control Panel, Add or Remove Programs, find Web Deploy and
choose Modify, Next, then Change.
Set IIS Deployment Handler to Entire feature will be installed, Next
etc.
On my windows server core there is no "Control Panel" or other access to "Add or Remove Programs"
What resolved it for me was downloading the .msi package for WebDeploy to the server and running it from cmd.
msiexec /L msdeployinstall.log /I <path_to_msi>
This runs the installation wizard and you can change the installation with:
Set IIS Deployment Handler to Entire feature will be installed, Next etc.
as described by franzo.
Best regards and thanks for the advice.
I just ran into this on a fresh azure server 2022 node and after doing all of Franzo's stuff it still didn't work.
I decided to connect the IIS on the new node to the IIS on the old node just to see what it did... I hit "Connect to a Server...", put in the IP of the old node, and when it connected it told me the new node was missing some extensions. The web deploy was one of them and it installed it for me.
I have a web application implemented in ASP.NET MVC3 and SQL Server 2008 Express. It's relatively small so I can deploy it in local computer of my clients (Windows 7 or higher).
Currently, I deploy it manually by create new web site in IIS, copy published files to the folder of website, install SQL Server 2008R2 and use Management Studio to restore database with some initial data.
It's OK with me but not with my clients. They can't do the same things. What I want is an automatic installer, my clients just need to click a few buttons to get all done.
Specifically, this automatic installer must do the following things:
Install SQL Server 2008R2 Express and restore the initial database.
Install IIS7 (if it's not enabled in Windows 7).
Create a new app pool (V4) and a new Web Site use this pool. Then copy published files to the folder of the Web Site.
The installler can run aspnet_regiis command and grant permission for NETWORK SERVICE account to TEMP folder. This is required for web site to run.
The installer can copy some fonts to Font folder of Windows.
I see many app can do this automatic installer, but after googling I can't find a thorough solution to try.
Please give me some advice on this. Thanks in advance!
If you want a free solution, WiX is what you need, but it will take you some time to learn using it if you never created a package with it.
A more easy to use, and also powerful, but payed tool, is Advanced Installer, you need Professional edition, but you can try it for free with the 30 days trial mode. It has predefined prerequisite for SQL Server Express, built-in support to install IIS entities, and set file/folder permissions. Bassically all the requirements you need.
To enable any IIS feature you can simply add a PowerShell script.
As the question says, I have a problem running the web app on local IIS.
Here is my situation:
WIndows over Oracle VM VirtualBox running on Linux Ubuntu.
Bridged Adapter so that Windows box gets local IP from my router.
Visual Studio 2010 + sp
WCF REST Service application plugin for project template
The application runs when using visual studio development server (on localhost).
Target framework is v4.0
What I need is that the application runs on IP instead on localhost (so I can consume it on remote computer in LAN), so I configured IIS7.
Here is IIS configuration:
I created a website with target framework v.4.0
I binded the site to my local IP on port 80
Path to the site is /inetpub/wwwroot iisstart.htm as default document
IIS runs ok. If I open "http://my_local_ip" I get the welcome logo.
The problem is in visual studio.
When I go to project properties "Web" section and select local IIS over vsd server is where I get lost. If I set "Project URL" to "http://my_local_ip/some_name" visual studio complains that it cannot find IIS server and so it was unable to create the virtual directory. I tried manually adding virtual directory in IIS manager, but no effect. If I use "http://localhost/some_name" as the "Project URL" the virtual directory gets created, but it makes no sense does it?
Could some one please enlighten me?
If I use "http://localhost/some_name" as the "Project URL" the virtual directory gets created, but it makes no sense does it?
I think you are mixing two different things here. When you ask VS to use localhost as the IIS Server for your project, it will connect to the local IIS to perform configuration tasks. If you ask VS to use "my_local_ip" you are telling VS that you IIS Server is remote, and therefore VS will use remote administration to configure IIS (VS can't know that my_local_ip is the local computer).
But remote IIS admin isn't enabled on a default WinServer box. Furthermore, it would require some additionnal network config. You should therefore tell vs to use the local server.
In fact, IIS site bindings and VS deployment parameters are too completely different things. So, deploy your site on http://localhost/your_site.
However, I don't really like the prospect of using VS debugging deploy to deploy a real app. The directory will contain all your project files... You should:
create your site on IIS manager and setup a virtual directory.
Either
ask VS to publish the site to a directory (your virtual directory)
ask VS to publish a WebDeploy package, then ask IIS manager to import the package.
How to deploy my ASP.NET website to IIS7? I'm using Visual Studio 2005. And I don't know where to start.
I tend to take more of a manual approach, but there is a web publish feature built into Visual Studio that should get you going.
Here is some reading you can do on it:
http://www.codeproject.com/KB/aspnet/VSDeploy.aspx
Here's some preliminary steps, a little more manual than some other options, but they are the ones I'm comfortable with:
Obtain access to the server where IIS7 is installed. If you don't have IIS7 installed on a server, install it. If you are not able to get access to this server, you will need to have the administrator of that server set up IIS7.
Create the website in IIS that you want to deploy to, or have the server administrator create an empty website for you to run your website on.
Use the 'publish' feature in Visual Studio to build a deployable version of your site. This is what you will install on IIS7.
Copy paste the website over to the server where IIS7 is installed. You will need to place it in a directory which you can set as the Home Directory for the site.
If you have access to the server, and rights to administer IIS7, set the Home Directory of the site to point at the directory where you copied over your files.
Enable the website, and you should be good to go!
NOTES:
These instructions assume the following:
a) You have some basic knowledge of how to configure IIS7 (or at least access to somebody who does)
b) You have some basic knowledge of how to install IIS7 if it is not installed (or access to somebody who does)
c) You have some basic knowledge on web site publishing from Visual Studio
If you need more instructions on these 3 notes, you may wish to consult the references for IIS7 and Visual Studio.