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'm betting you launch VS using a profile with CredentialsA, and have to provide CredentialsB for Azure DevOps, and it's getting confused between the two so it has to ask you Every. Single. Time.
One of my VMs with VS used to be set up exactly this way, and it gets really annoying, really fast. Eventually it was changed so it's now set up so I login with the same credentials VS has to provide to DevOps - and it's been pretty quiet ever since.
I do realize however that you might not have the luxury of being able to change your local user profile in that way. In which case I have no good suggestion. Bouncing back and forth between multiple accounts has been the bane of my existence since, well...since operating systems have needed to uniquely identify users. It sucks.
Yep, Although it's worse. I have profile A and profile B. But also Profile C that has the same email address as profile A, but is considered a "work" account. Or a personal account. I can't keep them straight. The "sign in" box comes up and it doesn't tell me which account it wants. I usually just hit profile B since it's easiest, and it stops complaining. For a bit.
I have this too, on Azure, Azure DevOps and Visual Studio (you can sign in with multiple accounts in Visual Studio and use them simultaneously).
Chris Maunder wrote:
But also Profile C that has the same email address as profile A, but is considered a "work" account
This is the problem.
I had that too and Azure DevOps had the same problem.
I somehow got rid of the dual account, which is now 100% personal, and I switched to another email with my work account, and I haven't had problems since.
It's so bad I had to bitch about it in my latest book, Azure DevOps Succinctly.
This is from the part "Creating a Microsoft account":
"Note: Microsoft has really messed up account creation in the past. Personally, I still have an email address that is used for both a personal and a work account and I have no way of seeing in which account I am logged in to. Sometimes I have to switch accounts which is just logging in again with the same email address. To fix this issue, Microsoft has disabled registration with a work or school email address. In practice, this means any email from a domain that is configured in an Azure Active Directory (Azure AD or AAD). So, if you have an email address firstname.lastname@example.org and want to use it at this point, you may be out of luck. No worries though, you can still use it later. You can read more about this issue here: https://mspoweruser.com/microsoft-finally-blocking-users-creating-microsoft-account-work-email-address/."
not sure if it is good place to ask this question: I bought a legacy software running on Windows XP. it comes with 7 disks(installation).
to make a backup, is there a good way to merge these 7 disks into one CD?
During the Windows XP era it was common to implement DRM as physical defects on the media. Literally bad sectors/tracks on the physical media. So maybe you can back it up... if the disks are not protected.
is there a good way to merge these 7 disks
Chris Wu wrote a powershell cmdlet that can easily make an ISO. It uses the Image Mastering API
You do realize that this is the Lounge right? I am drinking a glass of red wine and could not care less about the outcome. powershell files have a PS1 extension. I am not in the mood at the moment to hold your hand. Ask me tomorrow
The responses so far suggest to create ISO files or equivalent of the original floppies, which is going to be a little annoying when installing - mount a file, let it copy, dismount it, mount the next, etc. Although it probably is the method that's the most likely to work.
But it also depends on the installer on those floppies. Some installers will be perfectly happy to keep going if they can find the files it's looking for - if it can't, that's where it pauses everything and asks you to insert the next disk. But I've absolutely seen cases where, if you dump all files from all disks into a single folder then run the installer from there, it'll blast through the installation process without ever stopping, as long as it can find (for example) disk1.cab, disk2.cab, [...] diskN.cab.
That approach won't work however if you have files with identical names but with different content on each disk.
In a case like this, you might be able to get away with creating subfolders (disk1, disk2, [...] diskN) with a raw xcopy dump of the original disk in each corresponding folder (then it won't matter if filenames clash). When the installer is done with disk 1, it'll stop and ask you to provide the path to disk 2, at which point you just have to replace the disk number in the path displayed, and it'll carry on. Still a lot quicker than mounting/dismounting ISOs.
But again, it really depends on the installer. If you don't know your way around a file system, I don't recommend the experiment and would just go with the ISO suggestions.
I suspect this is not gonna work, as changing the content of any file will, well, no longer match what the installer is expecting. You might be able to get away with it (depending on the installer), but I think the odds are stacked against you in this case.
you can look at all your TODOs by going View|Task List in VS2019
Yes, you can. And you might even create tech debt items to track them in your favorite issue/project tracking system. And monitor their presence/growth over time in a nice dashboard. But it's unlikely you'll ever fix them.