Is there anyway configure IIS Express 7.5 to utilize JRun 4 for jsp pages?
We are currently trying to get through rewriting our remaining Java Server Pages to ASP.NET but until this is completed, is the fact that we still have some, gonna force us to continue using the full version of IIS during development?
I'm new to IIS Express and for that fact, I'm also new to the configuration method of IIS 7.x all together, we're still on 6. Thanks in advance for any help or guidance.
Related
I am trying to install Sitecore 8. I got an error saying "SQL Server Version Not supported - SQLServer (10.50.1600.1)" I tried to find installation document to know database requirements. I could not find anywhere, may be i am looking in wrong place.
doc.sitecore.net
kb.sitecore.net
Could some one point me out in right direction.
Found it finally,
For someone like me searching the whole internet here is the link
Sitecore 8 installation Guide
Checkout How To Install and Configure Sitecore for the complete guide on installing latest version of sitecore.
Sitecore 8.1 has a specific requirement for the operating system, IIS web server, .Net framework and the database server. Follow the detail sitecore guide for installing the sitecore properly.
IIS Requirements for Sitecore 8.1
IIS 8.5
IIS 8.0
IIS 7.5
IIS 7.0
.NET Framework and Database Requirements for Sitecore
To install Sitecore 8.1 you would need minimum version of .net framework 4.5 and above. Sitecore requires miminum MS Sql server 2008 R2 SP1 or above editions like SQL server 2012, SQL server 2014 and MongoDB Database 2.6x
The site appears to be in beta, so the accepted answer is no longer working.
It appears that the best recommendation, as of now, is to view the general Sitecore 8 downloads page, find the version you want documentation for, and then scroll down that version's page to find the documentation.
Given how hard it is to find the Sitecore 8 page (I had to search their new beta community forums), I much prefer the old SDN site.
We are trying to make a cut over from IIS 6.0 to IIS 8.0 Integrated pool on Windows Server 2012 Standard edition for an application built on ASP.Net Version 4.0. Our web application requests go into a RequestAcquireState ( ASP.Net Session gets locked for concurrent requests working with the same sessionid ) , in IIS 8.0 Integrated pool on the above Windows Server . However this behavior does not show up when we run the same app in Classic mode on IIS 8.0 .
Session is stored InProc.
We can rectify this situation on a Windows Server 2012 Data Center by modifying SessionStateLockedItemPollInterval in registry. However that solution does not work in Windows Server 2012 Standard edition.
This has left us perplexed -
why does an ASP.Net Run time Session issue surface in IIS 8.0 Integrated Pool for an application we have run successfully on previous versions of IIS and classic mode in IIS 8.0 ?
How do we rectify this problem now on Windows Server 2012 Standard edition ?
Thanks, will appreciate if some body can help
IIS 8 comes with .net framwork 4.5 so you may be running into missing the fix http://support.microsoft.com/kb/2828842
Issue 6
Symptoms
When you send many concurrent requests that have the same SessionId to an ASP.NET 4.5 web application, some requests may freeze at the RequestAcquireState stage unexpectedly.
Resolution
After you apply the hotfix, the hotfix makes sure that the EndRequest event will always trigger.
try installing this fix and see if that addressed the issue
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...).
I am learning asp.net MVC 3 by my own since 6 months and i am enjoying it; i have downloaded MS visual web developer 2010 express for free which comes also with free database . i have the following 2 questions
1. but my question is if i can build a web site that runs on a production server using these free softwares offered by Microsoft
2. and can i also deploy the production web site using IIS 7 express which is also free ?
BR
You will be able to deploy the web site you have developed using the free tools to any production web server running IIS.
However, IIS Express is not intended for production use, but rather for development. Refer to Scott Gu's post on IIS Express
You might be interested in free asp.net hosting. Look at aspspider.net
If you need more robust and professional hosting for your site, go with a paid hosting service. I use discountasp.net/ a lot, but there are plenty of others.
When I run my asp.net mvc site in visual studio 2008 is it running iis7 or iis6 Internally?
Also does mvc require iis7 (is intended for?)
Via Visual Studio, you're not really running IIS6 or IIS7. You're running Cassini. You can find out how Cassini differs from IIS here. As for ASP.NET MVC, it may be deployed to run under IIS6 or IIS7. As mentioned previously, you have to jump through some hoops if you want to run under IIS6 so IIS7 is ideal if possible. If you are stuck with IIS6 (maybe you're on Windows Server 2003) there are a couple of best practices (Url file extensions or wild card application maps) which Phil Haack has well documented which will help to get your application running correctly.
If you mean the one built in to windows, that is tied to your OS version rather than to your version of Visual Studio.
If you mean the version that Visual Studio uses as a development webserver, then that version is not IIS. Its an internal webserver (very similar to Cassini) suited for testing and debugging only.
MVC can work in IIS6 but you need to make sure to set your routing to "{controller}.aspx/{action}/{id}".
As for IIS6 or 7 for the "IISLite" that VS uses, I am unsure of that. I think VS2008 uses IIS7 because I do not need to add ".aspx" to my controller in the route when debugging.