The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I am currently in the process of setting up Azure DevOps for the first time, which will be self hosted on one of our dev servers. (I have never used TFS before either... well, aside from a failed attempt in setting it up a few years back).
Any of you lot have any experience with it? Particular any obvious "gotchas" that I am likely to hit that you could pre-warn me about?
Currently we use Mercurial for source code, so that will be a conversion job over to Git at some point.
Thanks in advance for any advice. I also welcome your input if you just want to laugh at my impending doom.
If project and team is small and server must be in-house, you can consider Azure DevOps Express. Free for 5 member teams and runs on single machine. However, hosted Azure DevOps would be my choice. When you consider hardware, configuration, maintenance, updates , backups , TCO is cheap.
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.
Ok so I've registered my net core API and a client app with Azure AD, I now have lot's of keys and ids that I need to access my API from the client. All is working as expected. I can't help thinking I've created another problem. I need to put these keys somewhere accessible but secure. Any recommendations?
"We can't stop here - this is bat country" - Hunter S Thompson - RIP