alternative to visual studio 2010 - ide

Is there any alternative to visual studio 2010 for develop with .net 4.0?
thanks

Considering that .NET 4.0 only just came out (at the same time as VS 2010) I would hazard a guess at "No". :)
In general, Visual Studio is by far the best IDE I've ever used. Nothing else even comes close.

You can use SharpDevelop to develop .NET projects, including .NET version 4.0. SharpDevelop 4.0 final has been released 06/2011. (though the support for 4.0 is still in beta status AFAIK.)

Notepad and .net 4.0 compiler :-)

MonoDevelop is really catching up. It is not a 100% replacement of VS, because it is based on Mono. The IDE is starting to be really good (GUI designer, debugger, test framework, web and IPhone stuff etc. etc.). Supports .NET 3.5 for now.

The visual studio platform crashes frequeltly, Several times a day, especially when debugging.
I use sharpdevelop when debugging. It does not have all the features of VS, but it doesn't crash.

If you want to do your development in the cloud, check out www.coderun.com

Related

Can I install VB6 over VS 2010?

I have already using Visual Studio 2010 for my project. Now I have to work with a Visual Basic 2006 legacy application. Can I install VB 2006 Enterprise Edition on my system?
Will this affect Visual Studio 2010?
Yes. Visual Studio 2010 and Visual Studio 6 will happily install side-by-side.
You can run multiple versions of Visual Studio on the same machine. I currently have VS2003, VS2005, VS2008 and VS2010 installed and am using all of them.
Where you may get into problems is with something like hooking up the older ones to TFS. This can be done, as I have VS2003 and VS2008 connected to TFS2010, but my VS2005 won't work as it whinges about the provider for some reason.
Another area to watch out for is IIS. As you have already installed VS2010, IIS may be defaulting to .Net 4.0 so if you start deploying .Net 2.0 apps then the websites may not work without some adjustment of things like app pools.
But if you are just using them independently of each other then you should be fine. If you're really paranoid, consider creating a VM and installing the old VS on it.
EDIT
I see from your edited post that you were talking about VB6. This also can be installed alongside any of the later versions of Visual Studio.

Make ReSharper run test using .net Framework 3.5

I am currently testing sharepoint components using msTest, which works nicely. However, when I run my testst using ReSharper all tests fail because ReSharper (6) is running the tests using .net Framework 4.
Is it possible to configure ReSharper (6) to run all tests using .net Framework 3.5 (CLR 2)?
In case you use Visual Studio 2010: This is an issue in Visual Studio, not in ReSharper.
See Microsoft's answer:
Hi Chris,
In VS 2010, the Test Team has made a painful yet concious decision to
not support multi-targeting. As a result, test projects will be
upgraded to target .NET 4.0. We have made some, workarounds to allow a
VB Test Project that references an MVC code under test to not upgrade,
but in general, all others will be retargeted. The VB 3.5 Test Project
sill has some limitations and will always run tests in a .NET 4.0
process. Also, you cannot take the tests and run them on a VS 2008
test system.
Thanks Visual Studio Product Team.
in site http://connect.microsoft.com/VisualStudio/feedback/details/514130/visual-studio-2010-beta-2-silently-upgrades-mstest-test-projects-to-net-4-0.

Development for .NET 4.0 (Windows XP) with Visual Studio 2012

