Browser testing on Windows 8? - testing

I have a Mac and I am deciding whether to install Windows 7 or 8 on Boot Camp.
Is it possible to test websites inside actual windows of IE6+ and older Firefox/Chrome/Opera browsers with Windows 8?

I tried bootcamping a Core 2 Duo iMac a year or so ago with Windows 8 and it would cause regular crashes. It looks like there is an updated to Bootcamp (I was running the previous version 4) which supports Windows 8 so you could use either option.
If you use Windows 7 (like I did), you can install and run Windows Virtual PC with different versions of Windows and IE. The cool thing is Virtual PC has something called Integration Features which allows you to launch specific applications (like IE) from the virtual machines without being in the virtual machines. (Think virtual applications)
I do this. I have one Virtual PC with XP and IE6. I cloned it, upgraded it to IE7 and then did the same thing with IE8. Now I've got a Windows 7 machine with IE9 and virtual browsers of IE8, 7, and 6. I also run older versions of Firefox on those cloned XP machines.
If you use Windows 8 you can do the same thing, its just a little different procedure (see my comment below) because Windows 8 uses Hyper-V instead of Virtual PC. I prefer Virtual PC because of the Integration Features, with Windows 8 you'll have to use the Hyper-V console but you can do the same thing.

You'll need a virtual machine within Windows 8 to run anything earlier than IE10, since Windows 8 only started with IE10.
There are some hacks to make pages behave a bit "like" IE6 (or other browsers), but I doubt they are going to work well now you're reaching all the way back from IE10.
Firefox/Chrome/Opera will work OK, as they aren't integrated into the OS.

There are a couple of options that might work for you better than installing Windows 7 or 8 on bootcamp:
Use a service such as BrowserStack. This costs money, but Microsoft provides 3 free months via Modern.ie
Install virtual machines on your Mac. Microsoft makes these available for free, also via Modern.ie

Related

Ideas on how to get around Windows 11 ARM not supporting IIS

My new Macbook Pro running on an M1 Max (ARM) chip just came in. I installed Parallels and Windows 11 Preview for ARM, and Visual Studio installs / launches / builds my solution beautifully. Unfortunately the turn windows features on or off dialog doesn't have the option for installing IIS, and others have posted that this is not supported in Windows 11 for ARM.
Our dev team runs multiple ASP.NET Core 3.1 websites locally under IIS using subdomains, e.g.: https://auth-dev.mydomain.com, https://web-dev.mydomain.com, https://webapi-dev.mydomain.com. This was easy to set up in IIS using the bindings dialog, I could specify for port 443 (https) to use a certain subdomain and our dev SSL certificate.
Now I need to figure out how to make this work on Windows 11 ARM. Developing on an inferior non-Macbook Pro laptop doesn't seem like a great solution for .NET devs, I have to assume others with M1 chip Macbook Pros have run into this same issue. What are my options?
I first started looking into using IIS Express, but it seems like every website has to run on a different port, whereas I need them all to run on port 80 (just with different subdomains.) I'd be fine with them running on different ports if there was a way to forward those various ports to the subdomains, but it doesn't seem like the windows HOSTS file supports that.
I also looked into using the Apache web server for Windows, but I read somewhere that it doesn't support running ASP.NET Core apps.
OS build 22563.1 supports IIS. I'm not sure if this is the first build that supports it, but I checked after the last automatic windows update and the IIS features are available; they were not before. I am on a m1 Mac using Parallels with the Windows Insider Preview ARM image.
Edition: Windows 11 Pro OS
Build: 22563.1
Experience: Windows Feature
Experience Pack 1000.22563.1.0
I'm using Windows 11 & IIS Express on a MacBook Pro M1 Max (via Parallels) and it is working fine. Of course, for developing environment!
You can download IIS Express from
https://www.microsoft.com/download/details.aspx?id=48264
You can download the ASP.NET Core Runtime or .NET 5.0 SDK to allow you run to run ASP.NET applications on Windows, Mac or Linux.
See https://support.microsoft.com/en-us/windows/downloads-for-windows-32490f9b-01ee-c13e-b2af-b5057c2d34e8

Starting the WindowsPhone 7 emulator crashes running instances of VMWare (Server)

I have a machine running Windows 7 Professional SP1 directly on hardware.
I use this machine for all developing stuff. As this includes web– as well as WP7–development I have some virtual linux-hosts running inside VMWareServer2 for my webdevelopment.
As soon as I start the WindowsPhone emulator (natively, not inside any of the VMWare client-instances) all the VMWare machines stop working and remain unstartable upon restart of my Windows 7 machine.
It seems, that the launch of WindowsPhone emulator (which is a virtual machine itself) crashes VMWareServer and keeps it locked down even after the WindowsPhone emulator was closed.
How can I prevent the WindowsPhone emulator from crashing VMWareServer?
Have a look at this blog post, he seems to have the same problems as you and found a work around... Although not an idea one he had to disable hardware assisted emulation in VMWareServer.
VMWare themselves just say to uninstall the competitors emulator... as if that was an option
http://pcbl.de/2011/06/13/round-1-fight-windows-phone-7-emulator-x-vmware/

