Which version of Windows 7 should I install on my development PC? - windows-7

I am a .net and java deloper. I have an MSDN subscription with access to all editions of the Windows 7 operating system. I am going with a 64 bit installation. Which edition of Windows 7 should I install on my development PC: Professional, Ultimate, Enterprise, Enterprise N, etc.? Thanks in advance.

Put Ultimate on the box and run the others in virtual machines.

If you have access to all versions, I see no reason not to install Ultimate.

As long as your tools run on the OS it shouldn't matter
(btw: I'm running ultimate and it's working out fine)

I think you should use Vista, or even XP for developing your .Net Apps
the reason is your apps have to be backward compatible.
Remember most users still use XP.
And you cant sell your app to an XP user even if your app is very clever, because they cant install it.
And at last .Net is Platform independ , you can use it on which ever windows version you want. (even for Linux)
(excluded windows 3, 98)

Related

Can I bypass hyper-v with an earlier version of visual studio

I installed visual studio express 2013 on my windows 8.1 computer. Everything was fine until I learned that I needed 8.1 pro to have hyper-v to use a phone emulator to run my program. (I think)
Rather than downloading a new operating system, would I be able to use an earlier version of visual studio? If so, which one...
I am very new to phone development and (considering I can't get past the installation stage) would appreciate the simplest explanation out there.
Thanks!
Sadly, no. Hyper-V is a requirement for WinPhone emulation, and it requires Pro, no matter what version of VisualStudio
Note: To use the Windows Phone 8 emulator your PC must have Windows 8
Pro or greater and a processor that supports Second Level Address
Translation (SLAT).
https://www.dreamspark.com/student/Windows-Phone-8-App-Development.aspx
http://msdn.microsoft.com/en-us/library/windows/apps/ff626524(v=vs.105).aspx
However,you can easily upgrade to Pro, see http://windows.microsoft.com/en-us/windows-8/feature-packs You just buy an upgrade key and enter it, you don't have to go through the whole install a new OS process

Which Windows versions have preinstalled MSINET.OCX control

I have an old VB6 application that depends on MSINET.OCX. I'd like to know if I can distribute this application without registering MSINET OCX component. My target OSes are XP, Vista and Windows 7. Do all of them have this component preinstalled?
See if this information from technet helps you. The short of it seems to be that it does not come preinstalled, it is installed when you install an application that uses it. You will need to include it in your installation.
It's not shipping with the OS. It is however delivered with Visual Basic. You must include it within your application setup. For details on Vista and Win7 support see: Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7

Run Visual Studio 2002, 2003, and VB6 side-by-side on Windows 7

I am upgrading my machine to Windows 7 but I would still be supporting VS2002 (.net 1.0), VS2003 (.net 1.1) , and VB6 applications.
Is it possible to load these VS and VB6 applications, build, compile, edit code, and support this source code in Windows 7?
Best way to answer your question is to do an experiment. You can setup a VirtualBox whose guest OS is Windows 7, then put whatever programs inside and test out. If they run fine, it's okay to do the real upgrades.
Yes you can.
Refer here
http://www.vbmonster.com/Uwe/Forum.aspx/vb/33424/VB6-on-Windows-7-64-bit
You need a virtual machine. Sorry. You could always see if the virtual machine in Win7 works - but failing that, do what I did and create a virtual machine running XP and run it from there.
I'm pretty sure I've used VB6 and VS2003 on Vista in the past, so there shouldn't be a problem with 7. I'd second setting up a VirtualBox or maybe try VirtualPC to give it a go.
Even if for some strange reason you weren't able to install the development tools, you could (assuming you're using a high enough edition) use Windows XP mode for those tools that you couldn't get to run natively under Windows 7.

Can I use Windows XP for Windows Azure development

I have got the Windows Azure Platform account.
Fot he development with Windows Azure, can I use computer with Windows XP Professional.
If not what environment should i set to start working with Windows Azure, and migrating existing web projects to Windows Azure.
Regards.
Pravin.
Since azure uses Windows Server 2008 SP2/R2 as it's core OS, you will need at least Windows 7 or Windows Server 2008 to come close to mimicking the environment in Azure. If you are in a situation where you cannot upgrade your OS then you should look at utilizing a VM for development/testing purposes.
To answer your question, yes you can hack together a solution, is it pretty, no. Would I do it, no way. I also find that I like Windows 7 a lot better than XP or Vista, but I am also work for the man so I am jaded.

Has anyone had success with Visual Studio 6 on Windows 7?

