@DamianEdwards Allow Microsoft C# extensions in Cursor IDE so I can use FBA's. I realize this is more-so a cursor problem, but Microsoft did specificially add in the extension logic to disable not only the debugger aspect (which I get), but language features too...
@jacobbundgaard@DamianEdwards Technically already somewhat possible natively (see link below), but certainly would like cleaner native support for dotnet inline FBA!
https://t.co/TRaqjjfSDg
@LinusEkenstam Needs an indicator of possession. These teams would voluntarily send the ball back to their half quite frequently. So visual misrepresented a teams advance at times.
@RaulJuncoV Same conclusion I made. Requestly was the only one I found that supported collection runners w/o requiring a sign-in or subscription. And it appears to be in active development, so I'd bet any of the rough edges will be polished real soon.
@awakecoding any open software engineering roles at Devolutions? I'm a .NET developer and have heavily used RDM in my day-to-day. Love the product and would love to join the team!
@awakecoding In case its helpful, Here's a deep dive I did a while back of Windows sandbox internals, albeit its a bit outdated probably.
https://t.co/Ep4QiAXm0t
@WindowsCentral Dont think this is an accurate report of current events. The recent security incident was at the hosting provider end, not a github hijacking AFAIK...
https://t.co/8I6ymO5ImP
@brankopetric00 Explore containerization. Establish versioning best practices and automatic testing. Bump db/svr bkp frequency. Standardize tech stack and tooling. Etc...
All of this requires substantial team and management buy-in, and likely significant team size additions.
@brankopetric00 Using legacy tech stacks, source control, and outdated packaging tooling... The fix? A whole lot of patience. Focus on critical paths and iterate. Collocate all severs (on-prem/cloud). Establish a form of CI/CD. Install deployment agents on servers. Use proxies effectively.
@chux13786509 U said bug, but not specifically vulnerabilty, so looking more generally: line 43 & 49 dont have return, so client never receives valid token (or exception). Not familiar with the environment, so maybe thats not necessary to do? π€·ββοΈ