PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchTo preview an ASP.NET Core website in Visual Studio, select the https launch target and press F5 (Start Debugging) or Ctrl+F5 (Start Without Debugging). Visual Studio builds and runs the project, then opens the running application in a browser at its local URL. Press Shift+F5 to stop it. This is a live preview of your application, not a screenshot of source files.
The exact controls vary by project type and Visual Studio version. The workflow below separates the normal ASP.NET Core browser preview from Browser Link, Hot Reload, and Web Live Preview so you can choose the right tool.
Preview an ASP.NET Core website in Visual Studio
- Open the project or solution in Visual Studio.
- On the toolbar, choose the https launch profile. A project may also show an HTTP profile, IIS Express, Docker, or another configured target.
- Press F5 to start with the debugger, or Ctrl+F5 to run without debugging.
- Visual Studio builds the project, starts the web server, and opens the local address in the selected browser. The URL normally uses localhost and a port from the launch profile.
- Use the site in the browser. For example, an
Index.cshtmlRazor page is rendered as the app’s Home page in a web browser, as described in Microsoft’s ASP.NET Core Visual Studio tutorial. - When finished, press Shift+F5 to stop a debugging session. If you used Ctrl+F5, close the running session from Visual Studio or stop the process in the usual way.
The first HTTPS run may display a prompt asking you to trust the ASP.NET Core development certificate. Accept it only if you trust the local development environment and the prompt matches the project you started. If the certificate is already trusted, no prompt appears.
What F5, Ctrl+F5, and the browser target do
F5: debug the running site
F5 starts the app under the debugger. Breakpoints, exception details, watch windows, and other debugging tools are available while the browser talks to the local server.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Ctrl+F5: run without debugging
Ctrl+F5 starts the same kind of local web server and browser preview without attaching the debugger. It is useful when you want a lighter development run or are checking behavior that does not require breakpoints.
Selecting a browser
The browser or debug-target dropdown beside the Start button determines where Visual Studio opens the application. The available targets depend on the installed browsers and the project profile. Microsoft Edge documentation shows Visual Studio launching an ASP.NET Core app in an Edge preview channel such as Beta, Dev, or Canary; choosing that channel changes the browser used for testing, not the fact that the app must be running.
To test more than one browser, use Browse With… where it is available and select multiple installed browsers. This starts the same local application in each selected browser. Browser-specific extensions, privacy settings, cached assets, and rendering engines can still produce different results, so inspect important layouts in each target rather than assuming one browser represents all users.
See edits while the site is running
Refresh, Hot Reload, or restart
Save the changed file, then refresh the browser. Some edits are picked up by Hot Reload; others require a Hot Reload action, a full browser refresh, or an application restart. Razor (.cshtml) changes and server-side code do not all have identical update behavior, so do not assume every save appears instantly.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Browser Link for connected browsers
Browser Link creates a development communication channel between Visual Studio and connected browsers. It can refresh several browsers, help test different screen sizes, map selected UI elements to markup or source, and support browser-based test automation. CSS Hot Reload can refresh connected browsers when CSS files change.
Rank #2
Browser Link is not the preview itself: F5 or Ctrl+F5 runs the application, while Browser Link coordinates refresh and communication after browsers are connected. Its controls and behavior depend on the project, Visual Studio version, and configuration. Microsoft’s Browser Link guidance recommends Hot Reload rather than runtime compilation when observing Razor changes.
Web Live Preview versus the Live Preview extension
Web Live Preview in Visual Studio
Microsoft’s Visual Studio Toolbox material describes Web Live Preview in Visual Studio 2022 as a Web Forms experience in which changes can be reflected in the running application. It is not the general ASP.NET Core launch path. For an ASP.NET Core MVC or Razor Pages project, start with the https profile and F5/Ctrl+F5.
The similarly named VS Code extension
If you installed something called “Live Preview” and cannot find a command in Visual Studio, first check which product you installed it for. A Microsoft Q&A response distinguishes the Live Preview extension associated with Visual Studio Code from Visual Studio’s separate Web Live Preview feature for Web Forms. Treat community setup advice as version-specific and verify the instructions for your exact Visual Studio release.
Launch-profile settings that control the preview
A launch profile supplies the application URL, protocol, environment variables, and browser-launch behavior. If the app starts but no browser appears, open the project’s launch-profile settings and check:
- Launch browser is enabled.
- The Application URL is valid and its port is available.
- The selected profile is the one you intended (for example, https rather than a profile for a missing service).
- The browser target is installed and selected in the toolbar.
Microsoft’s ASP.NET debugging documentation describes the Debug tab where launch-profile settings are exposed. You can also copy the local URL from Visual Studio’s output and paste it into a browser manually; that separates a browser-launch problem from an application-startup problem.
Common preview problems and fixes
The browser never opens
Confirm that the project built successfully, the selected profile has Launch browser enabled, and the application URL is present. If the server is running, paste its localhost URL into a browser. A blocked or already-used port can prevent startup; choose an available profile or correct the port rather than repeatedly launching the same failed profile.
HTTPS or certificate errors
Visual Studio may ask you to accept the development SSL certificate on the first HTTPS run. Follow the prompt carefully. If the certificate is expired, untrusted, or missing, use Microsoft’s current certificate guidance for your installed .NET and Visual Studio versions instead of applying a universal command from an unrelated release.
The page is blank or returns an error
Look at the Visual Studio Output and Error List windows for build failures, then inspect the browser’s address and developer console. A successful build does not guarantee that a route, database, API, or view exists. Verify the requested path, startup project, connection settings, and any dependent services.
Changes are not visible
Perform a normal browser refresh first. If the asset is cached, use a hard refresh or clear the relevant cache. If the edit is not supported by Hot Reload, stop and restart with F5 or Ctrl+F5. Browser Link refreshes only connected browsers and does not make every server-side change live.
“Live Preview” is missing
Identify whether you are in Visual Studio or Visual Studio Code, and whether the project is ASP.NET Core or Web Forms. The similarly named features are not interchangeable. For ASP.NET Core, use the running-browser workflow; for Web Forms, check whether Web Live Preview is available in your Visual Studio 2022 installation and project type.
Rank #4
The wrong browser opens
Change the browser/debug target in the toolbar, or use Browse With… for a one-off selection. Close stale browser windows and confirm that the selected profile is not overriding the target through a project-specific setting.
Recommended Free Tools
Previewing responsive layouts and multiple browsers
Use the browser’s responsive or device emulation tools after the app opens to check narrow and wide viewports. Browser Link can refresh multiple connected browsers, but it does not replace testing real devices, touch input, browser permissions, or production HTTPS. For a meaningful check, test navigation, forms, authentication, static assets, and error pages in addition to the home page.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you need a clean image or PDF of a URL rather than an interactive local debugging session, ScreenshotNeo provides a website screenshot API and MCP server. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing result in headers.
For a public or deployed URL, make one GET request (see the ScreenshotNeo API documentation):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Python:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)
Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
ScreenshotNeo also offers an MCP server with take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. Options include full-page and CSS-selector captures, dark mode, device presets or custom viewports, retina scale, PDF paper and margin controls, custom CSS or JavaScript, click and wait actions, request blocking, cookies and headers, timezone and geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed image links, asynchronous webhooks, bulk capture of up to 100 URLs per call, usage reporting, and an OpenAPI specification. Parameter names used by other screenshot APIs are accepted to ease switching.
The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; Growth is $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free, and every feature is included on every plan. Sign up free to try it without a card.
Free tools Windows power users keep installed
One-click scans. No signup required.
Frequently asked questions
Does Visual Studio show a static preview without running the project?
No. The standard ASP.NET Core workflow starts the application and displays its rendered output in a browser. A source file alone is not the running site.
Can I preview a site without debugging?
Yes. Ctrl+F5 runs the application without attaching the debugger and opens the configured browser target.
Is Browser Link required?
No. It is optional communication and refresh support for connected browsers. F5 or Ctrl+F5 is sufficient for a normal preview.
Why does a Web Forms tutorial not match my ASP.NET Core project?
Web Live Preview is documented for Web Forms, while ASP.NET Core uses the launch-profile and browser workflow. Project type determines which Visual Studio features appear.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
