🧹 How to Remove SSR (Server Side Rendering) from an Angular 19 Project

Sometimes you add Angular SSR using @angular/ssr, but later want to return to a clean client-side app. Here's how to fully remove SSR (Server-Side Rendering) from your Angular project. 🔥 Step 1: Delete SSR Files Remove these files from the src/ folder: main.server.ts app.server.module.ts server.ts Any .server.ts files like: app.routes.server.ts app.config.server.ts 🛠️ Step 2: Update angular.json Inside "architect > build > options", remove the following: "server": "src/main.server.ts", "outputMode": "server", "ssr": { "entry": "src/server.ts" } Also remove the entire "server" block from angular.json if it exists. 🧾 Step 3: Clean Up TypeScript Config ❌ Delete: tsconfig.server.json ✅ Edit tsconfig.app.json like this: { "extends": "./tsconfig.json", "compilerOptions": { "outDir": "./out-tsc/app", "types": [] }, "files": [], "include": ["src/**/*.ts"] } 🧹 Step 4: Uninstall SSR Dependencies 🖥️ Run in Terminal / PowerShell / CMD: npm uninstall @angular/platform-server @nguniversal/express-engine express 🚀 Step 5: Clean & Serve PowerShell (Windows): Remove-Item -Recurse -Force node_modules, dist, .angular npm install ng serve Mac/Linux terminal: rm -rf node_modules dist .angular npm install ng serve ✅ Done! Your Angular app is now SSR-free and runs entirely with Client-Side Rendering (CSR) — faster dev, fewer headaches!

🚀 How to Copy a SQL Server Database Using a .bacpac File (Schema + Data) || Clone DB

#Clone Database 
Need to duplicate a full SQL Server database — including tables, views, stored procedures and data — without writing complex scripts?

Let me show you a simple, reliable method: Exporting and Importing a Data-tier Application (.bacpac). It’s perfect for backups, migrations, and creating dev/test clones.

---

 Step 1: Export the Source Database

1. Open SQL Server Management Studio (SSMS).

2. Right-click your source database → Tasks → Export Data-tier Application.

3. Choose "Save to local disk", then pick a file path and name (YourDatabase.bacpac).

4. Click Next through the wizard and generate the .bacpac file.

---

 Step 2: Import into Target Server

1. In SSMS, right-click Databases → Import Data-tier Application.

2. Select the .bacpac file you exported.

3. Give the new database a name.

4. Complete the wizard. 🎉 Done!

---

🧩 Diagram

[ Source DB ]
     |
     |  Export as .bacpac
     ↓
[ YourFile.bacpac ]
     |
     |  Import on Target Server
     ↓
[ New DB Clone ]

 Why Use This?
🔄 Migrate databases between environments (dev, staging, prod).
🛠️ Create dev/test clones without risking production.
📦 Archive snapshots with both schema and data.

Run ai model in python code with ollama

 First download and install ollama By this blog:
Tech Journey With Gagan: Run Any AI Model with ollama in windows

For Use AI model in python:
1. run this script
Note: this example for mistral ai model please change acording to your model

Declare function

import requests def ai_generate(prompt): response = requests.post('http://localhost:11434/api/generate', json={ 'model': 'mistral', 'prompt': prompt, 'stream': False }) return response.json().get('response', 'Error: No response from AI.')

For run

print(ai_generate("hello"))

it is work like this

Option 2: 

Run server explicitly 

1. Click on Quit Ollama

2. run server with ollama serve mean in cmd type "ollama serve".

Run Any AI Model with ollama in windows

Steps for install Any model with ollama in local : 
1. Download Olama  and install 

2.  open cmd and run "ollama" command to verify that ollama installed or not.

3. Install models  
    a. find your model and click on it.

   b. copy command and paste into terminal

                      press Enter now your model installed 

Note :Later on same command run your model will run automatically this time it is not downloading it just run 

How To work python with ollama: Run AI Model with Python

😮Create Task Scheduler app using AI Agent in just before 2 min 😮

Steps to create :
1. use Cline Agent extention in vs code.
2. use api of AI models like.
3. Give prompt to Cline.
4. Work automatically give you clean app.
Note: No need to create any file it will do automatically.

📌 GitHub Repository Viewer

Loading...

Git Hub Repo Link Here

Building a C# Web API with Onion Architecture, CQRS, MediatR & Quartz.NET CRON Jobs

 

Introduction

In modern C# applications, clean architecture plays a crucial role in maintaining scalability and maintainability. In this blog, we will build a C# Web API using Onion Architecture, CQRS, MediatR, and Quartz.NET for scheduling background jobs. This guide will walk you through structuring a project with best practices and SOLID principles.

Why Use Onion Architecture?

Onion Architecture provides a clear separation of concerns by organizing the application into different layers:

1. Domain Layer → Contains core business logic and entities

2. Application Layer → Contains CQRS commands, queries, and interfaces

3. Infrastructure Layer → Handles database, repository pattern, and external integrations

4. Presentation Layer (API Layer) → Exposes the application as an API

Tech Stack

• ASP.NET Core Web API for building RESTful APIs

• Entity Framework Core for database operations

• CQRS Pattern for separating read & write operations

