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.
Vistual studio community 2017
Moderators: hgm, Rebel, chrisw
-
- Posts: 100
- Joined: Tue Oct 15, 2013 5:45 pm
Re: Vistual studio community 2017
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
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
-
- Posts: 759
- Joined: Fri Jan 04, 2013 4:55 pm
- Location: Nice
Re: Vistual studio community 2017
Hellopkumar 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
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
Isa download :
-
- Posts: 366
- Joined: Thu Jun 05, 2014 2:14 pm
- Location: Iran
- Full name: Mehdi Amini
Re: Vistual studio community 2017
If you want, you can try this new RC version: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
http://forums.codeblocks.org/index.php/ ... 265.0.html
Farewell.
-
- Posts: 2204
- Joined: Sat Jan 18, 2014 10:24 am
- Location: Andorra
Re: Vistual studio community 2017
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.Dann Corbit wrote:I like code::blocks on Ubuntu.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
Using Visual Studio has made me lazy
Daniel José - http://www.andscacs.com
-
- Posts: 268
- Joined: Sun Apr 24, 2011 12:33 am
Re: Vistual studio community 2017
There is no doubt that VS is the best IDE to debug, also you can add some add-on to get a better experienceDann Corbit wrote:I like code::blocks on Ubuntu.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
Using Visual Studio has made me lazy
Skiull http://skiull.blogspot.com
-
- Posts: 2488
- Joined: Tue Aug 30, 2016 8:19 pm
- Full name: Rasmus Althoff
Re: Visual studio community 2017
I'm just using Notepad++, also professionally. Sometimes, the only kind of "debugger" available is an oscilloscope, attached to some I/O pin of the microcontroller. In very difficult cases, not even that because it alters the timing. Then it's the Chuck Norris way - staring at the code and forcing it to confess.jdart wrote:What is this IDE you speak of?
-
- Posts: 100
- Joined: Tue Oct 15, 2013 5:45 pm
Re: Vistual studio community 2017
I installed CB 16.01 again. There was no difficulty in rebuilding a project a few times. So I shall continue with this till the problem reappears. It may be relevant that my laptop has 4 GB of memory and quite a few other windows were open when CB crashed.
-
- Posts: 100
- Joined: Tue Oct 15, 2013 5:45 pm
Re: Vistual studio community 2017
I installed CB 16.01 again. If there is any problem I shall try the RC version. Thanks for the link.
-
- Posts: 7220
- Joined: Mon May 27, 2013 10:31 am
Re: Vistual studio community 2017
I also get this error when opening my project:
Some of the properties associated with the solution could not be read.
Very accurate warning (not). Which properties?
Some of the properties associated with the solution could not be read.
Very accurate warning (not). Which properties?