How adarsh-basantwani/e-network works
Project type & purpose (from file tree + README)
This is a classic ASP.NET Web Forms application (circa 2015) named E-Network, which appears to be a social-network-style web app:
• Web Forms pages: *.aspx with code-behind *.aspx.cs
• Shared layout: MasterPage.master + MasterPage.master.cs
• Styling/themes: App_Themes/*, StyleSheet.css
• Local SQL Server databases: App_Data/Database.mdf and App_Data/ASPNETDB.MDF (plus log files)
• User-content storage: profilephotos/ (and likely uploads via UploadContents.aspx)
• Features indicated by page names: friends, friend requests, messages, profile editing, content upload/search, session expiration.
For diagramming: treat it as a server-rendered web application running on IIS + ASP.NET, backed by SQL Server (MDF), with some file-system storage for images/uploads.
Application logic
In Web Forms, most app logic is usually inside the code-behind (.aspx.cs) and potentially in helper classes (none are visible in the tree, so assume “page-centric” logic).
Data / persistence
• App_Data/Database.mdf: likely domain data (users, friends, messages, contents)
• App_Data/ASPNETDB.MDF: typical ASP.NET Membership/Role provider DB for authentication/authorization (or a similar identity store)
• web.config: connection strings, membership provider configuration, session/auth settings
Static & file storage
• profilephotos/: stored profile images (on web server disk)
• images/: static site images
What to extract from README (and what’s missing)
• Whether auth uses ASP.NET Membership (ASPNETDB.MDF) and Forms Authentication
• Whether data access is ADO.NET inline SQL, or some DAL classes (not visible)
• Whether file uploads store metadata in Database.mdf and binaries in profilephotos/ (or elsewhere)
Client
• Web Browser (end users)
Web Server / Host
• IIS (or IIS Express) hosting the ASP.NET app
• ASP.NET Web Forms Runtime
Application (E-Network Web App)
• Page Controllers (Code-behind): one component per major page group
Examples:
• Auth/session flows: Default.aspx(.cs), Logout.aspx(.cs), SessionExp.aspx(.cs)
• Profile: EditProfile, ChangePwd, ChangePhoto
• Friends: AddasFriend, ConfirmRequest, IgnoreRequest, myfriends, SearchFriends
• Messaging: Messages
• Content: UploadContents, LatestContents, SearchContents
• UI Composition
• MasterPage.master (layout shell)
• Themes/CSS (App_Themes/*, StyleSheet.css)
• AuthN/AuthZ subsystem
• Membership provider / Forms Auth (configured via web.config)
• Session State
• InProc session (most likely) unless web.config says otherwise
• Data Access
• Even if it’s embedded in code-behind, show a “Data Access (ADO.NET)” component to make DB boundaries explicit.
Datastores
• ASPNETDB.MDF (Identity/Membership DB)
• Database.mdf (Domain DB: friends, messages, content, etc.)
File Storage
• profilephotos/ (profile image binaries)
• Potential “Uploaded Content Files” location (if any; start by showing profilephotos/ since it’s explicit)
• Browser → IIS/ASP.NET: HTTPS/HTTP
• IIS/ASP.NET → Web Forms Pages: Server-side routing to .aspx + page lifecycle
• Page Code-behind → Membership DB (ASPNETDB.MDF): Auth queries / user validation
• Page Code-behind → Domain DB (Database.mdf): CRUD for friends/messages/contents
• ChangePhoto/UploadContents → File Storage: Write image/content files
• Home/LatestContents → File Storage: Read images/content (if rendered from disk paths)
• SessionExp / any authenticated page → Session State: read/write session variables
Architectural patterns present
• Monolithic Web Forms app (all features in one deployable)
• Page-centric architecture (each .aspx is a unit of UI + logic)
• Server-rendered HTML (no SPA frontend implied)
• Two-database split: Identity (ASPNETDB) vs Domain (Database.mdf)
• Mixed persistence: relational DB + server file system for images
Technologies in labels
• “ASP.NET Web Forms (.aspx + code-behind C#)”
• “IIS”
• “SQL Server Express / LocalDB MDF”
• “ASP.NET Membership Provider”
• “File System Storage (profilephotos/)”
• “Themes (App_Themes) + CSS”
Labels
• Use exact names where helpful (e.g., UploadContents.aspx, Messages.aspx)
• Use grouped labels to reduce clutter:
• “Friends Module: AddasFriend/ConfirmRequest/IgnoreRequest/myfriends/SearchFriends”
• “Profile Module: EditProfile/ChangePwd/ChangePhoto”
Examples:
• “Authenticate user”
• “Query friends list”
• “Create friend request”
• “Store profile photo”
• “Render latest content feed”
• “Search contents”
“Don’t overthink it”: separate into many components (recommended breakdown)
To be maximally detailed, split the application into these components (even if implemented as code-behind today):
• Auth & Session
• Default/Login (assumption), Logout, SessionExp
• Membership Provider integration (web.config)
• Profile Management
• EditProfile, ChangePwd, ChangePhoto
• Profile photo storage (profilephotos/)
• Friends / Social Graph
• SearchFriends, AddasFriend, ConfirmRequest, IgnoreRequest, myfriends
• Messaging
• Messages
• Content
• UploadContents, LatestContents, SearchContents
• UI Shell
• MasterPage + Themes/CSS
Component to:
• Domain DB (Database.mdf) as needed
• Membership DB (ASPNETDB.MDF) as needed
• File system where needed