No Extensibility Support on Express

Published 14 November 05 04:09 AM | adrian

Buat yang sudah pernah menggunakan Visual Studio Team System Beta 2, berikut adalah bagian-bagian yang tidak disupport dalam versi Express (on suck-iness order):

  1. Extensibility, that means Refactor! won't work, Code Rush, and all other stuff that is built into the IDE. External tools like Code Snippet editor and third party controls are working, though.
  2. Deployment Tools, nothing more than XCOPY deployment methods. That is, unless you used external tools such as InstallShield etc.
  3. Documentation, it's just a shortened version of the full MSDN Library.
  4. Source Code Control, not even Visual Source Safe 2005.
  5. Unit Testing, are we supposed to live with NUnit? But, IMO, NUnit was easier than VS Unit Test.

Khusus yang nomor 1, baik di situs MSDN maupun DevExpress tidak di-state bahwa Refactor! tidak akan jalan di Express.

Share this post: | | | |
Filed under:

Comments

# adrian said on November 15, 2005 04:25 AM:

no. 1, I'll explore further. I know Express products don't come in with VSIP (Visual Studio Integration Partner) module. If it's still possible to create normal add-ins, then extensibility is no problem. After all, I did create my Refactor-Z using normal add-in. VSIP is needed only if you need to parse the whole source code, things like http://www.wholetomato.com/

no. 2, What's wrong with XCopy? The beauty of .Net is private folder deployment. You put all your files and DLLs in one folder, and run it from there. Thats how we install in my previous company.

no. 3, Uh, you can always install the full MSDN Library that you receive from MSDNAA. And the always-up-to-date is http://msdn.microsoft.com anyway

no. 4, is what a team of programmers need, as such it's only available in Visual Studio Team System.

no. 5, unit testing can be done on .net assemblies, not on the source code. thus external tools can be used (or created yourself). this one works with express btw http://weblogs.asp.net/nunitaddin/archive/2005/11/07/429825.aspx

# adrian said on November 15, 2005 09:18 AM:

no. 2, the wrong with XCopy is that it's not the "standard" method of software distro. Ordinary people uses installer, and ZIP files are sometimes just too much for them.

no. 4, SCC is not just for team development, you will still need to implement source code control system. Pengalaman gw sih enak banget buat coba-coba fitur baru yang belum pernah, contoh NSnake, setelah CTP release, gw mau coba pake DirectX, ternyata belum cukup kemampuan, nah tinggal direvert aja ke code CTP buat develop lebih lanjut.

It's not about the bundling (of VSS), tapi tentang support dari IDE. Kalo suatu ketika hobbyist ini perlu SCC, mau ngga mau harus up ke Pro, padahal SCC yang untuk personal cukup banyak.