VS6 popped off a series of errors before bombing out completely during install on Windows 7. I specifically need to get VB6 functioning on Windows 7. Anyone having any luck?
Folks on the VB6 newsgroup report they have managed to get it working on Windows 7.
There's this step-by-step guide on how to install the IDE on Windows 7 (including 64 bit).
If that doesn't work (scrapes barrel) try this old tip about persuading the install not to install the Java VM? Link is now broken so here is the tip:
Before trying to install VB6. Create a new file, name it msjava.dll and place it in your windows directory. The file can be zero length. You can then happily install without the prompt to install an old version of Microsoft's flavour of Java. Once you have installed VB6, delete the msjava.dll otherwise windows update will prompt you to update it.
Or (scrapes hole in barrel) these tips from an article about getting the IDE working on Vista?
Footnote: if developing with ADO, be aware of this.
The only way I've found that works is Windows XP mode (i.e. a virtual machine). Works fine there, but otherwise, not at all.
I found ALL the answers in a thread at vbmonster.com. As mentioned above, you CAN install Visual Studio 6 with Service Pack 6 under Windows 7 by following Derek's detailed instructions at fortypoundhead.com.
I had a problem because I needed to install Service Pack 5. I use a third party program that does not work with Service Pack 6. A really smart programmer (GuideX) came up with a great hack to get around the MDAC 2.5 error.
Win 7 64 bit service pack 5 & 6. Turn compatability off and it seems to work.
Recently I had to debug an ancient application written in Visual C++ 6.0 on Windows 8.1. Tried different solutions all of them failed, only this one worked.
This guys made a special installer that allows installing VC++6, VB6, and SP6 on Windows Vista/7/8/8.1/10 without any errors whatsoever.
Hope it would be helpful to someone.
I installed VB6 on Windows 7 Pro without having to use compatibility settings or run as administrator.
Doesn't really help you, but does show that it can work.
Several people in my office have installed Visual Studio 6 (without VC++) on Windows 7, both 32-bit and 64-bit with no problems. The one thing we have in common: we've all turned UAC down to it's lowest setting. Nothing else special required.
I am using vb6 on windows 7 32 bit system for a long time.
you will need to install your vb6 with compatibility of xp2.
Create a 0-byte file in the C:\Windows directory called msjava.dll.
Don't just install via the Autorun executable; instead browse the Visual Studio 6 CD (or folder), right-click Setup.exe and select Run As Administrator.
On any Program Compatibility Assistant warnings, click Run Program.
Step through the setup screens until you're able to choose Custom Setup, then click next.
On the setup options, install the following items and nothing else:
Microsoft Visual Basic 6.0
ActiveX
Data Access
Graphics
Click continue and the process will start, and (hopefully) eventually complete.
Skip the installations of the MSDN CD, BackOffice, VSS and SNA Server, and clear the checkbox for "Register Now". Setup should be complete.
Download the VB6 Service Pack 6 from http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=A8494EDB-2E89-4676-A16A-5C5477CB9713&displaylang=en and install.
Change the compatibility settings for Visual Basic (to get it to run a little more smoothly under Windows 7) by browsing to C:\Program Files\Microsoft Visual Studio\VB98, right-clicking the VB6.exe file, and selecting properties.
On the Compatibility tab, check the following:
Run this program in compatibility mode for Windows XP (Service Pack 3)
Disable Visual Themes
Disable Desktop Composition
Disable display scaling on high DPI settings
When you start up the IDE, you may get a notification saying that the color scheme has been changed to Windows 7 Basic, but it will be changed back to Aero once you exit. Everything should be working fine at this point!
Note: when you first run your new install vb6 run it with admin rights and with xp2 compatibility so that your exe can run on any system.
The word "supported" is used loosely in this thread, potentially leading the unwary reader to the conclusion that Microsoft supports the VB6 IDE (that is, the integrated development environment) on operating systems beyond Windows XP. This fact clearly is stated in the table that appears on the page at this link:
https://blogs.msdn.microsoft.com/nikosan/2012/04/20/support-statement-for-visual-basic-6-0-on-windows-8-updated/
Note that executables developed using VB6 are in fact compatible with Windows OS's from Windows XP through Windows 10--32/64-bit versions:
https://blogs.windows.com/buildingapps/2015/06/22/getting-ready-for-windows-10-sdks-compatibility-bridges/
Anyone using non-standard methods to coax the IDE into working on OS's that Microsoft does not support is exposing themselves/their organizations/their employers to risk and is not suitable for risk-averse organizations.
Having said that, I think the purest solution is to install Windows XP onto a virtual machine and run that VM in a modern host OS, such as Windows 10. That works just fine, and you can install directly from the VB6 Setup disc without making any pre-install/post-install customizations.
I had a Vista x64 box with a working copy of the VB6 IDE (which was supported). I upgraded the OS to Windows 7 x64 and the VB6 IDE still works fine. You could try that. I know, a huge PITA and kludgy but still, it worked for me.
I run Windows 7 Ultimate 32-bit, installed Windows Virtual PC - XP Mode, and that solved my problem isince I can run MSDEV 6.0 in the XP Window.
Not esay to install XP Mode though, the MS site is buggy.
The VB6 programming language is supported on the Windows 10 Technical Preview.
Visual Vasic 6 applications run and the VB6 IDE installs and works too.
I have the VB6 IDE running OK on Win-XP-16, Win-7-32, Win-7-64, Win-8.1-32, Win-8.1-64, win-10-32 and win-10-64 by using the instructions above which basically say, turn off UAC, run the installer AS ADMIN, and then set the VB6.exe file to run in XP-SP3 Compatibility mode.
I have had some issues with it and have had to do a bit more googling to solve these but I don't remember any more what those issues or solutions were.
I've even got the VB3 IDE running on the 32-bit versions of XP, Win-7, Win 8.1 and Win-10 - without even installing them - just copied the C:\VB folder from another computer and copied the *.LIC license files and *.VBX etc files as well.
I have successfully installed vb6 on win 7 32 bit by installing xp first then installing new win 7, (not upgrade), and do not format. then it will install vb6 without a problem
It's depending on your build version of Windows 7.
If your Win7's version is lower or is not updated, it has MANY PROBLEMS with compatibility.
But mine is newer Win7 version and has NO COMPATIBILITY TROUBLE.
I am currently using VB6 , VS6 and they still work fine!
If Properties->Compatibility->Windows XP doesn't help, fix it with UPDATING your Win7.

Resources