Just getting started on a project to migrate from win 2003 iis6 to win 2008 / IIS7, and after reading the MS documentation and also various articles I am a little confused, as it states a site needs to have one or more applications.
However I have setup a new site pointed at my .Net 3.5 directory and it works.
This means that ....
A- I am seeing things.
B- A site does not actually need one or more applications.
Can anyone explain the above behaviour? and or point me to any useful articles that explain site, applications etc... to me.
The app pool is in classic pipeline mode, not sure if this is a problem.
Many thanks,
Your guess in a comment is correct - a web site itself also acts as an application and does not require an explicit application subfolder.
Here's some links that helped me with understanding IIS 7.0
Configuration reference
Operation Guide
Related
I've created a small application for internal use with asp.net web forms. I don't have a server to deploy it, but would like others in the office to have intranet access. Just a handful of people will have access (2-6). It is not a public-facing application.
I saw the following instructions on this site to deploy an asp.net mvc application to a desktop computer-using IIS 7.
1.Install IIS from the standard windows components.
2.Put your code in the root directory of the default created web site.
3.Be sure the firewall is allowed the 80th port.
Would the procedure be the same for my asp.net web forms application--or is there something inherently different (between web forms and mvc) that makes this impossible?
Thank you for your help!
The instructions would stay more or less the same. The process can be a little more complicated than what you've described in the steps above, but it's a good starting point.
In addition to making sure port 80 is open, you'll probably need to assign an IP address for the site too. See the illustration below:
It should work exactly the same.
One thing you'll need to check is that the ASP.NET framework version the default web site created by IIS7 is using is the same as the version your code was created in. To do this; goto IIS -> Application Pools -> DefaultAppPool then check the .Net Framework version.
Bar that; as long as the physical path of the Site inside IIS is pointing to the correct folder it will work the same as MVC would
I have a question regarding IIS (version 7.5) and ASP.NET (.NET Framework 4) . I am trying to debug ASP.NET web application which is stored on IIS. Now, I have done this in past and everytime it worked perfectly.
But now when I try to do same, **Visual Studio 2010** always gives me error, **"unable to start debugging on the web server. the iis worker process for the launched URL is not currently running" ...** even the application I had created in past (& stored in IIS) can't debug using Visual Studio. But all applications (new & old) can be accessed if I type their path in Browser, and they work fine too.
I did search on internet about my problem and I found many posts, but almost every post talks about activating **Windows Authentication** in IIS for the application in question. But, I am using Windows 7 home premium and the IIS shipped with this version doesn't support option for Windows Authentication. Also, if this is the only reason then why my old applications were working just fine till now without this Authentication method?? I found MSDN help about this error but it is not much helpful to me. I also checked APPLICATION POOL selection in IIS and my Application (both are using V.4.XX.XXX)... I have also checked **BINDING** , which is *:80 to Default Website, that means all requests to port 80 will be directed to default website (where my all applications reside)
As a side note, I have SharePoint Server 2010 installed. Which has its own website (which I have disabled while debugging) ...
I think there is something is changed in my IIS configuration, but I cant figure out what it is. And I am sure that it has something to do with SharePoint installation (may be because of more than one website on IIS for same port ??). Because I am using IIS for first time after installing SharePoint and I am having this error.
I will really appreciate if any one has answer ...
Thanks,
Jack
UPDATE: As I suspected ... having more than one site in IIS was root cause of trouble, Once I uninstalled Sharepoint Server 2010 and its web sites from IIS, my Visual Studio 2010 debugger was able to "Auto-Attach" w3wp.exe process while debugging any application ... ( I really don't see any reason that even after disabling all other websites why still it was giving me error at first place ?? )
I know its not a solution, because I have to remove Sharepoint Server ... but at present its more important for me to work on that application then Sharepoint Server.
But I am still open for any suggestions which might help me to run both together ....
Thanks,
Jack
Check the Bug fix for this issue in the Microsoft's Connect site.
.
Is it with .NET 3.5 in Visual Studio 2010 , if yes , then check http://www.ginktage.com/2010/08/fix-for-visual-studio-2010-hangs-when-debugging-asp-net-3-5-web-application/ for information
We have an ASP.NET application running on a webfarm. When we release a new version and copy it to the production servers, occasionally it happens that after a few hours the application reverts to a an earlier code base.
Have anyone else experienced something like this? Would sharing an application pool between two applications running different versions of the code make this happen?
Additional information:
3 x web servers running w2k3/iis6
ASP.NET 3.5
I've had this happen rarely on non-precompiled sites and the solution was to stop IIS and clear out the temporary cache at:
%WINDIR%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files
Is not a long-term solution, but will address the immediate problem. If not already, it is worth considering deploying the site pre-compiled.
I am thinking of getting a $20/month VPS Ubuntu box with Slicehost.com or linode.com and running asp.net MVC on mono. Has anyone done this? I have successfully configured asp.net MVC with Apache on my local ubuntu box but I just am not sure how stable this would be? I really like the idea of root access VPS plus being able to run asp.net mvc for $20/mo would be sweet
Jackson Harper runs his site on a similar system running on Linode.
You might want to check his blog, slides and his pre-configured appliance that runs ASP.NET MVC here:
http://blog.monoontheweb.info/
Miguel is right I did run that setup for quite some time. Unfortunately that blog is down now because I am using that node for testing another project. You might be interested in this project as it as meant to make deployment of the very setup you are talking about much easier.
More info on the project here: http://jacksonito.blogspot.com/2010/01/setting-up-mono-powered-aspnet-web.html
As per my results running my Mono web server on Linode. I have had used that setup for two different sites and had excellent uptime and performance on both of them. None of them were extremely popular sites but they got a couple large spikes in traffic.
I wish to migrate a website to windows 2008 platform, is there any obvious pitfalls i should be aware of?
code base is c# 3.5,asp.net with ms ajax.
I googled a bit and found this link:
http://weblogs.asp.net/steveschofield/archive/2008/09/04/iis6-to-iis7-migration-tips-tricks.aspx
Biggest Issue i find is that 3rd party components needs to have 64bit version ready to get most of benefits.
I haven't had any experience with a migrated application not working properly. I've only done a few, but we've tested a number here at work, and they all run great under IIS7.
The only gotcha is that the .NET "Managed Pipeline Mode" is set to "Integrated" by default, which caused problems in some of our applications. Either setting it to "Classic" on your app pool, or switching your application to use the "Classic .NET" app pool should resolve the problem. For some more information about the new pipeine, read about it here.
Oh - and +1 on the wacked-out interface. I want my old IIS6 interface back!
Don't let the wacked user interface put you off (but it will drive you dilly)