Hope somebody can give me some info regarding this.
I have a silverlight web app (.NET 4). I would like to use msdeploy to deploy it to IIS 7 running on a Windows 7 64 bit machine.
I have read many pages and have tried a lot of the steps in them so far but am still struggling.
What I have done:
1. Installed Web Platform Installer.
2. Installed msdeploy
3. Started and set to automatically start: "Web Deployment Agent Service" and "Web Management Service"
4. Created a web site in IIS 7 and set permissions.
5. Tested the website "http://server/page and get a blank directory browsing because nothing is added yet.
So now I would like to deploy but am getting an error : "No connection could be made because the target machine actively refused it:10.224.201.117:8172
I have tested telnet'ing to the address on port 8172 which fails.
It is suggested that msdeploy is not configured correctly and I need to Enable Remote Connections. However it does not seem that Windows 7 IIS 7 has the icons in IIS to do this. (No "Management Service" option under add / remove features of IIS)
Does this mean i can not deploy to Windows 7 IIS 7?
Or is there another way to enable remote connections, perhaps using powershell?
Any help is greatly appreciated
Tx
Neill
Related
I have turned on IIS on Windows feature but I am unable to open IIS in my personal laptop. Can you please help to solve the issue?
But if I try to open inetmgr, it shows the below error.
One thing I observed that IIS is not there in in Windows Administrative Tool(screenshot below) so tried to install IIS from https://www.microsoft.com/en-us/download/details.aspx?id=48264 but its is showing that latest version is already present in your computer.
Can you please help?
To enable IIS and the required IIS components on Windows 10, do the following:
1)Open Control Panel and click Programs and Features > Turn Windows features on or off.
2)Enable Internet Information Services.
3)Expand the Internet Information Services feature and verify that the web server components listed in the next section are enabled.
4)Click OK.
Required IIS components:
-Web Management Tools
IIS 6 Management Compatibility
IIS Metabase and IIS 6 configuration compatibility
IIS Management Console
IIS Management Scripts and Tools
IIS Management Service
-World Wide Web Services
Application Development Features
.NET Extensibility 4.5
ASP.NET 4.5
ISAPI Extensions
ISAPI Filters
WebSocket Protocol
Common HTTP Features
Default Document
Static Content
Security
Basic Authentication
Request Filtering
Windows Authentication
To ensure that IIS is installed and working, type IIS in the Search bar near the Start button. You’ll see the Internet Information Services Manager as a result. Click on that to open it.
I have a ASP.NET application and I would like to deploy it on a webserver.
So I searched for a some tutorials and most of them tell to enable the IIS Management Console in control panel.But I don't have such an entry in there.
So I guessed that I have some component missing(jigsaw) and used the MS WebPI utility to install IIS components and other things even remotely connected to web development.
I have installed
Web deploy 3.0
IIS Express 7.5
.NET framework 4
and MS web tools for Visual studio 2010.
Still no luck.Run>inetmgr still fails.There is no inetpub folder anywhere.(I expected something like apache htdocs folder)
Excuse me for the newbie question.I am in windows7 home basic.
You are NOT able to use full-fledged IIS with Windows 7 Home Basic.
According to MSDN IIS7 installed on Windows 7 Home Basic is too limited and you won't be able to run ASP.Net application there. IIS Management Console is also unavailable on Windows 7 Home Basic.
I think that you can try IIS Express and all-in-one WebMatrix solution. WebMatrix provides you with a neat interface to start /stop / restart IIS Express and to edit some of IIS Express settings.
What I am looking for and seem unable to find, it's late and I'm tired, is a step by step guide on how to set up windows 2008 server to run asp.net mvc applications.
I am a web applications developer, amongst other things, and can do that bit fine. Normally I let someone else, like the hosting company, worry about the setup and just publish using 1-Click with web deploy or ftp.
However, for this projects I have a local Windows Web Server 2008 R2 installed but I don't know how to set it up to run the application. the deploy works, all the files arrive in the correct folder on the server, but can I get it to work?
No.
Hence the question.
For your information the app is built using Sharp Architecture, MVC3 and Razor and targeted at .NET 4 which is installed on both my development PC and the server.
Any suggestions?
Thanks.
Best thing would be to download Windows Web Platform installer and select the options you want, for example, .NET 4, MVC3 etc etc ...
Then, remember to enable ASP.NET in your IIS (under Roles or something...).
Is there some kind of deployment wizard I can run and have it install just the things it needs to run right onto the server end point? Do I have to build the project using VS2010 on the server? If I can't get this thing deployed today I am really going to be screwed.
IIS 6 is there and I think .NET 4 is installed (I tried installing it from Microsoft and they had me install a million things like VS2010 express and SQL Server and all this other crap, the install failed but .NET 4 does show up in IIS).
I achieved this by enabling an FTP site for the IIS server website and using this to deploy the web application within visual studio 2010 which will build and deploy just the changed files for each build. Works very well. You can even add a Publish toolbar to help deploy regularly more easily.
All you have to do is install the .NET Framework 4.0 (32 / 64 depending on build) and run aspnet_regiis.exe in the Framework folder.
For me this is located here:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe
Hope this helps!
You can also use the publish command from VS 2010 to save it to the filesystem and then copy the files into an IIS site on the target server. Just map a network drive to X: or something (for your sites root) and publish directly to the share.
You can take a look at Web Deployment projects or even the VS "Publish" feature
From the Build menu in VS2010, just click Publish [name of your web project] and enter the location on your web server where the site is going to be hosted.
VS2010 will publish the files required there.
It shouldn't be necessary to install VS2010 Express, just to deploy a site. But if .Net 4 and ASP.NET MVC 3 is installed, you should be able to deploy. Right click the web app in VS2010, and hit Publish.
Remember to set the configuration to Release!
But, with IIS 6 you could be in for a fight in regard to HTTP Modules, Handlers and other server configuration. Anything inside your Web.config's system.webServer section will always be ignored by IIS 6.
I'm debugging a vb.net windows program which I've upgraded to a VS 2010 solution, targeting Framework 2. I need to step into a webservice's code. The web service is framework 3.5, also vb.net, running on a windows 2003 server on our LAN. I've seen a ton of crap on the Net about it, mostly other people who couldn't get it working either.
The error I get in VS2010 is the exact same one I got before upgrading the project from VS 2005:
Unable to automatically step into the server. Connecting to the server
machine [servername] failed. The Microsoft Visual Studio
Remote Debugging Monitor (MSVSMON.EXE) does not appear to be
running on the remote computer. Please see Help for assistance.
So I did what Help said to do and ran the VS 2008 remote debugging wizard on the host server. I have verified that the remote debugger is running as a service on that machine. And it still fails.
Little help? THANKS
Just in case anyone comes here looking for this answer, here it is. No goofy 'Attach to Process', no weird bad instructions
from websites going off on a million stupid tangents. This answer has been FALKENIZED.
When on the same LAN and on the same domain, remote debugging from Visual Studio 2010 works when you do the following steps.
on web service host machine, share the web application folder where the web service lives; give yourself 755 permissions.
oops, give yourself wrxr permissions.
on local development machine, map a network drive to the [web service host machine][web app] folder you just shared.
copy the Visual Studio 2010 remote debugger folder (containing msvsmon.exe + support files) to web service host machine.
Make sure you get the correct platform for your host server, e.g. x86, x64, etc. Remote debugger is found here:
C:\Program Files\Visual Studio 2010\Common7\IDE\Remote Debugger[platform]
on web service host machine, drag a shortcut from the newly-copied debugger to the desktop, then start the remote debugger
on local development machine, step thru code. when reaching a call to the web service, you'll be prompted to navigate
to the location of requested web service code file, which will then be available in your mapped path. Do it.
Finally after 1000000 headaches, you may start debugging your web service. CONGRATULATIONS