I've tried this on two different machines now on Windows 7 and it appears that the Window > New Window menu command is not available in Visual Studio 2010. It doesn't work for HTML, .aspx, and .js files, but does work for .css, .cs, and .xaml files. Has anyone else noticed this or knows why this is?
(I have the productivity power tools extension installed)
I found a registry entry at
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\Languages\Language Services\HTML]
or
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\Languages\Language Services\HTML]
for 64 bit machines
called "Single Code Window Only"
I deleted it and the menu command showed up!
Then I made a new window, and it was completely blank.
I checked with Visual Studio 8 and found the same thing. Apparently they have not implemented "new window" for some file types.
Apparently they had started to implement it for Visual Basic Files, but had it disabled because it hadn't been thoroughly tested yet ( http://msmvps.com/blogs/deborahk/archive/2010/05/17/visual-studio-window-new-window.aspx ).
Related
Created a stock Blazor project (Client or Server side, both do it).
When I open the _Imports.razor, not a problem.
Open NavMenu.razor, a problem.
The IDE opens the file, displays formatted Razor and after a couple of seconds just hangs, CPU usage for devenv.exe goes 50% and stays there until End Task.
Any idea how to fix this? The IDE should not hang when I try and work with a Razor file.
Thanks to the effort by these guys, changing the IDE font from 'Cascadia Mono' to Consolas sorted the problem:
https://youtrack.jetbrains.com/issue/RSRP-487353/Visual-Studio-2022-stops-responding-when-used-with-Resharper
(Note: Not using Resharper, stock VS2022 install)
On Visual Studio 2022, Windows 11.
Linq to SQL tools is installed from installer (Individual Components).
When right clicking a dbml file and View Designer, it just sticks on this and eventually needs an end task:
Tried (to no avail):
Clearing all app.config connection strings in the same project (in case it was silently barfing on one of those)
Installing older .NET frameworks, ticking on Data Storage and Processing and Data sources and service references
Any ideas what might be causing this? (Ran OK under Win 10 / VS 2022).
Edit: I've had this after every new PC install with Win 11, VS 2022 (3 work PCs), but it seems to resolve itself after a few days. I now know why, see marked answer re toolbox.
I experienced the same problem on Win8 with VS 2015 and 2017 and 2019, Win10 with VS 2015 and 2017. I did not solve the problem. Do not know what causes this problem. But now on Win11 with 2022 I opened my problematic DBML file, it took really long time to open (during opening it showed Not responding etc.) but finally VS opened DBML file. Then I made a change in the designer (just moved class a little bit = change = auto-generated file will be re-generated after save) and saved. Now this particular DBML file is opened within a second. Try it.
Viewing the Toolbox and (optionally) resetting it (right click > Reset) seems to solve this. It seems the designer can't open when the toolbox is not initialised (or fails to initialise). It is often a while before I open the toolbox on a new install so I kept on encountering this problem.
I'm new to JavaScript (/html in general) and to visual studio. I seem to have two different issues: I'm having trouble running code in browsers, and some of the keyboard shortcuts are broken.
I've recently installed Visual Studio 2017. Everything seems great except I need a way to test my open file. I've looked online at certain guides which tell me to configure the task runner to be able to do so. The problem is, to get to the tasks.json which I need to edit, I have to open the command palette with ctrl + shift + p, which doesn't seem to work. Additionally, I can't find any other way to open the command palette using the bar at the top nor can I find any other way to open tasks.json. Also, I noticed that I should be able to run code in browser using the "View in Browser (Google Chrome)" and "Browse With..." options under "file". The keyboard shortcut doesn't work for View in Browser, and when I click on both options, I get a dialogue box with the error "The operation could not be completed. Class not registered".
How can I set things up properly, or at least be able to properly test my code?
I think what you need is Visual Studio Code, not Microsoft Visual Studio.
Both were similar but target different programming platform.
If you want to develop web application, HTML/CSS/ts/js etc, better if you use VS Code.
I have a .NET 3.5 website that we work on in Visual Studio 2010. The problem is that when we publish the website and put the files to the web server with IIS7, the display is different than what is shown when we run locally. The problem happens on all of our supported browsers: Chrome, IE, and Firefox. The control that is displaying incorrectly is an asp menu control. While I have read many other threads regarding issues with this control, none of the solutions seem right for my specific problem.
In chrome, I used the Firebug extension to compare the html and css for the desirable and undesirable displays. I found that the css is identical while the HTML is different. The information below compares the html tags that get generated for different browsers and publishing methods.
Visual Studio 2008 publish and local (desirable):
Chrome: ul, li
IE: ul, li
Visual Studio 2010 publish (undesirable):
Chrome: span
IE: table, tr, td
Our temporary workaround is very inconvenient. When we are ready to publish, we open the website in Visual Studio 2008 and publish from there.
Another problem I have that is related: sometimes, this menu is supposed to be hidden. When I publish from 2010, it is not hidden when it should be. Desirable behavior is achieved when running locally or publishing from Visual Studio 2008.
I saw the solution here that was the closest thing I found to my problem. ASP.NET Menu rendering different from vs2008 to vs2010 The only difference here is that the asker's problem was Chrome specific while my problem extends to all browsers. Maybe this solution can be tailored to my issue?
I haven't solved this problem exactly, but do think I found the problem. I read that there is a bug with visual studio where the app browsers dll gets published in .net 4.0 even though my project is .net 3.5. A workaround is to save the file from the 2008 publish and replace the file from the 2010 publish with the 2008 version. I guess this problem will go away once we upgrade our .net version.
So far I was using VWD 2010 express quite smoothly on Windows XP. Now I have got a new laptop - with Windows 7 64 bit. Yesterday I installed VWD 2010 express. I transfered all my data to the new laptop. When I open an existing project, it opened well and even runs very well. But when I am design mode I have lots of problems like
Cursor is not seen in the .aspx page and scrolling does not work. Cant edit anything. However .aspx.cs works normally
when I press Ctrl + F, Find window opens up but when I give find next, the instance is not seen and the page does not navigate to the instance
When I double click on a file in the solution explorer, i dont see it open. But when I minimise the entire VWD and maximise it, I see that the clicked page is open.
sometimes (mostly just after the project is loaded) part of the screen is black and when i minimise VWD and maximise, the page is properly shown.
I tried Repair and also uninstalled and reinstalled the entire VWD 2010 express - the problem still exists. I dont know what problem it could be. I did not encounter any problem while installing VWD. Could this be a VWD problem or memory problem (8GB RAM) or graphic card(dedicated) problem? Any help is highly appreciated.
I solved the issue yesterday, I logged in to the forum today to post my solution so that it helps someone later. Here is what I did:
I opened the "Compatibility Troubleshooter" in the control panel and identitified that there is a compatibility issue. So I made changes to open VWDexpress in the compatible mode (In my case it was Windows XP service pack2) and saved the settings. Now it works very well.