Windows phone 8 SDK - This computer does not support hardware virtualization, which means Windows Phone Emulator 8.0 can't run on this PC [duplicate]

This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Unable to create the virtual machine
Warning during installation of WP8 SDK: "This computer does not support hardware virtualization, which means Windows Phone Emulator 8.0 can't run on this PC."
Environment:
Windows 8 Enterprise 64, on a VirtualBox VM, 4G RAM.
Thanks!
This issue is that you cannot have a box inside of a box and expect to have the same exact coin in each box, that is to say that you cannot run a virtual machine in a virtual machine and have them both using hardware virtualization extensions to speedup processing, I't looks like your running in a virtual machine which is your issue. To use the virtual phone you must install windows 8 on your base pc, or another windows 8 compatible pc. This is the only way to use the software due to the way it was coded.
You must run your Windows 8 instance on bare metal, not in a virtual machine, to be able to test WP8 apps on WP8 emulator.
I've described more requirements for the WP8 development here:
https://stackoverflow.com/a/13145586/574062

Developing for WP8 with only WP7 device?

I don't understand from today's WP8 event: will I be able to develop apps working on both 7.5 and 8, having only one 7.5 (7.8) device for testing?
I don't like WP emulator, even though it's better than iOS/Android ones. I know that in Visual Studio 2012 it will become even better. But still!
Current devices running Windows Phone 7.X will be able to be upgraded to Windows Phone 7.8 but not Windows Phone 8.
If you want to use a feature that is specific to WP8 you'll either have to wait for hardware or use the eumlator (when available).
I don't like WP emulator
But you should. The emulator for Windows Phone 8 is a full featured Hyper-V emulator, that can even run unmanaged code.
As pointed out by Matt, you'll not be able to do any deployment of Windows Phone 8 apps to your Windows Phone 7 device, and as such you'll need a new device, or use the emulator.
And as the SDK is likely to be released before any devices, I'll strongly encourage you to do development in the emulator until the real devices are on the market.
You'll have to use Windows Phone 8 emulator, or cross your fingers that the equivalent to XDA-Developers for Windows Phone roots your model of phone and is able to get Windows 8 working(hint: unlikely)
The Windows Phone 8 emulator is really very nice though. The only big troubling thing about it is that it requires hardware Hyper-V support and Windows 8. This means you can't run the phone emulator inside of most virtualization technologies. However, I've been using VMWare 9 which appears to include an "unsupported" feature to allow Hyper-V to work though.. So your only choice for running the phone emulator is to either buy VMWare 9 or upgrade a physical machine to Windows 8

ultimate virtual solution for testing <=IE8 browsers

I need to know of a solution to run a local test server through a virtual guest. I am able to use Virtual PC as well as most the other solutions. My current workaround is to deploy to Tomcat on Windows 7 and test the main current browsers there. I am also able to mount share my Tomcat instance to Ubuntu so am able to run the same app without redeploying.
Currently I just invested on a Windows upgrade to be able to try out Microsofts ie8 and down VHDs but the best I am able to do with this is deploy to production server and then run the ie6, ie7 and ie8 browsers which is very time consuming.
Any suggestions or pointers for me? Ultimately a working solution to run these VHds or browsers in VirtualBox would be ideal for me, as I am familiar with it.
Related to my question I have come across some useful tutorials that may help others who find this question:
Virtual PC solution for legacy IE browsers in Windows 7
VmWare solution
You can just use one Windows version (XP, Win7 will be fine) and install IETester:
http://www.my-debugbar.com/wiki/IETester/HomePage
My solution is as follows & will only work with upgraded Windows 7 (not home premium).
Uninstall IE9 update to bring back IE8, IE9 seems to support css3 well, so testing in FF7 should be good enough for IE9.
Then follow this tutorial and repeat the process for as many virtual browsers you want. Note
I did include IE8 but don't use it as it's slower to run a virtual PC than native IE8 just in case I wish to reinstall IE9.
I use quirks mode in IE8 to test for IE7 and IE6 can go to Davy Jones Locker :D
When using xpmode, you must copy the xp disk each time without any updates and start process from scratch.
I also use VirtualBox to test Linux browsers as it's faster than Virtual PC and I share test server (Tomcat) so am able to run same instance without redeploying.
Hope this helps...