Geeks With Blogs


Google My Blog

Catch me at: The List!

My InstallScript Utility Belt My Amazon Wishlist
My Standard Disclaimer

Chris G. Williams Beware: I mix tech and personal interests here.
I got a review copy of SlickEdit recently and over the last couple weeks, I fired it up to check it out. These are my thoughts...

Overall, it's a lightweight alternative to Visual Studio .NET. I can customize the look and feel and can build from it, and the memory footprint seems pretty small, so it's not all bad.

It's not all good either. I don't know if I'm just spoiled on Visual Studio, but a lot of the "not entirely necessary, but nice to have" features that I've come to rely on just aren't there. Or if they are there, I can't find them.

Could Visual Studio be more intuitive than SlickEdit? 

It was for me. If I open a solution file, I assume it's going to open the solution, not just show me the contents of the file. It didn't occur to me that I had to open a workspace in order to see my solution. Sure I figured it out eventually, but it wasn't obvious.

Hitting F5 to debug is pretty intuitive, except I had to go in and configure some command line stuff first before it would work. Fail.  If they can configure it to build right out of the box, then debug should be just as easy.

This probably sounds more negative than I mean it to be. It's not a bad product, and I'm sure there is a market for it. If I had more time to really dig into all of the various features and settings, I might like it better, but for now (and the foreseeable future) I'm sticking with Visual Studio .NET. Posted on Friday, June 20, 2008 11:04 AM General Interest , Reviews | Back to top

Comments on this post: my thoughts on SlickEdit

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Chris G. Williams | Powered by: