its possible create video conference using asp.net??

Short answer: yes — a web-based video conference can be built with ASP.NET and C#. Modern implementations put the media path in the browser (WebRTC) and use an ASP.NET app as the web server and signaling channel. This post updates the old thread for @am_dumb and @sachinkumar46; @kvprajapati correctly pointed out the thread age, so the following gives a current, practical approach.

Minimal architecture and steps:

• Client (browser): capture media with getUserMedia and create a RTCPeerConnection for audio/video.
• Signaling (ASP.NET/C#): exchange SDP offers/answers and ICE candidates via SignalR or a WebSocket endpoint.
• NAT traversal: configure STUN for discovery and a TURN server to relay media when direct P2P fails.
• Multiparty/scale: use an SFU (forwarding media server) or a cloud SDK if many participants, recording, or bandwidth control are needed.
• Deployment: serve pages over HTTPS (required for camera/mic access in browsers) and secure the signaling channel.

Example (simple SignalR hub to forward offers/answers/ICE):

using Microsoft.AspNetCore.SignalR;

public class SignalingHub : Hub
{
    public async Task SendOffer(string toConnectionId, string sdp) =>
        await Clients.Client(toConnectionId).SendAsync("ReceiveOffer", Context.ConnectionId, sdp);

    public async Task SendAnswer(string toConnectionId, string sdp) =>
        await Clients.Client(toConnectionId).SendAsync("ReceiveAnswer", Context.ConnectionId, sdp);

    public async Task SendIceCandidate(string toConnectionId, string candidate) =>
        await Clients.Client(toConnectionId).SendAsync("ReceiveIceCandidate", Context.ConnectionId, candidate);
}

Notes and common pitfalls: browsers require secure origins for getUserMedia; permissions must be granted; ICE candidates may be blocked by corporate firewalls (TURN required); bandwidth/CPU limits become apparent with many participants (use SFU or cloud services for scale). For a learning path, build a one-to-one WebRTC demo with SignalR signaling, verify STUN/TURN, then add an SFU or third‑party SDK for multi-party and recording. This keeps the original question answered while respecting the thread closure by @kvprajapati.