Your thoughts on Visual Studio Integration?

[mike.griffin]

Of course, this pertains only to MyGeneration 2.0. Remember, time spent on Visual Studio Integration means other features may be cut or delayed.

[Mike Shepard]

But not a necessity. The command line works fine, and writing \"External Tools\" menu items is pretty easy (I'd post the link to the message on these forums if I had it, but it works fine).

[sbc]

To be honest, it wouldn't be something I would want as I don't use Visual Studio. But I can see it being useful for others. I wouldn't even require SharpDevelop integration.

SharpDevelop's advantages over Visual Studio are that it is free/open source, and can target .NET 2.0 and 1.1 (with version 2 beta) as well as Mono. If they can do it (for free as well), why can't Microsoft?

[mgnoonan]

SharpDevelop's advantages over Visual Studio are that it is free/open source, and can target .NET 2.0 and 1.1 (with version 2 beta) as well as Mono. If they can do it (for free as well), why can't Microsoft?

It's not a question of Microsoft's ability, it's matter of desire.

[sbc]

SharpDevelop's advantages over Visual Studio are that it is free/open source, and can target .NET 2.0 and 1.1 (with version 2 beta) as well as Mono. If they can do it (for free as well), why can't Microsoft?

It's not a question of Microsoft's ability, it's matter of desire.

How else could they sell you Visual Studio 2002, 2003 and 2005? If VS 2005 could target previous framework versions, then that would be all you would need. The excuse I have seen them come up with is that it is too tightly integrated with the version of the framework it was developed alongside with.

[mgnoonan]

Which, of course, is complete BS. If they made backwards compatibility a project goal, they could do it. Like I said, MS does planned obsolesence better than anybody.