How to debug a .net 4.0 program on Windows XP? - visual-studio

I have Windows 8 + Visual Studio 2013 and made a program that runs with .net 4.0 on Windows XP. I'd really like to debug it on Windows XP, but I have no idea how.
I guess I'd need Visual Studio 2010, but I can't find a legal download link for it.
Any other ideas what I could do?

You can download an .iso for Microsoft Visual Express 2010 for Windows XP and install it (for example) with virtual clone drive.
It works flawlessly, if you adapt your .sln file as explained here:
open visual studio 2012 projects in visual studio 2008

Related

VS2010 and Windows 8.1

I've been developing with VB 2010 and Windows 7 for years.
Are there any "issues" I should be aware off when migrating VB2010 over to Windows 8.1
Any advice will be much appreciated.
John
Make sure you install the latest service packs and hotfixes to be fully compatible with Windows 8 and above:
Visual Studio 2010
Visual Studio 2010 SP1
Visual Studio 2010 GDR for Team Foundation Service
Visual Studio 2010 Compatibility Update for Windows 8 and Visual Studio 2012
You will need to upgrade your Visual Studio version to 2013 in order to build Windows 8 and 8.1 apps, but as long as you're targeting a Desktop application, you should be fine.
I have used visual studio 2010 on windows 8.1 and windows 10 so far I did not have any issues working on both the OS.
I am using visual studio 2010 professional with sp1
Me too have been using the VS 2010 Professional on windows 7 and I migrated to Windows 8.1.
Usually I develop console apps, desktop apps and I mostly use Access Databases as the database for my programs..
And also I use C# and VB..
So far I havent had any issue with VS2010 on windows 8.1.
That is my experience about that and I hope this will be a help for you.. :)
Thanks

Visual Studio for Windows Embedded 8.1 Industry

