I created a SharePoint Application Page. I chose Deploy as a Farm Solution and was able to make the application page work and get deployed on the local (development) SharePoint server. But apparently I cannot deploy (publish) a Farm Solution to a remote (users) server. My requirement is that I need to implement SharePoint Application Pages and deploy them to a remote server. But my problem is that if I choose Farm Solution, I can implement Application Pages but cannot publish to a remote server. But when I choose Sandbox solution I don't have the option to create application pages, the template says Application Page (Farm Solution only). What am I missing here? Why is the type of page related to the deployment target?
I am using Visual Studio 2012 and SharePoint 2013.
You likely need to package it up and deploy from the remote server using powershell: http://patrickboom.wordpress.com/2010/05/31/using-powershell-to-deploy-sharepoint-solutions-wsp-2/
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
I have just completed an Umbraco intranet using WebMatrix. Now I want to publish it to our server so that everybody can see and use it. WebMatrix can only do Web Deploy or FTP, so I opened the project in Visual Studio 2013 to publish it there. I was able to publish it to my desktop, where I have attempted to get it running here before uploading to the server. So in IIS I 'Add a Website' and set up the project, using port 101. I tried it both on my desktop and then moved it to wwwroot and in both cases IE says 'This page can't be displayed'. I am using the CE database with Umbraco 7.2.4.
Help please. I've been at this for days now.... I've tried the umbraco forum and google and got nowhere. :(
Tony
If you have remote desktop access to your web server, you don't actually need to rely on web publishing. You can just build the website in release mode, and then copy all the folders from the web project onto the webserver.
On the web server you can manually set up an IIS website and set up host names etc. You shouldn't need to deploy it using visual studio, this way is much safer
In IIS, you should set up a new website, using port 80 on your HTTP binding.
From the sounds of the error, IIS is not looking at the right physical path.
You should use the Microsoft guide on How to set up your first IIS Web Site as a starting point.
I'm trying to publish a LightSwitch app (web client) to a local computer and local network location.
Unfortunately all the videos I've encountered on-line only show how to deploy the desktop app but not web..
My LightSwitch app is connected to MS SQL server and SQL Server is installed on the same network but not on the local machine.
Here is how far I can get in the LightSwitch publishing wizard:
Are there any good videos regarding how to deploy web LightSwitch apps locally with visual Studio 2013?
Or a condense example?
(1) The missing link is IIS! Go to Control Panel -> Programs and Features -> Turn Windows Features on or off-> find 'Internet Information Services' (IIS) and install it. (There are many options, if unsure install everything except FTP Server)
I'd recommend watching a few tutorials about IIS to get you started.
(2) Next step is to download and install Web Deploy v3.5. (Make sure you choose custom install and select ALL options.)
(3a) In Programs and Features you'll need to make sure the 'Management Service' is installed.
(3b) You will need to make sure the 'Web Management Service' service is started and set to start automatically.
(4) Configure IIS for Web Deploy. (From memory: locate your Default Website in IIS, right click and you'll find a deployment wizard. Run it to create a deployment settings xml file. You can import this into the LightSwitch Publish Application Wizard.)
Side note: The User Name field (You've got 'sa') is not the database account, but a system account.
Good luck.
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 do I make the webserver within Visual Studio serve content that’s viewable by other machines on the network?
For example: When I press F5 and I give the other person the ip + port he/she can see the content.
Thanks!
You can setup Visual studio in order to use IIS to debug. Its in the properties.
If you do that then people can visit your debug.
http://learn.iis.net/page.aspx/387/using-visual-studio-2008-with-iis-7/
Sounds like it's not possible.
From MS Site:
If you cannot or do not want to use IIS as your Web server, you can still test your ASP.NET pages by using the ASP.NET Development Server. The ASP.NET Development Server, which is included with Visual Web Developer, is a Web server that runs locally on Windows operating systems, including Windows XP Home Edition. It is specifically built to serve, or run, ASP.NET Web pages under the local host scenario (browsing from the same computer as the Web server). In other words, the ASP.NET Development Server will serve pages to browser requests on the local computer. It will not serve pages to another computer. Additionally, it will not serve files that are outside of the application scope. The ASP.NET Development Server provides an efficient way to test pages locally before you publish the pages to a production server running IIS.
You could installl IIS or IIS express and publish to them, otherwise as Franky says its not possible with Cassini (the VS inbuilt one)