• MediatR for in-memory messaging

• Quartz.NET for CRON Job scheduling

• SOLID Principles to make the application scalable
  
  

  📌 Project Structure

  Your project will be structured as follows:
  
  

  Architecture Snippet

  Solution 'OnionArchitectureCQRS' │── Onion.Application (Application Layer) │ ├── Features/ │ │ ├── Students/ │ │ │ ├── Commands/ │ │ │ │ ├── CreateStudentCommand.cs │ │ │ ├── Queries/ │ │ │ │ ├── GetAllStudentsQuery.cs │ │ │ ├── Handlers/ │ │ │ │ ├── CreateStudentCommandHandler.cs │ │ │ │ ├── GetAllStudentsQueryHandler.cs │ ├── Interfaces/ │ │ ├── IStudentRepository.cs │── Onion.Domain (Domain Layer) │ ├── Models/ │ │ ├── Student.cs │── Onion.Infrastructure (Infrastructure Layer) │ ├── Repositories/ │ │ ├── StudentRepository.cs │ ├── Scheduler/ │ │ ├── CronJobService.cs │── Onion.API (Presentation Layer - Web API) │ ├── Controllers/ │ │ ├── StudentsController.cs │ ├── Program.cs
  Step 1: Create the Student Model (Domain Layer)

  📍 Location: Onion.Domain/Models/Student.cs


  Model Snippet

  public class Student { public int Id { get; set; } public string Name { get; set; } public string Description { get; set; } public DateTime CreatedOn { get; set; } }
  Step 2: Create CQRS Commands & Queries (Application Layer)

  ✅ Command to Create a Student

  📍 Location: Onion.Application/Features/Students/Commands/CreateStudentCommand.cs


  Code Snippet

  using MediatR; public class CreateStudentCommand : IRequest<int> { public string Name { get; set; } public string Description { get; set; } }
  ✅ Query to Get All Students

  📍 Location: Onion.Application/Features/Students/Queries/GetAllStudentsQuery.cs



  Code Snippet

  using Onion.Domain.Models; using MediatR; using System.Collections.Generic; public class GetAllStudentsQuery : IRequest<List<Student>> { }

  Step 3: Implement Repository (Infrastructure Layer)

  📍 Location: Onion.Infrastructure/Repositories/StudentRepository.cs


  Code Snippet

  using Onion.Domain.Models; using Microsoft.EntityFrameworkCore; using System.Collections.Generic; using System.Threading.Tasks; public class StudentRepository : IStudentRepository { private readonly AppDbContext _context; public StudentRepository(AppDbContext context) { _context = context; } public async Task<int> AddStudentAsync(Student student) { _context.Students.Add(student); await _context.SaveChangesAsync(); return student.Id; } }
  Step 4: Implement CRON Job Using Quartz.NET

  📍 Location: Onion.Infrastructure/Scheduler/CronJobService.cs


  Code Snippet

  using Quartz; using System; using System.Threading; using System.Threading.Tasks; public class CronJobService : IHostedService { private readonly IScheduler _scheduler; public CronJobService(IScheduler scheduler) { _scheduler = scheduler; } public async Task StartAsync(CancellationToken cancellationToken) { await _scheduler.Start(); var job = JobBuilder.Create<AddStudentsJob>() .WithIdentity("AddStudentsJob") .Build(); var trigger = TriggerBuilder.Create() .WithIdentity("AddStudentsTrigger") .WithCronSchedule("*/30 * * * * ?") // ✅ Every 30 seconds .Build(); await _scheduler.ScheduleJob(job, trigger); } public async Task StopAsync(CancellationToken cancellationToken) { if (_scheduler != null) { await _scheduler.Shutdown(); } } }
  Step 5: Register Everything in Program.cs (API Layer)

  📍 Location: Onion.API/Program.cs


  Code Snippet

  builder.Services.AddMediatR(cfg => cfg.RegisterServicesFromAssembly(typeof(CreateStudentCommand).Assembly)); builder.Services.AddSingleton<ISchedulerFactory, StdSchedulerFactory>(); builder.Services.AddSingleton(provider => provider.GetRequiredService<ISchedulerFactory>().GetScheduler().Result); builder.Services.AddHostedService<CronJobService>();

  Conclusion

  By following this guide, you have successfully built a C# Web API with Onion Architecture, CQRS, MediatR, and Quartz.NET CRON Jobs.
  This approach ensures:
  ✅Scalability using Onion Architecture
  ✅Separation of Concerns (SoC)
  ✅Background Job Execution with Quartz.NET
  ✅Better Maintainability with CQRS & MediatR
  

  🚀 Download Full Project
  Github
  

🔥 "Building a C# Web API with Onion Architecture, CQRS, MediatR & Quartz.NET CRON Jobs Project" 🚀

Cover In this:
✅ Onion Architecture ka Overview
✅ CQRS Pattern + MediatR used
✅ Quartz.NET ke sath CRON Jobs
✅ Dependency Injection & SOLID
✅ GitHub :https://github.com/gaganmanakpuria/AddStudentCronJobWithOnionArchitectureWithSOLID

📌 GitHub Repository Viewer

Loading...