🚀 New Release: gulp-jmkcoder-msbuild v0.2.2 I’m excited to announce the availability of gulp-jmkcoder-msbuild, a modernized Gulp plugin that streamlines MSBuild integration for developers. 🔧 What’s new? Support for the newly released MSBuild 18 Graceful fallback to earlier versions (from 1.0 through 17.0) Simplified configuration — just specify the version, and the plugin resolves the right path automatically Designed for CI/CD pipelines and developer productivity tooling This release continues the mission of making build automation developer-friendly, resilient, and future-proof. Whether you’re working with legacy .NET Framework projects or the latest Visual Studio builds, gulp-jmkcoder-msbuild ensures your workflow stays consistent. 👉 Available now on npm: npm install --save-dev gulp-jmkcoder-msbuild 📖 Learn more: https://lnkd.in/etZ4Ws9e #gulp #gulpmsbuild #msbuild
"gulp-jmkcoder-msbuild v0.2.2: Modern MSBuild Plugin Released"
More Relevant Posts
-
Excited to announce GitForge - my new VS Code extension for better Git workflows After years of using WebStorm and IntelliJ, I always missed their Git tools when working in VS Code. So I built GitForge to bring that same experience to VS Code and Cursor users. What GitForge offers: - Three-way merge conflict resolver with visual side-by-side comparison - Inline git blame with full commit history navigation - Branch management panel similar to JetBrains IDEs - Selective rollback with file filtering and diff preview - One-click operations for merge, push, pull, and fetch Why I built this: VS Code's built-in Git support is good, but it lacks the intuitive visual tools that make complex Git operations simple. GitForge fills that gap by providing a cleaner interface for everyday Git tasks like resolving conflicts, tracking changes, and managing branches. Coming soon: 1. AI-powered conflict resolution using Cursor or custom agents 2. Enhanced diff visualization 3. Team collaboration features 4. The extension is free and open source. I would appreciate any feedback from the community. Install from VS Code Marketplace: https://lnkd.in/e55Za5bm Source code on GitLab: https://lnkd.in/eYGDrv6j
To view or add a comment, sign in
-
🚀 Want a faster, high-quality way to write unit tests and boost your software reliability? Introducing GitHub Copilot Testing for .NET in Visual Studio Insiders — an AI-driven feature that creates unit tests right within your workflow, helping you move from zero coverage to fully validated code in just a few clicks. 🔍 What is it? GitHub Copilot Testing for .NET is purpose-built for generating high-quality tests, understanding your code structure and project setup to create, build, and run tests across any scope—from a single method to your entire solution. 💡 Why use it? It provides scalable AI-generated unit tests, deterministic and type-safe results, multi-framework support, and seamless Visual Studio integration, including automatic test recovery. ⚙️ Getting started Install the latest Visual Studio 2026 Insiders Build, ensure your C# project builds cleanly, enable Copilot Testing under Tools > Options, and make sure you have a GitHub Copilot license. 🎯 How to choose what to test Use @test #target in Copilot Chat to generate tests, where #target can represent a member, class, file, project, solution, or #changes for your Git diff. 📊 What you’ll get You’ll receive a clear summary of created/updated tests, coverage changes, quality indicators, insights into testability gaps, and direct links to the generated test files for quick iteration. Read the blog to find out more! https://lnkd.in/gfcDfrWT #VisualStudio #GitHubCopilot #DotNet #UnitTesting #AIForDevelopers #DeveloperTools #CodingProductivity #SoftwareQuality #Automation #DevCommunity
To view or add a comment, sign in
-
Most .NET teams don’t have a code style problem. They have a missing defaults problem. ⬇️ No .editorconfig. No centralized build rules. No quality gate in CI. I packaged the exact setup I use in real projects into a FREE starter kit: ✅ .editorconfig ✅ Directory.Build.props ✅ CI quality gate ✅ Visual Studio cleanup checklist Copy → paste → commit → done. Get it here (FREE): https://lnkd.in/dUBKZ7tp (This is the foundation of my upcoming course: Pragmatic .NET Code Rules: https://lnkd.in/dCitBN96)
To view or add a comment, sign in
-
-
Most .NET teams don’t have a code style problem. They have a missing defaults problem. ⬇️ No .editorconfig. No centralized build rules. No quality gate in CI. I packaged the exact setup I use in real projects into a FREE starter kit: ✅ .editorconfig ✅ Directory.Build.props ✅ CI quality gate ✅ Visual Studio cleanup checklist Copy → paste → commit → done. Get it here (FREE): https://lnkd.in/dUBKZ7tp (This is the foundation of my upcoming course: Pragmatic .NET Code Rules: https://lnkd.in/dCitBN96)
To view or add a comment, sign in
-
-
🚀 Excited to announce my first Visual Studio Code extension is live on the Marketplace! Introducing “Copy Branch Name Indian” – a simple yet powerful tool for developers who work with Git. 🔹 What does it do? No more manual typing or hunting for branch names! With this extension, you can: ✅ Use the Source Control toolbar button (copy icon) ✅ Run the command from the Command Palette ✅ Or use the shortcut Ctrl+Alt+B 🔹 Why did I build this? As developers, we often need branch names for pull requests, documentation, or CI/CD workflows. This extension saves time and reduces errors. 📥 Get it here: 👉 https://lnkd.in/gcprZK5H 💡 Try it out and let me know your feedback! If you find it useful, please rate it on the Marketplace and share it with your network. #VSCode #Git #DeveloperTools #OpenSource #Productivity #Marketplace
To view or add a comment, sign in
-
I still see many developers hesitant about agentic IDEs like Cursor — and trying to hold on to traditional setups with IntelliJ + AI plugins. But we’re facing a shift similar to the 90s, when we moved from VI/Notepad into fully-fledged IDEs. Back then, the change wasn’t just “adding a tool”; it reinvented how we built software. The same is happening now. Agentic IDEs aren’t just extensions — they’re a new development paradigm. Trying to fit them into old workflows is like trying to use an IDE as a fancy text editor. You miss the point. We’re entering a new world of software development — and our tools, and our mindset, need to change with it
To view or add a comment, sign in
-
-
🚀 Big news for developers using Visual Studio Code! The agent experience in VS Code just got a major upgrade: ✨ Agent sessions integrated into the chat view for a unified experience ✨ Support for isolated background agents powered by Git worktrees ✨ Seamless delegation across agents This update makes collaboration and coding smarter than ever. Check out the full details here: https://msft.it/6044tiQo6 #MVPBuzz
To view or add a comment, sign in
-
I just published PowerLanguage for MultiCharts, a VS Code extension that brings modern editor support to PowerLanguage and EasyLanguage developers. Features: * Syntax highlighting for .pla, .ela, and .easylanguage files * 20+ code snippets for indicators, strategies, and common patterns * Bracket matching and auto-closing * Code folding for begin/end blocks * Comment toggling support If you develop trading strategies or indicators in MultiCharts or TradeStation, this extension makes writing code in VS Code a much better experience. Free and open source on GitHub. 🔗 https://lnkd.in/dwsmkMwh #VSCode #Trading #AlgorithmicTrading #MultiCharts #TradeStation #OpenSource #Developer #FinTech
To view or add a comment, sign in
-
🎉 Introducing key-cooker — A New VS Code Extension for Developers I’m excited to share that I’ve just released my new Visual Studio Code extension: key-cooker! This tool helps developers work more efficiently with key-value property objects across JSON, YAML, JavaScript objects, and TypeScript types. ✨ Why key-cooker? Because sometimes you just want the exact key path—quickly. With key-cooker, you can copy the full key path simply by selecting or focusing on the key. No more manual tracing or mistakes. 🔗 Try it out here: https://lnkd.in/dQduUTv6 I’d love to hear your thoughts, feedback, or any suggestions to make it better 🙏 #VSCode #DeveloperExperience #DevTools #Productivity #OpenSource #SoftwareDevelopment #Coding
To view or add a comment, sign in
-
When you use Visual Studio Code to create your things try to have 3 markdown file docs for you and github copilot to reference to make your lives easier. Usually you will have something like: ProjectOverview.md (This is what your program is supposed to do and what it can do) CLIOverview.md (Command list if applicable) DirectoryArchitecture.md (Your directory architecture) Pick one model (Grok Code Fast 1 or Claude Opus are usually peak) and stick to it. Or you can make things even easier and literally just feed those 3 files in a project workspace like a normal person. Then you would also create a README, and any main files in the project as well. Establish the foundation and the backbone of it all first before working on anything. Master this, apply it to everything, and then everything becomes plug and play.
To view or add a comment, sign in
