SharpDevelop review.
Well, I'm kind of where I figured I would be after looking over things quickly yesterday.
SharpDevelop was number 1 on my list and I'm happy with it so far. The first thing I wanted to test was the ability to read in my old solution. Creating new solutions in other IDE's from existing projects is typically not a huge deal, but it is an annoyance. SharpDevelop opened it without any issue at all and even allowed me to quickly and easily convert it from the .Net 3.5 project for a .Net 4.0. A good point because it means this is also means my RecipeTracker downloads should work almost out of the box with this, just need to download the 3rd party references.
I would say that this is about 95% of the way to being as good as visual studio for day to day development which is HUGE for open source. The intellisense is where it lacks for me, but this is all preference I would say. It is also a strong point at the same time. There are some aspects of the intellisense that are better than the intellisense and then there are some where I like Visual Studio better. It is just different and I have had a lot of time to get used to how VS does it and from time to time it throws me off. The other small item is performance, with large files and all of the intellisense features I find the UI has an almost imperceptible delay, but it is definitely there.
So, unless I hit something I can't do I'll be sticking with this one for now.
SharpDevelop was number 1 on my list and I'm happy with it so far. The first thing I wanted to test was the ability to read in my old solution. Creating new solutions in other IDE's from existing projects is typically not a huge deal, but it is an annoyance. SharpDevelop opened it without any issue at all and even allowed me to quickly and easily convert it from the .Net 3.5 project for a .Net 4.0. A good point because it means this is also means my RecipeTracker downloads should work almost out of the box with this, just need to download the 3rd party references.
I would say that this is about 95% of the way to being as good as visual studio for day to day development which is HUGE for open source. The intellisense is where it lacks for me, but this is all preference I would say. It is also a strong point at the same time. There are some aspects of the intellisense that are better than the intellisense and then there are some where I like Visual Studio better. It is just different and I have had a lot of time to get used to how VS does it and from time to time it throws me off. The other small item is performance, with large files and all of the intellisense features I find the UI has an almost imperceptible delay, but it is definitely there.
So, unless I hit something I can't do I'll be sticking with this one for now.
Comments
Post a Comment