[MS] GitHub Copilot Dev Days: Build faster with GitHub Copilot CLI, in Visual Studio, and beyond! - devamazonaws.blogspot.com

GitHub Copilot Dev Days banner image Modern software development is moving fast—and AI is now a practical part of how Microsoft developers design, build, and ship applications every day. From writing code in Visual Studio and VS Code, to building cloud-native apps on Azure, developers are looking for ways to stay productive without sacrificing quality. That’s exactly why GitHub Copilot Dev Days exists. GitHub Copilot Dev Days is a global series of hands-on, in-person, community-led events designed to help developers learn how AI-assisted development fits naturally into the Microsoft developer stack. You’ll see how GitHub Copilot works alongside Visual Studio, VS Code, .NET, and more to streamline real-world workflows—from your first line of code to deployment. [cta-button text="👉 Find a GitHub Copilot Dev Days event near you and register" url="https://ift.tt/7akoBg1" color="btn-primary" align="center"]

Who should attend GitHub Copilot Dev Days?

GitHub Copilot Dev Days is designed for Microsoft developers at every stage, including:
  • Visual Studio and VS Code developers building in .NET, Java, Python, TypeScript, and more
  • Developers working in the CLI and other IDEs wanting to access GitHub Copilot directly from where they're building
  • Professional developers, students, and community members looking to modernize their workflows with AI
If you’re new to AI-assisted development, these events will help you get started using GitHub Copilot effectively inside the tools you already use. If you’re more experienced, you’ll learn advanced techniques to integrate Copilot into larger projects, enterprise codebases, and team workflows. Different events may cover different scenarios - we have content geared towards the GitHub Copilot CLI, GitHub Copilot in VS Code, Visual Studio, and other IDEs, the cloud agent, and more. Check the registration page of the event near you for more information.

What you’ll learn at a GitHub Copilot Dev Day

Each GitHub Copilot Dev Day is hosted by local developer communities—including Microsoft MVPs, GitHub Stars, Microsoft Student Ambassadors, GitHub Campus Ambassadors, Azure Tech Groups, and Microsoft and GitHub employees —and focuses on practical, hands-on learning you can apply immediately. You can expect:
  • Live demos showing GitHub Copilot in action with Visual Studio and VS Code
  • Hands-on workshops using Copilot with .NET, Java, Python, JavaScript, and more
  • Real-world scenarios that reflect how Microsoft developers build apps today
Topics may include:
  • Using GitHub Copilot in Visual Studio to accelerate .NET development
  • Pairing GitHub Copilot with VS Code for cross-platform and cloud-native workflows
  • Leveraging GitHub Copilot CLI and Cloud Agent to support asynchronous development
  • Applying AI-assisted coding patterns to increase your productivity
Each event is tailored by the local organizer, so session topics and agendas may vary. Be sure to check your event’s registration page for details.

A sample event agenda

While every event is unique, a typical GitHub Copilot Dev Day includes:
  • Introductory session (30–45 minutes): How GitHub Copilot fits into the Microsoft developer toolchain
  • Community session (30–45 minutes): A local developer shares real-world experience building with Copilot
  • Hands-on workshop (60 minutes): Guided coding exercises using Copilot in Visual Studio or VS Code
Along the way, you’ll connect with other developers in your area, share ideas, and pick up practical tips you can use right away—plus enjoy some snacks and swag.

Events start soon!

GitHub Copilot Dev Days events begin March 15, 2026, with events happening in cities around the world. Spots are limited, and many events are filling up quickly. 👉 Find a GitHub Copilot Dev Days event near you and register today Interested in hosting a GitHub Copilot Dev Day for your local user group or developer community? 👉 Apply to host an event  
Post Updated on March 2, 2026 at 06:00PM
Thanks for reading
from devamazonaws.blogspot.com

Comments

Post a Comment

Popular posts from this blog

[MS] Pulling a single item from a C++ parameter pack by its index, remarks - devamazonaws.blogspot.com

In my earlier discussion of pulling a single item from a C++ parameter pack by its index , I noted that with the Pack Indexing proposal, you would be able to write this to pull an item from a parameter pack while preserving its reference category. template<int index, typename...Args> void example(Args&&... args) { auto&& arg = (Args...[index]&&)args...[index]; using Arg = Args...[index]&&; } Why did I need to apply the (Args...[index]&&) cast ? Why can't I just write this: auto&& arg = args...[index]; or possibly decltype(auto) arg = args...[index]; Well, when you write the name of a variable, the result is an lvalue reference, even if the variable is an rvalue reference . Watch: struct S { S(S&); // construct from lvalue S(S&&); // construct from rvalue }; void whathappens(S&& s) { S t = s; // which will it use? } Try it out in your favorite compiler. This code construc...
Read more

[MS] Debugger breakpoints are usually implemented by patching the in-memory copy of the code - devamazonaws.blogspot.com

In practice, when you set a code breakpoint in the debugger, the debugger replaces the instruction at that location with a breakpoint instruction.¹ When execution reaches that instruction, it will encounter the breakpoint instruction and break into the debugger. When the program has been stopped in the debugger, what happens next can vary from debugger to debugger. Some debuggers remove all their breakpoints when the program stops, and then restore the breakpoints when the program resumes. Other debuggers leave the breakpoints in place even when the program is stopped. In both cases, if you inspect the memory in the debugger, you will see the original unpatched code. In the first case, it's because the code really is unpatched; the breakpoint instructions are removed. In the second case, it's because the debugger is lying to you and showing you the original bytes even though they aren't what are in memory right now. Most of the time, this deception is insignificant. Eve...
Read more

[MS] The case of the crash when destructing a std::map - devamazonaws.blogspot.com

A customer reported that they were getting crashes while destructing a std::map . Here's the point of the crash: eax=245bd25c ebx=00004d33 ecx=31feece4 edx=00c40000 esi=00000000 edi=31feece4 eip=563397db esp=245bd250 ebp=245bd268 iopl=0 nv up ei ng nz na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010286 contoso!std::_Tree<⟦...⟧>::~_Tree+0x2b: 563397db cmp byte ptr [esi+0Dh],0 ds:002b:0000000d=?? 0:054> k9 ChildEBP RetAddr (Inline) -------- contoso!std::_Tree_val<⟦...⟧>::_Erase_tree [xtree @ 1073] (Inline) -------- contoso!std::_Tree_val<⟦...⟧>::_Erase_head+0x5 [xtree @ 1073] 245bd268 56338313 contoso!std::_Tree<⟦...⟧>::~_Tree+0x2b [xtree @ 1073] 245bd290 56362695 contoso!Contoso::IdCollection::~IdCollection+0x163 245bd2b4 564c8510 contoso!Contoso::LogEntry::~LogEntry+0xd5 245bd2e0 5691a999 contoso!Contoso::LogEntries::Cleanup+0x90 (Inline) -------- con...
Read more