How prabhatjain8/tpowebsite works
Project type and purpose
• This is a full-stack Training & Placement Office (TPO) web application.
• Frontend: Angular SPA providing login/registration, role-based UI (admin, student), company listings, upcoming/past drives, comments, enrollment.
• Backend: ASP.NET Core Web API (C#) with Entity Framework Core for data, Identity for auth, email service for verification/reset.
File structure
• TPOwebsiteFrontend/ – Angular CLI structure:
– src/app/Components/* – feature components (login, register, upcoming, past, admin, comment, password)
– src/app/*.service.ts – Angular services calling HTTP endpoints
• TPOwebsiteBackend/ – ASP.NET Core Web API:
– Controllers/*.cs – HTTP endpoints (LoginRegisterController, CompanyController, CommentController, UpcomingController)
– Models/* – EF Core DbContext, entity classes (Company, Upcoming, Student, Enroll, CompanyComment), repositories, email service interfaces/implementations, token models
– Migrations/* – EF Core migrations snapshot
– Program.cs & appsettings.json – DI registration, configuration (DB connection, email settings)
– launchSettings.json – local ASP.NET profile
README for additional insights
• Features: email-verified login/register, role-based access, comment & enroll flows, admin CRUD on companies/upcoming, password change & reset via email.
a. Main components
1. Angular Frontend (SPA)
2. ASP.NET Core Web API
3. SQL Database (via EF Core)
4. Email Service (SMTP provider)
5. Authentication/Authorization (ASP.NET Identity or JWT)
b. Relationships & interactions
• UserBrowser ↔ HTTP(S) ↔ Angular SPA
• Angular SPA ↔ HTTP API ↔ Controllers ↔ Services/Repositories ↔ EF Core ↔ Database
• Web API ↔ SMTP server (for email verification & password reset)
• Auth flow: API issues JWT or token, stored in frontend, used on subsequent calls.
c. Architectural patterns & principles
• Layered architecture: Presentation (Angular), API Controllers, Business Services/Repositories, Data Access (EF Core).
• Dependency Injection (registered in Program.cs).
• Repository pattern (ICompanyRepository, IUpcomingRepository, IEmailService).
• Modular frontend: Angular modules, component hierarchy, route guards (AuthGuard).
d. Technologies & frameworks
• Frontend: Angular, TypeScript, Angular Router, HTTPClient, Reactive Forms
• Backend: ASP.NET Core 6, Entity Framework Core, ASP.NET Identity, Dependency Injection
• Database: SQL Server (or configured RDBMS)
• Email: SMTP (configured via EmailSettings in appsettings.json)