Yeah, I thought if there's no additional context beyond versioning a date works well (i.e. your `Filter2024` suggestion), as you shouldn't be refactoring multiple times per year, and keeping track of dates is easier than using any versioning system (e.g. if one component didn't get redefined when doing the v2 work, when you refactor again does that component jump straight to v3, or should it be the v2 of that component despite being v3 of the whole / etc).

There are some additional differences; e.g. server includes the ability to use categories (ways of grouping projects) whilst services just has the default category. That said; unless you have a good reason, going cloud is far better (normally I'm not a preacher for SaaS as I like the ability to be able to get into the DB to do reporting/investigations/data fixes where the UI doesn't allow easy access)... You only have a small team, so running up a dedicated server for this product, managing backups, keeping on top of patching, etc will all waste a lot of time and money given you can get all of that for free. You can also integrate it with your AAD or IdP if you want extra security (e.g. to help avoid leavers retaining access to the system) though even without that, it'll probably still be more secure than your on-prem servers unless you're really on top of security. Also - are you using source control today / if so what do you use for that; as there may be offerings that integrate better with your source control system which could better inform answers to your question. If not - that's the more important issue than the software you use to manage work items. Again, generally I don't believe in universal rules; but there's no good justification for not using some form of source control.

:laugh:

My issue with the printer scenario is: :thumbsup: Inkjets are cheaper to buy than laserjets :thumbsup: Inkjets are generally smaller than laserjets That makes inkjets the natural choice for the home user. However, most home users don't print that much / that often. And ink dries out if not used in a while, so even more costly (and it's already more costly than a laserjet to run before this added inefficiency). :doh: So far I've been unable to discover a home printer optimised for the person who prints 5-6 pages once a month, mostly in black & white with the occasional colour logo/image; though I get the impression this is the scenario most home users are in. There are printing services, but that means a trip into town; so the last minute print-out before an assignment's due, or remembering to print off tickets as you're on your way out the door to a gig don't fit well with that solution. :| One idea I had was to create a service that helps you find neighbours with printers, so you can share such resources; i.e. when you need to print it'll find someone within 5 minutes walk of your house who's in, and allow you to print to their printer, charge you for the use, and then you pop round and grab it. That's also more environmentally friendly as it means you don't have a neighbourhood full of unused printers. What do people think?

If it helps, you can find this info on the `SqlStudio.bin` file (under `%AppData%`). Here's some PowerShell to help make sense of the file's content: Get List of Servers from SSMS (i.e. historically used connections list from the New Connection dialogue) · GitHub[^]

Add-Type -Path (Get-Command 'Microsoft.SqlServer.Management.UserSettings.dll').Source
[bool]$loaded = $false
Get-Item -Path 'C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.ConnectionInfo\*\Microsoft.SqlServer.ConnectionInfo.dll' | Select-Object -ExpandProperty FullName | Sort-Object -Descending | ForEach-Object {if (!$loaded ){try {Add-Type -Path $_;Write-Verbose "Successfully loaded $_";$loaded=$true}catch{Write-Warning "Failed to load $_"}}}

[string]$settingsFilePath = (Resolve-Path (Join-Path -Path $env:APPDATA -ChildPath 'Microsoft/SQL Server Management Studio/*/SqlStudio.bin')).Path | Sort-Object -Descending | Select-Object -First 1
if ($settingsFilePath) {
try {
[System.IO.MemoryStream]$ms = [System.IO.File]::ReadAllBytes($settingsFilePath)
[System.Runtime.Serialization.Formatters.Binary.BinaryFormatter]$formatter = New-Object -TypeName 'System.Runtime.Serialization.Formatters.Binary.BinaryFormatter'
[Microsoft.SqlServer.Management.UserSettings.SqlStudio]$sqlStudio = $formatter.Deserialize($ms) #[Microsoft.SqlServer.Management.UserSettings.SettingsDictionary[[System.Guid],[Microsoft.SqlServer.Management.UserSettings.ServerTypeItem]]]
foreach ($serverTypeItem in $sqlStudio.SSMS.ConnectionOptions.ServerTypes.Values) { #[Microsoft.SqlServer.Management.UserSettings.ServerTypeItem]
foreach ($server in $serverTypeItem.Servers) { # [Microsoft.SqlServer.Management.UserSettings.ServerConnectionItem]
([PSCustomObject][Ordered]@{
Instance = $server.Instance
AuthMeth = ([Microsoft.SqlServer.Management.Common.SqlConnectionInfo+AuthenticationMethod]$server.AuthenticationMethod)
Connections = $server.Connections
})

        }
    }
} finally {
    $ms.Dispose()
}

} else {
throw 'Could not find SqlStudio.bin. Older versions used MRU.dat... but I''ve not coded a solution for that, sorry!'
}

The connection settings are held in a di

They've changed how licenses are managed; i.e. if you used to assign licenses via the Volume Licensing Service Center you should now use the VS Manage Portal. An email was sent out to VLSC admins recently; so hopefully someone in your organisation got this? In addition, I believe subscriptions may expire when their parents do; so if you have a VS subscription with 2 years left but the Enterprise Agreement it was purchased under expires today, all those child subscriptions expire early. I'm not sure if this is still the case; happened to us ~8 years ago; though I think it was resolved after various support calls; so not sure whether it was intentional...

(Tangent thread) You could use ⸮

• [⸮]
• Irony punctuation - Wikipedia[^]

I agree that 404 seems wrong in the sense that the service has been found; it's just the data's not there. Taking a quick look on SO it seems 204 is the most popular choice of code for where the service is found, but there's no data: rest - HTTP status code for "no data available" from an external datasource - Stack Overflow[^]. A 200 with empty result set makes sense if you're returning a list in some contexts; e.g. if I want all students attending a course and provide a valid id for the course but there are no students allocated, I'd want an empty list. If the course id was invalid I'd want an HTTP error (probably 204 as per SO link above). If searching for a single item and it's not found, a 204 makes sense (i.e. presumably I'm searching by ID / some unique field as I know that I only expect a single item, so I'm expecting that single item to exist; thus it's an error if it does not).

Generally follow the standards / style guide at your place of work. However, with JavaScript there can be gotchas; due to semicolons being optional, as per this example: javascript - Why does a results vary based on curly brace placement? - Stack Overflow[^] So you have to be cautious that in such cases you use the code that works over the dictated style; and put a comment so no one decides to clean up your formatting not realising that they're introducing a bug. If you're defining a style, I'd say it's best to pick one which avoids this issue, so going with some variant of K&R makes sense for this language, to avoid such pitfalls & any cognitive load related to spotting them. For most other languages (i.e. where placement is solely formatting), I'd typically recommend Allman style for clarity (personal preference); though I may suggest K&R for any projects where the same developers are likely to work with JavaScript; again so they don't have to think about it (i.e. when switching languages). Regarding my personal preference; historically I was a K&R advocate, but later realised that the Allman style allows lining up the open and close brackets, which is more obvious than lining up the code responsible for the bracket. Once you develop the habit of thinking "the line before the open brace is the one defining this block" rather than "the first line of the block defines the block & ends with the opening brace" it pays off. You do use up more screen real estate; but often (at least for developers with large monitors), that's good, since it removes clutter.