Microsoft this week acquired Teamprise, a division of SourceGear that built tools to give developers access to Visual Studio 2008 Team Foundation Server from systems running Linux, Mac OS X and Unix.SourceGear's flagship SourceOffSite provides remote access to Visual SouceSafe, Microsoft's version control system.

Teamprise comes in three forms. The Plug-in for Eclipse allows developers source control, bug tracking, build and reporting operations from within their current Eclipse environment or Eclipse-based IDE. Teamprise Explorer does the same but can can stand alone. There's also the Command-Line Client automated builds and other scripting situations.

Updated to version 3.2 in March, Teamprise was given a complete command-line feature set, support for building projects with Maven and a single sign-on for Linux and Mac OS X with Kerberos authentication. All three modules at that time also gained support for HP-UX on IA64. Teamprise is now at version 3.3, which according to release notes, is a maintenance release.

Microsoft said in a statement that Teamprise functionality will be integrated into the Visual Studio product line beginning with Visual Studio 2010.

Visual Stupido - please, just hit me on the head with a brick! There are MUCH better IDE's for Linux and Unix if you need. Even a good editor and Make are (in my mind) preferable!

And their Visual Stupido on Linux is, of course, some remote access cloud-based thing that no sane programmer would ever want to use, but are so annoyingly easy to sell to the I-have-no-clue-what-my-employees-actually-do kind of managers. They probably sell this to managers by telling them that the remote access / cloud stuff allows their employees to work from anywhere on any platform.

For instance, on a 2 hour transfer at some airport on a business trip, the Micro$oft sales people will probably argue that their product allows your employees to be productive in those two hours, not mentioning that they'll need a high-bandwidth connection (the kind you rarely get at an airport), a secure connection (the kind you never get at an airport), an outlet to plug in the laptop (because their product will surely suck that battery dry in no time), a table to set it on (not to burn your lap), they'll need to connect through a VPN of some kind (and watch out for shoulder-surfing), probably wait a while for the sync to be completed, and then, they can start working, but will constantly be slowed down by all the lag in the system.

In the mean time, rubberman can be sitting in the same airport, with a small laptop that he doesn't have to plug in or take off his lap (because it's not overheating) and code away on his handy standalone light-weight code editor on his own local version of the code. If he ever has to commit his work up to the server, all he needs is a low-bandwidth unsecure wifi connection to send his work down an SSH pipe. No fuss, no trouble, no security issues, rubberman is a happy and stress-free man, while your employees are stressing out because they have work to do and they are stuck on the phone (paying roaming fees) with the tech-support of Microsoft to figure out why they can't even connect to the service (and the tech-support people argue that your company needs to upgrade their paid support plan in order for them to help you with this issue!).

If it wasn't clear already, I'm on rubberman's side here. Who would ever want to use a bad delivery (remote access) of a bad IDE (Visual Stupido) on a system like Linux which already has all of greatest development tools? (and mostly for free too)