.NET 4.5 is an in-place-upgrade and therefore replaces .NET 4.0. Consequently when I install .NET 4.5 with Visual Studio 2012 I can no longer develop applications for .NET 4.0.
As .NET 4.5 is not supported under Windows XP, how can I maintain my existing .NET 4.0 applications which still have to run under Windows XP after I installed Visual Studio 2012?
Until now I could always devlop .NET applications for every version, even .NET 1.1, as long as VS2003 was installed. I don't have a problem with Microsoft not supporting .NET 4.5 on XP, I think it's allright to cut off old stuff.
But as we have still customers using Windows XP, we need to be able to create .NET 4.0 programs at the same time as .NET 4.5.
EDIT:
I just had my first incompatibility issue: I installed VS 2012 on a Windows Server 2012. I created a project targeting .NET 4.0. In blend 4.0 I create a copy of a control template of a checkbox. The generated template contains references on colors which are available only under .NET 4.5. The solution cannot be compiled any longer. However the same case works fine on my Windows 7 installation.
I assume that the installation of .NET 4.5 has replaced the control templates for my standard controls. Therefore I cannot create copies any longer.
Ironically, it seems Mono supports much of the .NET 4.5 functionality, and that it can be installed on Windows XP.
If your need C# 5.0's async and your client refuses to upgrade it's OS, this can be an option.
I have run into some serious issues developing .NET programs for 4.0 against computers with 4.5 installed. One issue, for instance, is that if you are doing WPF development and have a private setter on a property - if you're binding to that property with Mode=TwoWay, you will not get an exception if you're developing against .NET 4.5! You should get an exception and you will if you're in an environment with only .NET 4.0 installed (even though you're developing to target 4.0 in Visual Studio). Now obviously you should not have Mode=TwoWay and a private setter, but maybe you had originally intended for the property to be only OneWay. The point is that this is just one of many examples of issues that are simply swept under the rug by 4.5 and has caused me to go back to developing in Windows 7 with Visual Studio 2010 and .NET 4.0 for anything targeting .NET 4.0.
In the meantime I have found a great blog of Scot Hanselman which answers my concerns: http://www.hanselman.com/blog/NETVersioningAndMultiTargetingNET45IsAnInplaceUpgradeToNET40.aspx
.NET 4.5 is an in-place-upgrade and replaces the .NET 4.0 CLR, but it will still be possible to create .NET 4.0 applications with Visual Studio 2012.
EDIT: I now installed the final release of VS2012. My existing .NET 4.0 projects compile and run, no problems so far. The only drawback is, it doesn't support Windows Installer Projects any longer. You can switch forward and backward between VS2010 and VS2012.
BIG EDIT: We should wait until Microsoft announces the final decision, it's not clear yet, only conclusions.
But, I think that Microsoft won't drop support for XP and Vista that easy, it appears that the matter of decreasing support is just for speed-purposes to show it to the developers.
Also, if the it comes true and Microsoft Stopped the support for XP and Vista, then you have the virtual machine as an excellent choice!
Best wishes

.net 4 debugging api causes access violations in debugee

is there any way the .net 4 debugging api can somehow corrupt the state of an application during startup?
the issue i have is the following:
if i start my application from within a debugger using the .net debugging api (visual studio 2010, sharp develop 4, mdbg), i get various random access violations.
if i start my application from within a debugger not using the .net debugging api (delphi 2007, windbg with sos extension) everything works fine.
if i start my application directly and later on attach a debugger to it (like visual studio 2010, sharp develop 4, mdbg, delphi 2007, windbg), everything works fine.
if i move back to .net 3.5 and clr 2.0 i have no problems at all.
so what changed from .net 3.5 to 4.0 in the managed debugging api causing my application to throw access violations if started with it?
the application is written in delphi (unmanaged) and c# (managed) using managed vcl to do the interop.
i can hardly give any example to reproduce this issue so i'm aware that answering this question might be impossible, but if someone with more insight to the debugging api can give me a hint in the right direction or could help me narrow it down i'd be very thankful.
Just for fun try and disable the Visual Studio hosting process. In Visual Studio right click on the project, go to the 'Debug' tab, and uncheck the "Enable the Visual Studio hosing process" check box.
We've seen some strange stuff in the managed/unmanaged land on 64 bit systems running 32 bit apps.
Some additional info based on experience: It is important to use the COMPLUS_MDA environment variable (remember to restart VS2010 afterwards), not the MDA registry key. I tried setting the registry key (followed by restarting the computer) as described by the MSDN article http://msdn.microsoft.com/en-us/library/d21c150d, as the article indicated this should have the same result, but that didn't work.

Mono IDE on Windows

Is there any IDE for coding mono on windows platform?
MonoDevelop has now released a installer for Windows. You no longer need to build it from source. It is available from the MonoDevelop website
However on windows it runs on the .NET Framework, not Mono - it uses the .NET debugger instead of the Mono one.
SharpDevelop and Visual Studio will both work. You can also use the Windows version of MonoDevelop.
I would recommend #develop or check out the status of porting MonoDevelop (A fork of #develop) back to Windows.
SharpDevelop comes to mind... I've found this quick howto for setting up a development environment with it and Mono and windows:
http://yacoding.blogspot.com/2006/04/howto-mono-sharpdevelop-and-firebird.html
Use Delphi Prism 2010