Page 2 of 3
Re: Vistual studio community 2017
Posted: Fri Nov 17, 2017 7:49 pm
by Michael Sherwin
I'm having trouble with 2 thousand errors as well. Unfortunately the errors are all in my DNA.
Re: Vistual studio community 2017
Posted: Mon Nov 20, 2017 3:19 am
by jdart
What is this IDE you speak of? All you need is a terminal and emacs.
I have had no special problem with VC++ but I am not using C#.
--Jon
Re: Vistual studio community 2017
Posted: Mon Nov 20, 2017 7:14 am
by Dann Corbit
jdart wrote:What is this IDE you speak of? All you need is a terminal and emacs.
I have had no special problem with VC++ but I am not using C#.
--Jon
I like code::blocks on Ubuntu.
Using Visual Studio has made me lazy
Re: Vistual studio community 2017
Posted: Mon Nov 20, 2017 9:47 am
by Daniel Anulliero
Dann Corbit wrote:jdart wrote:What is this IDE you speak of? All you need is a terminal and emacs.
I have had no special problem with VC++ but I am not using C#.
--Jon
I like code::blocks on Ubuntu.
Using Visual Studio has made me lazy
I use code::blocks too but on win 7
It is free , good , have a profiler
I think it is sufficent to do my hobby , and I think it is sufficent for a "no progress" engine too
Re: Vistual studio community 2017
Posted: Mon Nov 20, 2017 10:39 am
by Henk
Thirty years ago I was using vi too. Using OO to open a new line and :wq to quit and saving edits.
And 'i' to insert a character.
Re: Vistual studio community 2017
Posted: Mon Nov 20, 2017 11:22 am
by pkumar
Hi Daniel,
I use code::blocks too - an old version(12.11) on win 7. I tried a recent version(16.01). While compiling, the display goes haywire - then recovers. I did not understand why. After this happened several times I went back to the old version. Which is your version and have you faced any such problem?
Regards
Re: Vistual studio community 2017
Posted: Mon Nov 20, 2017 12:08 pm
by Daniel Anulliero
pkumar wrote:Hi Daniel,
I use code::blocks too - an old version(12.11) on win 7. I tried a recent version(16.01). While compiling, the display goes haywire - then recovers. I did not understand why. After this happened several times I went back to the old version. Which is your version and have you faced any such problem?
Regards
Hello
I think I use a recent version and these things didn't happened for me . This evening I'll say to you the exact version I use , I'm not at home.(show a screen shot of your problem if you can).
But I remember I leaved the 12 .xx version because I never made the profiling plug in working properly.
Best
Re: Vistual studio community 2017
Posted: Mon Nov 20, 2017 2:19 pm
by Look
pkumar wrote:Hi Daniel,
I use code::blocks too - an old version(12.11) on win 7. I tried a recent version(16.01). While compiling, the display goes haywire - then recovers. I did not understand why. After this happened several times I went back to the old version. Which is your version and have you faced any such problem?
Regards
If you want, you can try this new RC version:
http://forums.codeblocks.org/index.php/ ... 265.0.html
Re: Vistual studio community 2017
Posted: Tue Nov 21, 2017 12:24 am
by cdani
Dann Corbit wrote:jdart wrote:What is this IDE you speak of? All you need is a terminal and emacs.
I have had no special problem with VC++ but I am not using C#.
--Jon
I like code::blocks on Ubuntu.
Using Visual Studio has made me lazy
Using Visual Studio has made me go much faster than any other alternative, starting from vi, pascal, delphi... Why have to do strange things instead of just producing? I'm not interested on doing things by hand.
Re: Vistual studio community 2017
Posted: Tue Nov 21, 2017 12:38 am
by tttony
Dann Corbit wrote:jdart wrote:What is this IDE you speak of? All you need is a terminal and emacs.
I have had no special problem with VC++ but I am not using C#.
--Jon
I like code::blocks on Ubuntu.
Using Visual Studio has made me lazy
There is no doubt that VS is the best IDE to debug, also you can add some add-on to get a better experience