TalkChess.com

Using visual studio community 2017 now. But it is equal like trusting a bad salesman.

For instance in 2015 version when I made a major change I get say 2000 compile errors. But now it's given me 40 times fifty compile errors. So each time when you think you have fixed the compile errors you get another fifty.
If it had told me in advance the right number of errors I probably would have changed something else.


It already started cheating when installing it. Installation only took a few minutes but when I opened an existing project it let me wait for hours before everything was installed. Also for using new C# features I still have to use NUGET to install the right packages.

Henk wrote:So each time when you think you have fixed the compile errors you get another fifty.

I bet you can configure this, but the new behaviour makes more sense anyway. If your code actually has 2000 compile errors, you are maybe trying to compile a program in one language with a compiler for a different language.

What's more probable is that there are a handful real errors, and the rest are followup-errors. It doesn't make sense to have that useless followup error spew that will vanish anyway when fixing the few actual errors.

Henk wrote:Using visual studio community 2017 now. But it is equal like trusting a bad salesman.

For instance in 2015 version when I made a major change I get say 2000 compile errors. But now it's given me 40 times fifty compile errors. So each time when you think you have fixed the compile errors you get another fifty.
If it had told me in advance the right number of errors I probably would have changed something else.


It already started cheating when installing it. Installation only took a few minutes but when I opened an existing project it let me wait for hours before everything was installed. Also for using new C# features I still have to use NUGET to install the right packages.

The more errors it shows you, the happier you should be.

You may feel better if you know I usually get the same with Xcode (in Mac world) in which I set using GNU compilers for compiling C++.

Henk wrote:when I made a major change I get say 2000 compile errors.

Always look at the compiler's *first* error message. People tend to only look at the last message they see (where everything else has already scrolled away) and try to fix that. This may sometimes reduce the number of errors from 2000 to 1999 while fixing the first error has big potential to solve all of them at once.

However, this is not related to any specific compiler. You can easily get 2000+ compile errors with gcc with one simple typo.

Sven wrote: However, this is not related to any specific compiler. You can easily get 2000+ compile errors with gcc with one simple typo.

Indeed it happen

After two days of dealing with annoying compile errors I now can start with run time errors.

Only change was moving time control from position to (game) player because that would fit better in data model

Nothing new. If your data model is not right you are in trouble. Twenty years ago I heard if your data model isn't right you have to start all over again.

Few years ago someone told me that database changes should not be a problem. I did not believe him and I still think he is wrong. Maybe small changes in data model are do-able.

Extending a data model is a different story. If extension means you 'only' need to add.

I had have some problem me too with VS2017 but I have solved all of them, with a few googling. Now I'm satisfied with this IDE, more than with any of the other ones. Recently I've found usefull NetBeans but just for html/php projects. For C++ I think that VS2017 is the best choice.

Good luck with your... two thousands errors!