The single most important setting in the whole of AS7

Go To Last Post
10 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0


I just got so irritated with Visual Studio that I had to find a way to turn off the dreadful "Error List" it shows to summarise the failures in a build - it does not show entire errors, they are in the wrong order (the worst of all its deficiencies) and it just misleads and misdirects when you are trying to locate the real reason a build failed. I don't think I have ever come across an occasion in which it was ever "better" then just looking at the first error reported in the Output tab from the build. So in VS2017 the way you switch it off is:

 

 

Because it is so similar, AS7 has an almost identical thing:

 

 

If you value your sanity I would highly recommend you un-tick this !!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Cliff - is that a perpetual setting, or does it have to be redone for every project?

 

Jim

 

Until Black Lives Matter, we do not have "All Lives Matter"!

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It affects all future operation of VS2017/AS7

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks

 

Jim

 

Until Black Lives Matter, we do not have "All Lives Matter"!

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

In my Microchip Studio 7 (Version: 7.0.2542) that checkbox has no effect. No matter what, the "Error list" window is shown, with all deficiencies described. Also, looking for defect reports for the upstream Visual Studio 2015 looks like Microsoft consider this unimportant. Now, at each build with errors/warnings I end up pressing Ctrl + Alt + O, to activate the output window and followd immediately by Ctrl + Home for scrolling at the top of output window. I've even tried to install the Visual Studio 2015 macro extension, for reducing the two shortcuts to just one but the IDE is crashing when trying to record the macro.

 

Is there a better way to either disable/erase the "Error list" window, make is somehow not to steal anymore the focus or, at least, to persuade it show the errors/warnings in the same order as in the Output window? Or do you know any extension which would help or any workaround in regard with this matter?

 

Thanks!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You are absolutely right - I just looked at my newly upgraded MSC7 (which replaces AS7). Made a deliberate build error which led to the Error List being shown. So I thought that, because it was newly updated, the setting must have reverted. But then I go to that project option I found the Error List was already unticked yet the bloody thing is still doing it.

 

This is just one of a number of "odd things" that have been happening here both in the last version of AS7 and now in this replaced MCS7. Oh dear.

Last Edited: Thu. Feb 4, 2021 - 03:11 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ISTR trying that option before, and finding that it made no difference.

 

frown

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The real secret here is after a failed build is to re-compile only the file containing the error. The "Errors View" rarely appears is that case, and the "Output View" is obviously far less verbose. In VS2017 I think ctrl-F7 or similar does that single file re-compile but it is available if you right-clock  the file in "Solution Explorer"

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The "re-compile only the file containing the error" method will be severely limited, especially in case C++ templates are used. Related errors spawn on several files and the order of the errors is very important for correctly assessing the problem.

 

Is there any way to let the gentlemen from Microchip letting know about this issue. On the website, I've found just the regular ticket-based support. Is there any public/account-based bug tracker for Microchip Studio?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Nope support tickets are the way to interact with them.