Yep, don’t spend any time on it – we’ll figure it out. From: [email protected] [mailto:[email protected]] On Behalf Of Eddie de Bear (Gmail) Sent: Wednesday, August 12, 2015 10:24 PM To: 'ozDotNet' <[email protected]> Subject: RE: Visual Studio 2015 complaints
I have several other solutions, similar size that don’t have the same issues. The only things that stand out with this solution are: · Targeting .Net 4.0 instead of 4.5 or later · Reports As for stripping out the reports, or reproducing this issue, it’s not something I have a great deal of time to do at the moment ☹. When I need to work on that solution, I just keep an eye on the memory situation and restart VS as required.. It’s the low tech solution ☺ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of DotNet Dude Sent: Thursday, 13 August 2015 3:19 PM To: ozDotNet <[email protected]<mailto:[email protected]>> Subject: Re: Visual Studio 2015 complaints I'd remove anything you think may be the cause like the reports (or most of them at least) and see how that goes. Probably not it but waiting around for a fix may take a while. Also do you have issues with any other solutions? How about a default template with almost nothing in it? On Thu, Aug 13, 2015 at 3:02 PM, Eddie de Bear (Gmail) <[email protected]<mailto:[email protected]>> wrote: That was my first thought, so I stripped out all VS extensions etc. Besides that, the solutions is what I’d call plain, no third party anything (I was using stylecop as a compilation target, but removed that as well). Probably the only not so standard thing left in the solution is a bucket load of reports (local reports *.rdlc), but besides that, it’s C#, Xaml and Sql Client. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of DotNet Dude Sent: Thursday, 13 August 2015 2:54 PM To: ozDotNet <[email protected]<mailto:[email protected]>> Subject: Re: Visual Studio 2015 complaints Any 3rd party components in the solution? I had similar issues with VS 2010 and it was something in a 3rd party control suite if I recall correctly. Seemed random at first but wasn't On Thu, Aug 13, 2015 at 2:49 PM, Eddie de Bear (Gmail) <[email protected]<mailto:[email protected]>> wrote: I’ve lodged a bug through connect about VS2015.. Basically, VS is crashing when it runs out of memory (it’s a 32 bit app, and its crashing when it hits a little over 2.3gb of RAM).. Yep, that’s right, a single instance of VS 2015 using 2.3gb or RAM. The particular solution I’m having issues with is a WPF app with a bit over 250k lines of code. ** Just as a side note, VS 2013 used around 500MB for this same solution *** I’m not having any other issues with other solutions **** The 2.3GB is used within about an hour of serious work. That’s a lot of crashes each day.. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of David Kean Sent: Thursday, 13 August 2015 2:41 PM To: ozDotNet <[email protected]<mailto:[email protected]>> Subject: RE: Visual Studio 2015 complaints Thanks Greg. First is known and something we’re aware of, it will be fixed in the next VS Update. Second I’ve not heard, can you use the Send-A-Frown, we’re looking at these daily and this will get routed to the right team. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Wednesday, August 12, 2015 9:33 PM To: ozDotNet <[email protected]<mailto:[email protected]>> Subject: Visual Studio 2015 complaints • It seems to be well known around the web that if you have the VS2015 options so C# Text Editor has "Keep Tabs" then F12 (go to definition) and Alt+F12 (peek definition) don't work. This may sound utterly absurd but it's true (it's like a link between slamming my car door causing it to rain). Unfortunately for me, I've had "Keep Tabs" on since it was invented. • In VS2013 I could Ctlr+Wheel to change the font size of individual windows. In VS2015 the font size of all open windows seems to be ganged together. This is also crippling me due to having two monitors of different resolutions. These two seemingly small issues about F12 and font sizing are driving me barking mad during the whole of my working day. If anyone has any insights or tricks about these issues I'd really like to hear from you. In the meantime I'll keep searching, but nothing useful so far. Greg K
