The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
There is an option to only show 1 line per contact, instead of 2.
Yes, I've done that. It's still too big. I often have to scroll the list of just 20 people to select someone. That's annoying.
Single-click opens the menu options
That should be a context click. A single click should restore the window. Many IMs work that way.
When we first started using it I had to turn that on per contact.
Yes, I've done that manually for each contact. I hope it sticks. And yes, it is a group policy that I don't have privs to change. There's a Powershell cmdlet that will let you alter that, but it fails for me.
This does not happen to me when I set to Away, but does when I am set to Be Right Back.
Or an oncoming train? Well as most regulars will know I am 'resting' at the moment trying to get a new role had two interviews this week Monday & Tuesday, the Monday one was not a goer. The Tuesday one (bit of a long commute) but the guy who interview me had a couple of manuals I had written off me to show the managment, seemed over joyed I had worked on automated test systems and had an understanding of serial comms...then things went side ways again my Dad (who lets get over it is a senior citizen, one of the WW2 generation, narrowly missed D-Day, did Suez and Egypt) is not too well, it appears to me that a small stroke might have happened. Doctors on the way to see him, Mum going nuts,sorry about the long rant just needed somewhere to moan!
Best wishes to your father, my old man had a mild (if there is such a thing) stroke last year, fortunately he was near a hospital at the time and received prompt treatment he's now 95% recovered, so there is hope. Also, good luck on the job prospect!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
I've only just recently started using Newtonsoft for JSON. I assumed there was probably another way to get it besides NuGet, but I haven't had the time to research alternatives. Can you take a moment to describe your workflow in this regard?
Recently though, I'm keep getting stuffed by conflicts, bugs and wierdities.
Recently? I've never had NuGet behave properly. And that BS about changing something in some config file to override the version number, well, it's just that, BS.
If I can, I compile the source directly and add to my project the necessary DLL's. This is often fraught with problems, as people can't seem to provide source code that actually compiles, or doesn't compile with the .NET framework that I'm using, or doesn't provide a SLN file, or has all sorts of project kruft that I don't need or care about.
Failing #1 (happens often enough) I create a separate project, do the PM NuGet BS, grab the DLL's from the appropriate .NET version folders, put them in a "Libs" folder that my real project then references, and delete the temporary project.
And the very elephanting last thing I need/want is for some package to update itself, breaking code, breaking other dependencies, etc.
One problem with NuGet is Visual Studio itself. It assumes you will organize everything at the solution level, so if you're working with a code base with multiple solutions, there are package folders littered everywhere!
Then there are out and out bugs in MSVS. Try centralizing your downloaded packages into one package folder and it all starts going south...
Anyway I've done pretty much what Marc describes above.
I create a ThirdParty solution that I use to download all NuGet packages I want to use. They all get downloaded into the ThirdParty solution's package folder, where literally everything in the package folder gets put into source control.
This pattern allows me to download and keep multiple versions of the same NuGet package so that legacy applications are able to use an older version if, for some reason, it is withdrawn.
From there, any other solutions that want to use a NuGet package will simply use a file reference for the dll directly from the ThirdParty package folder.
Source code from other vendors are included as projects to the ThirdParty solution and again those libraries can be referenced from a solution as a file reference.