IIS 5.1 shipped with windows xp has 10 connection limit. Singll ASP .NET MVC application can use more connections even if HTTP 1.1 is disabled.
To fix this, Microsoft recommends to use IIS 7 Express in XP.
I tried
iisexpress /path:c:\myapp /port:80 /clr:v2.0
and it works in local computer.
This XP computer has number of users. User can log off antytime.
How to run iisexpress automatically if computer is turned on ? I googled but havent found a way like to run it as XP service ?
How to run IIS Express as a process started via a Windows Service describes how to run it from application. However I'm looking a way to use Windows XP as http server without application. Maybe srvany can help ?
Related
Is it possible to run MatrikonOPC Simulation Server on Windows 8.1.
I am trying using this tutorial (http://home.hit.no/~hansha/documents/software/documents/MatrikonOPC%20Server%20for%20Simulation%20User%20Manual.pdf) to run it and so far there is no success at all.
We have a need in our project to automate the process of creating AppPools and Websites in IIS . We would like to write some batch script to get this done. From my research I found that PowerShell has commands that can be used. However when I tried to run IIS module commands in PowerShell on Windows Server 2012 , it does not recognize the commands. Is it correct that this feature was only available for Windows 7 / IIS 7 ? Is it also available now on Windows 2012 R2 / IIS 8. If so where can I find proper documentation and help ?
This feature is of course available in Windows 8/8.1 and Windows Server 2012/2012 R2.
You probably forgot to run Add-PSSnapin WebAdministration before executing other IIS cmdlets.
You can find the full documentation on the Microsoft Technet.
If you run Windows 8.1 or Windows Server 2012 R2 (i.e. you have Windows PowerShell 4.0) you can also use the new PowerShell Desired State Configuration feature with the xWebAdministration Module to create WebAppPools and Websites.
I have upgraded my pc Windows 8.0 to Windows 8.1, I am using Microsoft SQL Server R2, and this was working fine with my windows authentication/ SQL authentication when I am using Windows 8.0, but after upgrading my PC windows 8.0 to 8.1 the SQL server was not able to connect using windows authentication or SQL authentication. This problem occurring in only with my credentials, but It is able connect when use other credentials to connect to other database.
Please help me some one regarding this problem.!
I have figured out a work around for this issue.
First create a local account that will work with your sql server. Then switch to your Windows Live account (a seperate user) and modify the shortcut's target.
C:\Windows\System32\runas.exe /user:domainName\localAccountName /savecred “pathToExecutable”
This should work for any program that needs to use Windows Authentication.
Trying to develop and test an ASP.NET MVC 2 as well as a hosted WCF app where the client is limited to IIS 6.0 (OS Windows 2003). I am developing and testing in Windows 7 which has IIS 7. I do not have access to a Windows 2003 disk, so creating a VM doesn't appear to be a viable option for me...
Any suggestions or tips would be greatly appreciated
Update:
Lucas' response led me to consider a virtual dedicated server... Going to try that for a testing environment.
You don't have many options
You bend (get a MSDN subscription or Win 2k3)
Your client bends (upgrades to Win7/2k8)
Find someone you know who can let you use an IIS 6 machine.
Get your client to let you use one of their machines during development
You can virtual PC it. If you can use Windows XP, M$ provides a virtual machine + WinXP trial. It's more for using IE6 I think, but I don't think it limits application installation like IIS.
I don't have the link anymore, but it's provided by M$ from their download area
I am running tests successfully on Windows XP but not even got a single successful build while running through Windows 2003.
Any one knows whether it is compatible or not as I read on some site that WatiN is fully tested on XP and not on other Windows editions.
I'd ordinarily post this as a comment on Sam's answer, but I'm trying to make a stack trace searchable, so here goes...
WatiN.Core.Exceptions.IENotFoundException : Could not find an IE window matching constraint: Timeout while waiting to attach to newly created instance of IE.. Search expired after '30' seconds.
at WatiN.Core.IE.CreateIEPartiallyInitializedInNewProcess()
at WatiN.Core.IE.CreateNewIEAndGoToUri(Uri uri, IDialogHandler logonDialogHandler, Boolean createInNewProcess)
at WatiN.Core.IE..ctor(String url, Boolean createInNewProcess)
c:\...\WithVendorSite.cs(42,0): at WithVendorSite.VerifyCanLogIn(TargetSite target)
I developed my test on Windows 7 against WatiN 2.0.10.928 but the test was continually getting stuck with a blank browser with about:blank in the address bar when run on Windows Server 2008 with latest WUs, and Enhanced Security Configuration turned off and running the tests elevated (Run as Administrator).
The problem in my case (thanks Sam) was the absence of Microsoft.mshtml.dll in the bin directory (I had figured out Interop.shdocvw.dll was necessary from error messages I'd encountered on the Windows 7 side).
After adding Microsoft.mshtml.dll, things run happily with ESC turned back [but the test process needs to run elevated].
I run our WatiN integration test suite (hundreds of tests) on Windows 2003 with IE6. Works fine, no special tricks done. What is the exception you are getting? Are you sure mshtml.dll (the COM dll somewhere in the windows directory) is registered correctly on this machine? Do you have the Microsoft.mshtml.dll (interop assembly) and interop.shdocvw.dll in the same directory as WatiN.Core.dll?
Update: Its officially supported, from the faq
Which windows versions are supported?
Windows 2000, Windows XP, Windows 2003
and Windows 2008.
Original post:
I use it on vista all the time. I haven't used it on windows server 2003 though.
Have you tried logging on interactively into the server and trying to run the tests manually? It may be because of the account that your build server is running under or some particular security settings you have setup. Have you checked to see if IE is stopping you from viewing the page due to it not being in the trusted sites list?
I was using Watin 1.3 on Windows XP but the same on Win 7 having problem....
Officially Watin 1.3 works on O.S. Xp and earlier on Win XP
But Watin 2.1 works fine on Win 7 and XP.
Officially Watin 2.1 supports any Microsoft O.S.