My solution consists of several projects and every time I compile the project that I need to change. But lately every compiler eventually leads to the collapse of the visual studio.
Anybody know why?
I also had this problem, it is because every time you compile the LESS filesbuilds css. cancel this feature will override the options
Related
We're working with a solution which has multiple projects which references NuGet packages from other solutions.
Every time we do get latest from the TFS server on the solution, Visual Studio (2015) starts reloading each project in the solution which takes a really long time. Now this wasn't always the case, since this started happening only a few weeks back (the solution is a year old).
We have other solutions which were already experiencing this problem and our solution is to close the solution, then do get latest, then reload the project which is much, much faster.
Can anybody explain why this is happening and how to fix this issue?
This has been reported as a bug to MSFT, see Slow project reloading & Reload of projects is slow after call to TFS to get latest changeset. It seems your project files are updated from outside VS, which causes VS to load all them. More details please see the reply from VS IDE team:
Main culprit is, your project files are being updated from outside
VS, which causes VS to load each of them one by one. This is
extremely taxing process and it happens on the main UI thread. Hence,
this ASL logic is on-by-default to alleviate unresponsive solution
loads. Essentially, you’re pointing out a limitation in our ASL logic
that we hadn’t considered. This will be considered for a future
release, thank you.
In the meantime, one way to mitigate the problem would be to force
solution reload by touching the solution file, the *.sln file, which
will trigger ASL to kick in, basically VS thinking you’re doing full
solution load and it will optimize responsiveness time as much as
possible.
Ulzii Luvsanbat
Visual Studio IDE Team
Please try these steps:
Open Visual Studio installer and install the most recent available update for 2017 version.
Open %localappdata%/Microsoft/Team Foundation/7.0/cache and delete all files, then restart Visual Studio and retry.
I'm using Visual Studio Community 2013 to work on a solution containing a bunch of C++ projects. In my daily workflow, I often change the code of one project and rebuild it (which can take a significant amount of time), and at the same time I continue to work on another project within the same solution.
I noticed that the Quick Replace functionality (as found in Edit > Find and Replace > Quick Replace (CTRL + H)) is not available for any project as long as building is not completed or interrupted. In particular, the field "Search term" is always available (and thus I can continue to search whatever I want), but the corresponding "Replacement term" is grayed out.
Why does Visual Studio inhibit Search&Replace while building the solution? Is there an possibility to avoid this behavior?
I found a way that works for me: I can load the same solution in a second session of Visual Studio and build the modified project (or the entire solution) over there.
In the meantime I can continue to use the first session of Visual Studio to work on other projects within the same solution. This way the quick replace functionality remains useable all the time.
Not exactly what I was hoping for, but it's nonetheless a workaround that suits me well.
I am just having a problem in my Visual Studio 2005. Every time I debug my code, the project is re-generated and it really takes too much time. For this reason I am looking a possibility to disable this option if possible. Can you please help me with this situation?
Right click the solution and select "Properties". There should be an entry "Configuration" (sorry, I'm using German VS, so it may be named differently). There you can check boxes that determine whether a project should be built or not.
Please note that this affects the overall build process, too. I've had situations where I wondered why changes wouldn't work until I noticed that I kept working with an old version because I unchecked the Build checkbox!
When working in VS, the error messages in the bottom panel are compiler errors and warnings, right? Does this mean the app is being compiled all the time? I would expect those to appear only when trying to run the app.
This is probably a silly question, but I cannot find the answer.
Visual Studio continually parses the source code; this allows it to preemptively report some errors before you actually compile the source.
This is, of course, dependent upon which language you are using. C++ didn't get preemptive error reporting until Visual Studio 2010.
Visual Studio doesn't natively continuously compile code.
However, I just downloaded the 14 day trial of this little app called .Net Demon that's a plugin for Visual Studio. It costs $30, but definitely a nifty tool if you've got large solutions with many projects.
http://www.red-gate.com/products/dotnet-development/dotnet-demon/
I'll probably end up breaking down and buying it, it's pretty slick.
Each programming language is different (each provides a Visual Studio 'language service' specific to that language that provides the feedback), but for the most part, yes, it is being compiled over and over. In F#, for example, the compiler is divided into a few stages, main ones being lexer/parser, typechecker, and code generator, and the lexer/parser/typechecker are running inside VS, and every time you type a character into a file, that file is re-run through those stages of the compiler.
When you compile an application there might be errors and warnings which will be shown at the errors window. When you run the application errors will no longer be shown in Visual Studio but depending on how your application is organized it will either crash or handle them gracefully. Also notice that if you try to run the application with F5 or Ctrl+F5 Visual Studio will try to compile it first and if there are compile-time errors and warnings they will be shown.
Using Visual Studio 2005, if I open tests in a VSMDI and try running tests, it sometimes re-builds projects. However, these builds go extremely slow. The CPU is 99% idle and the output window shows VS clunking along compiling things. Is there any way to fix this? It makes no sense. Upgrading isn't necessarily a viable option for those of us with shared legacy code to deal with.
Have you tried upgrading to SP1? I don't know of any specific issues in this area but this would be the first change I tried to make.