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.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions. Or if you must, use the Back Room[^] - but enter at your own risk.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen. For those discussions where you wish to be a little more frank, use the Soapbox[^]
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
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
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.
Last night, my son was taking an online test for a summer college course (on his Win10 machine) when his machine suddenly rebooted.
The machine finally came back up and the disk I/O was at 100%.
He couldn't do anything.
Microsoft antimalware exe was going crazy. He has Norton AV also so he doesn't have a (known) virus.
We tried to kill everything -- just to get back into the test which is timed. The 100% I/O persisted as we killed tasks but you can't really kill the antimalware exe which was eating up I/O like crazy.
We will simply have to upgrade him to an SSD now too.
Such a crazy h/w upgrade path that Microsoft seems to be enforcing.
I've had MS anti-malware process running for a few days now, sucking up 30% of my CPU. And that's with SSD's. When I try to kill the process, I get "access denied."
Followed the instructions here and rebooted, which fixed it, then Windows Imaging something or other fired up and started consuming 10% of the CPU, but fortunately was able to kill that. This stuff is ridiculous.[/edit]
I thought the same thing, but the built-in antimalware on Win10 cannot be removed that I know of.
Normally, the Norton install and the OS takes care of that.
If you check out my article, you will see that there is definitely seems to be something up with Win10.
Thanks for the input.
Removed, probably not, but it should the smarts to disable itself when it sees you're installing an alternative AV. Or rather, Norton should be registering itself as an AV so Defender should disable itself.
Try removing Norton, then reinstalling it. I'd say something didn't get triggered properly the first time around, and Defender is too dumb to realize it.
Last Visit: 31-Dec-99 18:00 Last Update: 22-Jun-17 4:54