Hi there: I have to debug two branches of the same codebase side-by-side (a development branch vs a release branch), as we're seeing unexplained differences in behaviour between them. I've opened two copies of VS 2019 (latest patch v18.6.3 at 16th Dec 2020), and when launching them, one will succeed, and the other will throw up an error message:

One or more errors occurred.
Failed to launch the debug adapter. Additional information be be available in the output window.
Cannot connect to runtime process, timeout after 10000 ms - (reason: Cannot connect to the target: connect ECONNREFUSED 127.0.0.1:4318).

What I've tried: - Making sure that each web project is set to start on a unique port number, I've selected 53199 for one branch and 53200 for another. - Delete the applicationhost.config inside .vs, restart VS and let it recreate. What I've noticed: - The two Visual Studios try to launch as tabs in the SAME Chrome instance. I loaded a random different project from another codebase and that project launched its own new Chrome instance. - Inside each applicationhost.config, in the section, BOTH projects have:

- Their site "id" is the same, but each config file does have the correct virtualdirectorypath for its project location. - this is new behaviour (maybe a new bug?) and I've been able to run this configuration plenty of times in the past. - the output window contains only this: Verbose logs are written to: C:\Users\Bar\AppData\Local\Temp\visualstudio-js-debugger.txt The program '' has exited with code -1 (0xffffffff). The program '[21072] iisexpress.exe' has exited with code 0 (0x0). - as each site starts up, the visual studio debugger log shows a --remote-debugging-port which is unique for each site, so no conflict there... Since we're using TFS version control, "two branches" in this context means two completely different folders on disk, each with a full copy of the project source inside. I cannot see why these projects interfere with each other. Each one launches into debug successfully on its own and then the other won't launch. Can I "fool" VS / IIS Express by manually changing the site "id" or "name" in applicationhost.config? Any help gratefully appreciated! -- edit: there are workarounds, e.g. using two different browsers, but still would like to clarify whether it's me or VS or IIS express causing this, and whether it can be fixed!

An additional "Good Luck" from me too. I'm now 7 weeks into my 12-week notice period, counting the days (just 25 left) until I'm free of "workin' fer the man". Both my fiancee and I have decided it's time to start up a business for ourselves, and will be offering web/applications development and support into the property management / conveyancing industry (initially just local) with ad-hoc consultancy where we can get it. To keep the boat afloat we're also going to offer small-office/home-office setup and support in the form of network/infrastructure, VOIP, server admin, desktop installation and optionally PAT testing to those same local businesses (and as many others as we can get!) It's all going to be very small scale (read: low income) compared to app development in the financial sector, but I want to look back on it in 20-30 years and say "win or lose, I gave it a shot"... Maybe it's the mid-life crisis doing all the thinking here :wtf:

Entire degree useless :) Did Electronic + Electrical engineering. Got corporate sponsorshop from a power cable manufacturing company. Pretty much from day 1 after graduation and into employment, found myself working on Access databases and VB 4 -> 5 -> 6 applications for the company's statistical process control (manufacture -> test -> feedback loop). 2 years in and went into dedicated software development (might as well get paid for it eh?) haven't applied knowledge of electrical power systems since.....

I found almost this exact code in the splashscreen of an app I inherited responsibility for.... "The app takes too long to start" was the complaint from the customer. In fact the splashscreen sat there burning up CPU cycles as fast as possible performing "sw.Elapsed.TotalMilliseconds < 10000". Then once the 10 seconds had elapsed it closed the splashscreen and *then* started all the application init tasks (DB connection, load config etc...) I replaced the stopwatch with: - a background thread to perform the app init (which normally took about 7 seconds) - a thead.sleep to "pad" the splashscreen's lifespan up to 10 seconds Apparently a 10-second splashscreen was desired, but cramming the app init into that 10 seconds cured the customer's "slow app" nicely.

Congrats! Posts like this remind me that "the beast" is languishing in a garage and hasn't seen the road in 2 years except for the annual 10-miler to the MOT station and back. Time to buy some tax!

Source article: ASP.NET WEB API Custom Authorize and Exception Handling Attributes[^] Abusive comment: Abusive comment from member 12437293[^]

I've had the opportunity over the past year to interview about 20 candidates for .NET development positions. First up take somebody else in with you, preferably with some overlapping, and some complementary skills. Between you, you should be able to test the candidate on a range of things, and two opinions are better than one when discussing the candidate's merits afterwards. Have a bank of technical questions on hand but *don't rely exclusively on them*. Candidates can spot when you're just reading off a list - it's probably the same list as they might have researched before coming to the interview. That said, we do like this list: Scott Hanselman's blog: What Great .NET Developers Ought To Know We generally try to structure an hour as follows: 5-10 mins talk to the candidate about the business, the role etc. 15-20 mins general chat about their previous roles, throwing technical questions of relevance from both from the bank, and from your own thoughts/experiences of the areas under discussion. Personalise some of the questions e.g. "ah, we had a similar problem with XYZ - how would you have gotten around that? 15-20 mins a larger question i.e. a system design, technical problem to discuss. Watch the candidate think their way around something larger. Provide paper + pens for ad-hoc diagrams. 5-10 mins any questions from the candidate - let them ask you about the work environment, projects ongoing (in particular their future) Let H.R. schedule their own extra 30 minutes before or after, get your full hour's worth! You'll find as you conduct more interviews, your ability to shoot a relevant technical question at the candidate in context of an ongoing conversation improves and you'll need the bank less and less. If it's going like an informal chat but with lots of opportunity to throw a question, then it's going okay. Don't let the candidate suffer in silence. If they don't know an answer, it may be nerves or it may be lack of knowledge, either way drop to a simpler question on the same topic - you're testing whether the candidate has oversold him/herself on that topic, but you want to find the level to decide on whether you would choose to bring the candidate on in that skill area once they're onboard (training, mentoring or pair programming etc). p.s. the above are only my opinions! You may work for/with someone who wants to give strict time limits, hard questions, lots of formality,