SlickEdit Community
SlickEdit Product Discussion => SlickEdit® => Topic started by: cillybole on August 29, 2014, 08:44:11 AM
-
I've used slickedit for many many years now. I'm a driver developer and have always been able to get away by using command line build scripts/makefiles and configuring slickedit to use them. It's getting harder and harder these days to not use Visual Studio. They're pushing driver development over to it, obviously all the .NET languages want you there, etc. My #1 issue is emacs keybindings. I can't work without them (the emacs bindings plugin for VStudio sucks so it's not really an option).
So, I haven't upgraded my Slickedit version since 2008. I'm wondering, is it worth upgrading to 2013 given my above requirements? Can I use Slickedit as a full replacement for Visual Studio now? Or, is there a Slickedit plugin for Visual Studio (I seem to recall something like this). Or, what are my options? Thanks for reading.
-
is there a Slickedit plugin for Visual Studio (I seem to recall something like this)
There used to be one, but it's discontinued. I honestly don't know how anyone makes a product that's a VS plug-in since the programming model seems to be built on shifting sands.
-
With the somewhat new WDK integration into VS you can deal with VS solutions and projects, I think.
SE is able to import them as workspace/project(s) and you should be fine and you could use SE as usual :)
You can use VS just as a more or less convenient configuration tool.
AFAIK the kernel debugger integration into VS still lacks important features so you won't miss it.
BTW SE2013 already supports windbg based debugging.
In the sense of upgrading SlickEdit note that SE2014 (v19) provides VS2013 support.
So I'd recommend to upgrade to SE2014 if you don't profit from annual maintenance, yet.
HS2
PS: Please note that I'm guessing. I'm currently not involved in a driver project.
-
Thanks for the responses and @hs2, you're right about the integration level currently with slickedit. Well, I haven't tried to import the .sln I just create makefile based projects in slickedit and then use msbuild to build the .sln files. It's kludgy but I still obviously get symbols / tags and compile error parsing stuff so it's good enough.
So you're suggesting I go to SE2014 v19? Is it available yet? If so, I'll get that. Thanks again.
-
Using sln directly just works. Nowadays there is no need for manual interaction :)
I was also using handcrafted SE workspace/projects and build commands time ago when I made a KMDF driver. Well, it was still SOURCES based at that time ;)
SE2014 is currently in beta testing phase (see the changes here (http://community.slickedit.com/index.php/topic,10188.0.html)) and the release will follow soon.
I'd wait a bit and get the latest and greatest SE version coming with some very good improvements besides VS2013 support.
HS2
-
Ok cool -thanks for the info. Is there anyway I can get my hands on the beta now or buy now and get v19 when it comes out (without paying for the maintenance)? Thanks again.
-
Actually, it looks like I can download the beta now. I'd like to buy asap before my boss forgets he gave me the go ahead :) So, I'm still interested in knowing if I can pay now and still get the upgrade when it comes out. Thanks a lot.
-
Just contact sales@slickedit.com. I'm sure they can help and find a way :)
HS2
-
Awesome - you've been helpful HS2, thanks man.
~billy