Rafeeq on .NET

We talk a lot about AI assistants like Google Assistant or chatbots answering our questions. They're pretty smart on their own, right? But imagine if they could team up, combine their unique skills, and tackle really complex problems together, just like a human team does. That's the core idea behind a super exciting area Google and others in the AI world are exploring: Agent-to-Agent (A2A) communication and collaboration. Think of it less as a single product called "Agent2Agent" and more as the science and engineering of building AI teams. Ready to explore why this is such a big deal? Let's break it down! First Off: What Even is an AI Agent? Think of an AI agent as a specialized digital helper. It's a piece of software designed to: Perceive: Understand its environment (text, images, data, user requests). Reason: Figure out the best course of action based on its goals and knowledge. Act: Perform tasks (answer questions, writ...

 Imagine the world of Artificial Intelligence is like building with LEGOs. You have different kinds of LEGO bricks, each with its own special job. Agentic AI, MCP Servers, and Vertical Agents are like three really interesting types of these bricks. Let's take a closer look at each one in a way that anyone can understand. Agentic AI: The Smart, Independent Helper Think of Agentic AI as a really smart robot assistant that can figure things out on its own. Instead of you telling it every single step to take, you give it a goal, and it figures out how to get there. It's like giving your super-capable friend a task – they'll look around, make a plan, and get it done without you constantly looking over their shoulder. Imagine this: You ask your Agentic AI to plan a surprise birthday party for another friend. This AI wouldn't just set a reminder. It would: Look around: Check your friend's calendar, social media for clues, and maybe even ask other friends. ...

The AI revolution is no longer coming—it's here. In 2025, AI-powered developer assistants are transforming how we write code, debug, test, and even design software. Whether you’re a solo developer, part of a startup, or working in a large enterprise, these tools have become indispensable. From real-time pair programming to secure code generation and AI-driven documentation, here’s the definitive list of 20+ must-know AI assistants that are reshaping the developer experience. 🧠 1. GitHub Copilot X 🔹 Best for: AI pair programming, test generation, and code explanations 🔹 Why it’s hot in 2025: Now integrated with GPT-4 Turbo and deeply embedded into GitHub workflows. Copilot X doesn’t just autocomplete—it reviews PRs , writes unit tests , explains code in plain English, and even offers voice command support via Copilot Chat. 🔗 GitHub Copilot X ☁️ 2. Amazon Q Developer 🔹 Best for: Cloud-native devs, AWS integration 🔹 2025 upgrade: Auto-compl...

Introduction In the rapidly evolving field of artificial intelligence, efficient communication between AI models and applications has become increasingly critical. The Model Context Protocol (MCP) and MCP Servers represent a significant advancement in how AI systems interact with data and services. This blog post breaks down what MCP Server is, how it works, and why it matters for modern AI applications. What is Model Context Protocol (MCP)? Model Context Protocol (MCP) is a standardized communication framework designed specifically for AI model interactions. It defines how AI models receive input data, process information, and return results in a consistent, structured manner. Think of MCP as the "language" that allows AI systems to effectively communicate with applications, databases, and other services. What is an MCP Server? An MCP Server acts as the central coordination point in an AI system architecture that implements the Model Context Protocol...

In DD4T the 404 page can be retrieved as below, Override the Action Page, and when the Page is null return the NotFound Action. In the NotFound action, Query the Broker for the 404  page and return the view. The 500 Error page can be throw from the Global level as below, when error occurred handle it the global level and return just view with error information

ASP.NET routing enables us to use URLs that are not physical files, In DD4T we have the default page route definition. In which all page request redirct to Page controller and process the page. DD4TFormRouteHandler is a custom route handler responsible for mapping incoming browser requests to particular MVC controller actions, this works along with  DD4TFormHelper  (that generate the route information for the form) Posting a form in DD4T is not complicated, you can create the mvc form as a normal controller and action, then post it via AJAX. But, when we need to do post the form as normal page, It would need a tweak as the controller/action is not a page existed in tridion. This can be achieved by implementing a custom Mvc RoutHandler and reroute the posted form to the encrypted action and controller. It works as below daigram. So, how to do this. to render out the form we have BeginDD4TForm html helper as below that generate the form with encrypted route values....

When it comes with DD4T we have plenty of control on the data and we can decided on how we wanted the page to be rendered. The traditional approach of having difference size of same image is replaced in DD4T to have one single image and generate the thumbnail on the fly. In this approach, we will have only one image published in tridion, and rest will be created on the fly based on the request. Just by adding below configuration on the web.config modules session will enable this feature <modules runAllManagedModulesForAllRequests="true">   <add name="BinaryModule"         type="DD4T.Web.Binaries.BinaryDistributionModule" />  </modules> The BinaryDistributionModule process the request as below Process the Binary Request Check if the file is already in the file system. If file is available compare the last published date of the binary against the broker. If the file is updated, update the existing file in the file system....

Sometime when we work with Component presentation, we might come up with the scenario to have customized RenderComponentPresentation, when we deal with Area/View or splitting view into more organized structure. We can fetch and send the area from the Template. Currently DD4T doesn’t allow injecting the ComponentPresentationRenderer, instead it allows us to write our own renderer and call it along with RenderComponentPresentation as below The custom ComponentPresenationRenderer can be created based on the scenario, so when we use the area, we could have the custom ComponentPresentation as below SDL Reference implementation, customized Renderer beautifully and implemented the Renderor to use Area view concept.

There always been a question on What is the best approach for building navigation with DD4T and ASP.NET MVC? Answer is: There is TridionSiteMapProvider as part of the DD4T.Mvc project, which can be used out of the box. The  DD4T.Examples.Templates project also have a example on how Sitemap can be generated from the template ( TBB ) Many organization will have different kinds of navigation structure, It can be from very simple structure or it can be a heavily complex in nature. In this article you can see how the default SitemapProvider can be used and how we could customize to achieve complex Navigations like Megamenu or similar using TridionSiteMapProvider. Setting up the default TridionSiteMapProvider The only configuration you would need to do in web.config is set the your default sitemap provider is as below. <system.web> <siteMap defaultProvider= "TridionSiteMapProvider" enabled= "true" > <providers> <clear/> ...

Well, It's the high time to think about DD4T. What is DD4T? What makes more easier to the developer and Editor to talk about DD4T.!!  DD4T is a framework that developed by Tridion veterans. The framework makes it easier for Tridion developers to develop, deploy and maintain a project. The basic building blocks of Tridion  like, schema, components, template etc. are still remain the same as below. So what changes, if you look at the below diagram, you could see the different between both So, the whole logic goes to the web server, CMS just plays the role of generating the pages and delivering it to the Broker, no Template logic or HTML in CMS any more. DD4T solves the problem by making sure the pages and content are published to the broker as data, without any HTML rendering. If we summarize the diagram. 1) The role of editor and visitor are normal, and that is the main aspect of DD4T architecture. 2) Everything is published to the broker database. ...

DD4T is a great framework which would give you everything in place what you basically needed. Here we will see how we could resolve the publication based on the URL,  when we work with multiple publications accessing same web site, our DD4T would need to query dynamically to different publications. Many times it can be based on URL, based on the domain or language we could resolve the publication. It’s obviously up to us how we implement it. By default the DD4T framework queries the publication that we have mapped in the key: <add key="DD4T.PublicationId" value="7" /> or keep it 0 to query all publications We can make it dynamic simply by implementing the IPublicationResolver class Step 1: To resolve publication dynamically, we can write a class that implement DD4T.ContentModel.Contracts.Resolvers.IPublicationResolver namespace Indivirtual.DD4T.Mvc.Resolver { public class SitePublicationResolver : IPublicationResolver { ...