I think that the Visual Studio source code editor will be really great once we develop a Harbour language support for it:
http://msdn.microsoft.com/en-us/library/dd885118.aspx
In fact I already emailed some developers that have created new languages extensions for it (Lua, Irony which it is a great tool to implement these extensions, etc) and some of them confirmed me that it may take some weeks to implement it. There are several free implementations that we could use as a template. Anyhow its quite complex and I would like to do it once there is a significant amount of Harbour + FWH users using Visual Studio. I don't like the idea to use UEStudio and Visual Studio together (I don't say that it may not work -you are using it that way-) but if already has a source code editor why should we use another one ? I do all my coding from UEStudio, but I don't discard to use the Visual Studio one.
I love its low level debugger. I have used it to step by step run C code and its wondeful. And it has much more features that once we learn to use them (code analysis, profiling, etc) we will have a real powerful tool in our hands to help us.
I have never used IDEs, because I don't feel comfortable with them, but if I have to choose one, my choice is Visual Studio
