I have a visual studio solution and when I opened it I got an error saying:
"http://localhost:55365 : error : Unable to open the Web site
'http://localhost/_1'. To access local IIS Web sites, you must install
the following IIS components:
In addition, you must run Visual Studio in the context of an
administrator account.
For more information, press F1."
What is strange is that nothing is listed to install. NOTE : I have run visual studio as administrator. This is a screenshot of the solution in the explorer...
Really I have 2 questions:
1) What is the project type of the second project in the solution explorer?
2) Why wont it load? I do have IIS installed and I have other sites that run under the web development server....
Web Application or Web Site.
Project was pointing to a local IIS web site but this doesn't exist anymore.
About 2), maybe you erased by error your web site code and its physical folder, or the IIS web site.
Related
When I am trying to create a new project in dotnetnuke 9 with for Theme develop using VS, I am getting the following error:
"The Web Application Project is configured to Use IIs. The webserver could Not be found "
I am using VS 2019 and SQL 2017. I create a website in IIS with port 80 that works correctly at localhost. Folder wwwroot/dnndev.me has Network Service permission full access, hostname is dnndev.me without www, there is no .csproj file because the project has not created it yet.
Any suggestions are welcome.
Please check if you have some virtual directories and/or applications in your web site. Visual Studio creates these very often when you open a project. It's safe to remove them - also after opening the project.
I'm new to web-servers. I have Internet Information Services (IIS) 10 Express installed on Windows 10. I'm trying to develop an Office add-in so as to host it in the same computer I use. The problem is how do I host the add-in in a local web server? Since I'm new would appreciate a little of step by step answer.
while you are developing the add-in, you do not need to worry about a local web server. The Visual Studio tools take care of all that for you (it will run in a web server provided by Visual Studio).
If you are using Visual Studio 2015 (the community edition is free and works fine with Office add-ins), you simply create a new 'office add-in' project and it will all be set up for you. It will create a 'web project' for you and it will use that web project when you run the application locally - you do not need to do anything to make that happen.
You may find that you have to install the Office tools for Visual Studio but if you go to File > New > Project > Visual C# > Office/SharePoint you'll get a link to download the tools if you do not already have them.
In terms of hosting it in the public domain, I like to use the Azure Web App service as you can very easily publish directly from Visual Studio or you can setup continuous integration with GitHub, VSO etc. Once you have it hosted in the public domain, you simply change the 'Source Location' in your office add-in manifest file to point at your public URL.
Well I figured it out.
Except it broke my VS Setup now (Resolved)--> See here Installing IIS broke Visual Studio Office Add In Project Localhost
To enable IIS I had to open "Programs and Features" and select "Internet Information Systems".
Then start --> IIS. Browse to default site and added binding for SSL/Port 44367 (Same as VS). I already had a SSL cert from previous configurations, selecting the Dev Cert worked fine.
I copied everything from \ExcelWebAddIn1\ExcelWebAddIn1Web\* to the webroot C:\inetpub\wwwroot and adjusted the following in manifest.
replace:
~remoteAppUrl
with
https://localhost:44367
I then sideloaded the manifest and it worked as expected.
Note that Martin Kearn's answer still applies, this isn't needed if you want to just use VS and it has better debugging, but I wanted to test and learn.
This was all to test/debug deployment, and I was able to do the same by just changing the localhost url to a simple nginx webserver w/ the contents of the above webroot.
I downloaded and installed the RTM of VS 2015, got my Web API project working nicely, can hit F5 all works in IIS Express, lovely. But now I go to deploy my WebAPI on a local network server and oh my! I was hoping to find the publish to File System option and then to be allowed to select IIS but it ain't there. Publish to file system is there but that compiles wwwroot and approot folders and for the life of me I haven't been able to get them's files to run under IIS - tried all sorts, ege approot as my website root on IIS, wwwroot as my website root. I've found plenty of reference to show you how to deploy Web API ASP 5 to Azure but have as yet been unable to locate any information for how to deploy to IIS on network.
Just got it to work, for the sour down voter here's how
Right click WebAPi project select Publish
Profile -> Select File System
Connection Target Location browse to somewhere that makes sense eg. C:\inetpub\WebAPI
Settings ->Configuration select Release
Settings Target DNX Version select x64 example dnx-clr-win-x64.1.0.0.beta4
In IIS set the Physical Path of your website to be C:\Inetpub\WebAPI\wwwroot
Test eg localhost/api/Values
Whenever I try to connect with the url (Sharepoint customization wizard, with option deploy as a farm solution) of the solution after creating a new sharepoint 2010 solution with the VS 2010 ultimate and I can't connect it, but I can access it in the browser.
I am running visual studio as administrator.
It gives me the error:
"Cannot connect to the Sharepoint site: [site name].org.br.
Make sure that the Site URL is valid, that the SharePoint site is running on the local computer, and that the current user as the necessary permissions to access the site.
Additional Information:
It is working without need to making package, automattically, (just pressing F5) on the localhost, but is not working in the network intranet solution.
Cannot connect to the Sharepoint site: [site name].org.br.
Make sure that this is a valid URL and the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project."
Maybe it is required to use the Visual Studio Team Foundation Server to be able to make it to work.
EDIT: Was an error with the anti-virus at the network.
Now I can connect to the project, but cant deploy.
Now I have a problem when deploying it, it gives me a new error.
Recycle the IIS application pool:
Error occurred in deployment step 'Recycle IIS Application Pool': Cannot connect to the SharePoint site: http://[website]. Make sure that this is a valid URL and the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project.
I am using Visual Studio 2010 and I would like change debugging environment from the localhost to my full computer name/domain. Does anyone have some step by step instructions on how to do this? (I would also like to set it up as the default for all new projects plus how to change it in existing projects). I am new to using visual studio and programming in general.
I found this post Visual Studio 2010 - Change localhost to custom domain in the forum but it wasn't clear to me on how to make the change. I went to the project properties web tab and attempted to set up local IIS Web server but got the following error:
"ASP.NET 4.0 has not been registered on the Web server. You need to manually configure your Web server for ASP.NET 4.0 in order for your site to run correctly."
I am not ever sure if that was the correct way of going about doing this. I just need my debug url address to go from:
"http://localhost:53674/Projectname.aspx"
to:
"http://computername.pag-domain.webname.org/Projectname.aspx"
Thanks!
For fixing the iis web server, I am not really sure what was done...our IT department worked on that. For setting up the local IIS webserver in visual studio I did the following: In the web project properties, under the web tab, I choose "Use Local IIS Web server, in the project URL, I put the full computer domain and told it to create a virtual directory.
Got it. Our IT came to the rescue — he fixed some issues with the ASP.NET not accessing 4.0 correctly. Then I set up the "Use Local IIS Web server" correctly and it worked like a charm.