I'm currently using Visual Studio 2008 with WinCE 7 BSPs. If I'd like to move on to Windows Embedded 8.1 Industry BSPs, can I use Visual Studio 2008 itself or I need to install VS 2013? My OS is Windows 7. Also, what all base BSPs come along with the installation?
Windows Embedded INDUSTRY 8.1 is based on full-windows and does not require Visual Studio or any other development tool to configure the OS. You can do that interactively.
Windows Embedded COMPACT 2013 (sorry for the bold, but it's to highlight naming differences) is the next release of WinCE7 (you can call it WinCE8, no one will be offended :) ) and requires Visual Studio 2012.

Is Visual Studio 2005 compatible with windows 8.1 64 bit?

I haven't tried installing it either on windows 8.
I need to modify a program which uses a crystal report 2005 (w/c i think is included on the vs2005 professional installer)
It should work just fine after installing the required service packs and patches:
Visual Studio 2005
Visual Studio 2005 SP1
Visual Studio 2005 Update
for Vista
If you are connecting to TFS to get the sources, you might need to install more, see this blog post for details.

Install Visual Studio 2005 on Windows 8

I am currently working on a long-term project for which I need Visual Studio 2005, 2008, 2012 (2010 not necessary). Right now I have Windows 7, but I would really like to upgrade. Is it possible to install all of those versions of Visual Studio on Windows 8?
2012 can obviously installed (and takes away the need for 2010). I already found reports that 2008 is also possible if the 3.5 framework is enabled through Windows Features, but I'm unsure about Visual Studio 2005.
Is it possible and does anybody have any experience with this?
PS: Do not come with solutions as "Why still use 2005, 2008, ...", I really need it.
After installing it on VMWare (Virtualbox gives errors) I've enabled framework 3.5 (which indeed contains 2.0 and 2.5). After that I've installed Visual Studio C# Express Edition. During installation and startup of VS it gives a lot of "This program has been known for comptability problems" warnings and they offer to search help online or to run it as usual. I've always opted to let it run as usual. It installed fine and I could compile and run a Visual C# Windows application.
Visual Studio 2005 Standard installed mostly fine for me. I installed it on Windows 8 on an x64 CPU. It complained a bunch about "known compatibility issues," but if I told it to carry on everything seemed to go fine. The only catch was that "Microsoft SQL Server 2005 Express Edition x64" failed to install. Also, I had to run Visual Studio as administrator the first time so it could finish its setup, but after that I've just run it with my normal account.
Download Windows 8 Enterprise Evaluation and install to VMWare or Virtual Box. It's a 3 month trial and would allow you to test VS2005 plus the others. Once downloaded, it's a fast install. You can download from here: http://msdn.microsoft.com/en-us/evalcenter/jj554510.aspx
For an install of Visual Studio 2005 on Windows 7 as well as Windows 8 I install three things: (1) Visual Studio 2005, (2) Visual Studio 2005 Service Pack 1, and (3) Visual Studio 2005 Service Pack 1 Update for Windows Vista.
The Visual Studio 2005 service packs can be a bit difficult to locate on Microsoft's web site since everything is really about Visual Studio 2012 and later.
When installing Visual Studio 2005, there will be a number of Incompatible warnings displayed. I just click through them to get to the end.
Also I do a custom install and do not install some components: (1) Crystal Reports and (2) SQL Server 2005 Express Edition.
Microsoft Visual Studio 2005 Team Suite Service Pack 1 which seems to be for all editions of Visual Studio 2005 including Professional Edition which I use.
Microsoft Visual Studio 2005 Service Pack 1 Update for Windows Vista is required to update Service Pack 1 to work with Windows Vista and later.
Visual Studio 2005 / 2008 won't install by default on Windows versions later than 7.
In Windows 8.1, go to:
Control Panel > Programs and Features > Turn Windows features on or off
Check the box labeled ".NET 3.5 (Includes 1.0 and 2.0)" and press OK / Apply.
My system has issues with trying to download the files for such programs, and thus there is a way to bypass this error by running a script which installs the files from a Windows installation disc.
Here is the script (for error 0x800F0906, at least):
Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess
You can replace /Source:D: with whatever drive letter you may be using for your optical / virtual drive, if needed.

Windows Mobile & Windows Phone development on one box?

I've been developing for Windows Mobile/Pocket PC for a number of years without any issues. I recently started getting "Unable to start debugging" error messages after I installed Visual Studio 2010 and Windows Phone 7.1 SDK. The Visual Studio 2008 Remote tools would work, and Visual Studio could deploy the files, but "Start with Debugging" would not work while "Start without Debugging" would work.
I uninstalled the Windows Phone 7 SDK and am able to debug Windows Mobile applications again. Is there any way to allow the Windows Mobile 6.x and Windows Phone 7 SDKs to coexist on one computer?
With these Errors Double Check and make sure Service Pack one is installed for 2010.
Trevor, this issue has been reported as a bug with a known workaround by Jeffrey Walton on Microsoft Connect. The fix is summarized as follows:
Rename the directory C:\Program Files\Microsoft Visual Studio 10.0\SmartDevices\Debugger\target\wce400\armv4i to armv4i_temp
Copy the directory C:\Program Files\Microsoft Visual Studio 9.0\SmartDevices\Debugger\target\wce400\armv4i inside the Visual Studio 2010 path.
Reference: VS 2010 Windows Phone 7 Developer Tools breaks existing VS 2008 Windows Mobile Developer Tools
Visual Studio 2010 can not build (much less debug) a Windows Mobile application. It can develop for Windows Phone 7 (apparently - I certainly do not develop for it).
To develop (build/debug) for Windows Mobile, drop back to Visual Studio 2008. That's the last version of Visual Studio that offered support for Windows Mobile.
Unfortunate.
Right edm2.exe and other remote debugger Arm4i files versions must be deployed to device. Rename temporarily all folders containing edm3.exe and try VS2008 debug. If works, search edm*.exe in registry and repair related keys to VS2008only state.

Resources