I am building an asp.net website on vs2005 (c#) and I can't find a way to debug using a browser that is not IE.
I managed to open pages in non-debug mode with different browsers by using "browse with..." on any file's context menu and even setting the desired browser as default if i wish.
but I can't find a way to make this alternative browser work when I do it in debug mode (start debugging button/F5).
Is there any way to do this? I searched around a lot and all I found is a solution for vs2003 which doesn't seem to work in vs2005.
thanks,
Asaf
Related
I wanted to try developing a website in VS but I'd really like a visual (WYSIWYG) editor. Apparently, this is available in VS. In that video, and lots of other videos and websites, it shows 'Design' and 'Split' buttons on the window, which should show a live view of the web page that's open. It seems this is supposed to work with both .aspx and .cshtml files.
However, nowhere can I find how to enable this, and I've done a lot of searching. I've even uninstalled and reinstalled VS. There are no options, settings or menu options to enable it. I'm using VS 2022 Community, fully up to date, in an ASP.NET Core Web App project using .NET 7.0.
Does anyone know what's wrong? I wondered if it was only available in VS Professional/Enterprise, but seemed silly to me.
that feature in the brand new vs2022 is for ONLY .net framework, and ONLY for web forms.
So, if you using MVC, then you don't have a forms designer.
And if you using .net core, then you can't use this feature either.
So, when you create a project, it MUST be .net framework (not .net core), and it MUST be a webforms project, and NOT MVC projects.
So, that would be say this (for c#).
And (best choice) would of course be this template:
And if using vb.net, then again, same thing:
So, web projects, and .net framework - NOT .net core projects.
thus:
So, out of those templates, then again, of course a asp.net web application would be the preferred choice.
so, for example, here is a gridview in "live" preview, and yes you can edit or drag + drop controls into that live preview.
it looks like this (split screen for example).
but, if I run the page, same in a chrome based browser (Edge, or chrome).
Then I see this:
Since the new designer is based on the chrome engine then as above shows, yes, it is rather cool.
Here is that web page, not split view in the designer:
(so I have NOT yet hit f5 to run, but only am in design mode)
so, in old legacy designer, I would see/get this:
So, note how do you DO NOT see say for example the bootstrap menu bar.
But, if I turn on live preview, and now I see/get this:
Note how we now even see the bootstrap menu bar in the preview - I have not yet hit f5 to run in browser. And on the bottom, you see a "bread-crumb hierarchy" as to what element you clicked on (very much like f12 debug tools in a browser, and then using "elements" selection).
You can find it by creating an asp.net web (.Net Framework) and selecting Web Form in it.
I use vs2022 17.4.2 community version
You can also view its settings in the tool.
I am developing a web application on Visual Studio 2013. On older versions, whenever there is a bug in the web app, I moved from the browser to the visual studio to the line where the code is.
Now, whenever there is a bug, I just see it in the browser without being able to see it in the Visual Studio. As if the debugger is not able to step into my code.
This has been going on for all my web projects which makes me feel that it is a setting in VS but I am not able to locate it.
can anyone help?
I was able to find out what was wrong here.
it seems that for some reason, under Debug in the main menu and under Exceptions, nothing was checked! I checked ALL "Common Language Run-time Exceptions" and it worked for me.
However, you need to spend sometime there in the debugging list. If you enable ALL, you will get all sort of exceptions captured.
I have an ASP.NET application written in .NET 4.0. When I run the application through Visual Studio, everything works and looks good. Same thing when I deploy it to IIS7 on my local machine. However, when I deploy it to another box running on Windows Server 2008 R2 with .NET 4.0 and IIS7, I get the following parse error:
Cannot create an object of type 'System.Web.UI.WebControls.TextBoxMode' from its
string representation 'Number' for the 'TextMode' property.
It's complaining that the TextMode property on asp:TextBox doesn't contain the Number option, even though it works perfectly fine on my local IIS. I came across this post and people are suggesting the two machines have different .NET versions. This is not the case for me; both machines are have .NET 4.0 and IIS7.
Besides this error, other pages are also rendered differently style-wise. For example, IIS on the server machine doesn't respect the Width property on any of the asp:TextBox controls; I have to apply the width as a style, even though my local IIS renders them just fine. I'm using IE10 w/o compatibility mode.
I originally thought the problem might have been with missing js or style files, but IE reports success status for all content files in the Network Profiler window.
I'm truly lost at this point. The code, IIS settings, and .NET versions are exactly identical on these two boxes, but the pages are rendered differently. The only thing I can think of is that some other Web component was installed with Visual Studio that is changing the way IIS renders aspx pages. Is that possible? If anyone has come across this issue at some point I'd appreciate it if you could give me some pointers as to what could be causing the issue.
So I finally figured out what the problem was. The parse error did in fact have something to do with .NET. I have .NET 4.5 installed on my machine but not on the server. What I'm still confused about is that the target version for my application is 4.5, so if the Number option exists only in 4.5, why does Visual Studio even display it? Not sure if that's a bug or if I'm overlooking something.
As for the discrepancies between local and server IIS, it turned out I had to install the ASP.NET Browser Definitions Hotfix (KB2600088) on the server. That fixed all the styling issues.
this is acutally one of the interview questions I had. I didnt really use any tools to debug, only use trace, debug, breakpoint, command window.
I dont think my answer is what they are looking for. please tell me what tools do you use to debug your asp.net application and how do you debug the applicaiton in both Dev and Production environment.
Visual Studio is the most powerful debugger in the world, but mostly limited to server-side code.
Firebug, or the built-in dev tools in Chrome and IE for JavaScript
Fiddler for examining web requests, AJAX, etc.
SQL Server Profiler to find SQL-to-ASP discrepancies, query timing, etc
Red Gate tools for memory profiling, finding leaks. VS also has good profiling tools, depending on what version you're using.
Most of the dot net developers are using Visual studio debugger for all dot net applications such as ASP.NET, VB.NET, Console applications.
For ASP.NET application, you can debug server side & client side codes from VS (when you are running the application from VS). It will be in DEV & Prod environment you can use the latest DLL and attach debugger mode and test it in VS.
For Client side, you can use firebug in firefox, dev tools in Chrome and IE for JavaScript.
For more details please see this link.
Well it really depends on what you are debugging?
I often use Fiddler for trafic debugging and IE Deveoper Tools or Firefox Firebug for css, html and sometimes javascript debugging.
Visual Studio Debug, Firebug for Firefox with Firecookie addon, IE Developer tools and SQL Profiler for starters.
I'm using Firefox as my default browser and I'm trying to debug java script in side asp.net page visual studio 2008 with Firefox browser.
how to enable script debugging in visual studio 2008 when using Firefox?
by the way, I installed JavaScript Debugger plug-in for Firefox.
Unfortunately there's no way to attach to a non-IE browser in Visual Studio unless someone knows of a trick I don't. You'll want to either use the infinitely useful Firebug Extension for Firefox or the more feature rich Venkman debugger.
I have had issues with scripts being cached in FF while you're developing, so I would suggest making frequent use of the [CTRL][SHIFT] + Delete shortcut to clear your cache. Another trick I use is to insert
debugger;
into your script where you want to make sure you break into the debugger. I'm sure this works in Firebug and may also in Venkman.
Happy debugging.