Using a new laptop at work, my Visual Studio 2010 JScript editor basically locks up whenever I open the coffee-script.js v1.2.0 (minimized) file. It basically consists of a single line that is about 170k characters long.
I have attempted turning off all of my JScript extensions (outlining, etc.) but it hasn't really affected the performance.
Currently my only solution is to Open With the Source Code (Text) Editor instead of the Script Editor. But as I do a lot of JavaScript at work I'm worried that this may be the harbinger of many other script editor problems on this laptop. I'd rather not have to work around opening minified files all the time.
Does anyone have any thoughts?
Related
We need to localize an app that has hard coded strings across aspx and c# files.
This is a common need, so we expected to find tooling.
We tried resharper, but it turns out that for aspx files, this feature is essentially nonexistent.
What is the path forward? (initially 60 aspx files, ultimately 200+)
I should add that we reviewed all known tools (below). In every case, at least one of the below is true:
Does not work at all in visual studio 2015
crashes right and left
does not support aspx (mostly support .cs files only)
https://visuallocalizer.codeplex.com/
http://www.lingobit.com/extractor/c_sharp_extract_hardcoded_string.html
https://visualstudiogallery.msdn.microsoft.com/39ae29d3-81e1-43d4-9c48-fc9644869d84
Visual Studio - Tool to replace hard coded strings with resources
Find all source hardcoded strings
The best solution we have found so far is: Jinnee.Prelude 2015
https://visualstudiogallery.msdn.microsoft.com/e71acd60-0f16-4adf-b398-18c4fa210916
Gives us localization in C# and static strings in ASPX. But still need to extract inline strings from ASPX by hand.
It crashed VS a couple of times, but VS is fast to restart (thanks to not having resharper installed). Overall it is a win. (Wish we had sources so we could enhance it further!)
I've recently started using Visual Studio quite heavily since starting to develop in .Net
I really like the intellisense as it increases my productivity by allowing me to code faster. Previously when authoring CSS I would just use Notepad ++ and I got very used to some of the little features that this awesome text editor possessed however, now that I am doing the bulk of my work in Visual Studio 2013 I want to try and avoid having too many environments open at once. With this in mind, there is one feature inparticular that I would like to try and replicate in Visual Studio when editing CSS or indeed any other type of code.
In Notepad ++ it automatically includes a sort of guideline which runs down the page between the opening and closing tags of elements as shown below:
My question is, how do I replicate this behaviour in Visual Studio 2013 as the currently setup I have at the moment isn't as clear/productive as you can see below:
Any help would be greatly appreciated.
There are a couple of free extensions you can use to do this. These will run on any of the Visual Studio versions except Express, which does not support extensions.
You can duplicate this with the Indent Guides extension.
You can also use the Structure Visualizer Feature of the Productivity Power Tools.
Note: The backgrounds in the example are different because they are taken on different machines with different themes.
I have a C#/.Net 4.0 project in Visual Studio 2010. Parts of this project were originally from an old VB6 program that was converted to C#.
Sometimes I need to look at the old VB6 code side-by-side with the C# code, and so it's very convenient to just open and view the file in Visual Studio. V.S. even displays comments and keywords in appropriate colors for easy viewing. To open the VB6 file I'm doing a File>Open>File. The VB6 file has a .cls extension.
The problem is that when I do that it also tries to do background compilation of it, so as soon as I open it, it registers hundreds of errors because VB6 isn't a supported language and even if I do a Build Solution or Rebuild Solution it includes those results in the build so I can't build my C# project when the VB6 file is open.
1. Why does it do this, considering that the VB6 file is not part of the current solution or project?
2. How do I turn it off so I can view the file but not have Visual Studio try to compile it?
Why does it do this?
The cls extension is mapped to the Visual Basic language service. It will interpret any file with that extension as a VB.Net file and process it as such.
The Visual Basic Language service is always compiling files to a degree in the background. It doesn't actually produce EXE / DLL but will go far enough to provide semantic information to the front end. This is used in intellisense, code highlighting, error squiggles, etc ...
How do I turn it off?
Unfortunately you can't. Visual Basic background compilation is not configurable. Hence any file which it believes to be VB.Net code will be processed in the background and errors will be displayed.
The only way to view it without errors is to rename the file to an extension not thought to be VB.Net code (like txt)
I am a big fan of Microsoft Visual Studio. I like the code folding, auto-completion, auto-formatting, and many more.
I am thinking that it will be good if I can abuse MS Visual Studio as an IDE for LaTeX users. Shortly speaking, is it possible? For the first step, I think making me possible to invoke LaTeX compiler and invoke PDF viewer from within Visual Studio is more than enough. But you can step further by allowing me to use auto-completion, etc.
Is there any idea?
LaTeX editors usually have setting to invoke LaTeX compilers and PDF viewers as follows. It might be useful for you.
For Visual Studio Code (VSC) use extension: "LaTeX Workshop".
On Windows: Install MiKTeX, then over MiKTeX Console install package "latexmk". Finally install Perl http://strawberryperl.com/
PDF gets rebuilt automatically on saving the .tex file with VSC.
For viewing the changing .pdf file in Windows "TeXworks" did work best from multiple viewers tried, because it does not lock the .pdf file against changes and quickly refreshes the view on changing pdf output.
Yes. It is possible. Use Visual Studio Code with LaTeX extension. And it is free of charge.
I am working on a big solution that contains a mix of C# and C++ code using Visual Studio 2012 Professional with the latest Resharper plugin.
I obtain a fresh copy of the entire solution from source control.
As expected, Intellisense places its curly red lines under many types and fields in C++ code before I compile my Solution for the first time. However now these squiggly lines do not disappear even after (successfully) compiling the entire solution.
I get 100+ Intellisense errors saying "Intellisense: cannot open source file .tlh
But these files definitely exist at the given location and VS has full access rights to them as I start it with elevated rights..
I am even able to jump into the namespaces, declarations or whatever with the red lines underneath so the code definitely exists.
How do I make Intellisense worke again and make these annoying lines disappear?