I seem to have gotten a bit carried away with the number of libraries I'm referencing in a ASP.Net MVC web application I'm working on. Is there any tools or features already built into Visual Studio 2008/2010 which indicates to me which references I don't need?
See this older SO question and answer.
Resharper will do this for you, with its clean code context menu.
Related
I have recently installed Visual Studio 2015 (Enterprise), and although I only selected C++ from the programming languages list, it has also installed F#. A language I have never used and will not use, simply because I'm working with C# and VB currently, and I'm satisfied with the results I get. My plan is moving to C++ after I learn C#, so I have nothing to do with F#. It's only taking up space from my disk and I want to remove it. I've been looking all morning about an easy way to do so, but all I could find was a lot of questions regarding earlier VS releases and somehow managed to successfully remove the F# project templates. But the rest is still there - screenshot:
As you can see I cannot uninstall it via Extensions and Updates, nor I can find it in Programs and Features. I could find some F# SDK and F# for VS stuff in the registry, but I'm not experienced enough with it to find the uninstallers. Any ideas?
Goto Programs and Features in Windows, and select Visual Studio Enterprise 2015 and click Change, when the Setup dialog appears, select Modify then untick the following:
We have a large solution (112 projects) in VS2013 Ultimate.
I love the Code Map feature, however when I am dragging types onto a Code Map dgml it insists on building the solution - even though I have not made any changes.
I can't see many options for this great feature, but is there anyway to tell it to stop building the solution everytime I add a type to the diagram?
This is a known issue and major complaint with Code Map in Visual Studio 2013. It affects certain types of projects (like ASP.NET ones) more than others because these projects always report that they have changes and need to be rebuilt.
The experience is improved in Visual Studio 2015 Enterprise, as we have added a "skip build" option.
We've made many improvements to CodeMap in Visual Studio 2015, so it's definitely worth getting it if you use Code Maps. Note that you can install VS 2015 along side VS 2013, so you don't have to migrate projects etc.
I see the code map document window in VS 2015 now contains a button labelled "Skip Build" which seems to solve this problem
I have a solution with several projects that have Register for COM Interop checked.
I have a Visual Basic 6 project that references the resulting TLBs. One issue with VB6 is when it references a dll/tlb, it puts a lock on that file.
Using Visual Studio 2010, unless I'm doing a rebuild or have made a change to one of these interop projects, I can build/run the solution (with the VB6 project open) without it barking that one or more of the assemblies is locked.
However, using Visual Studio 2012, even on a simple build where nothing has changed, apparently it always does the regasm, which makes it impossible for me to debug my VB6 project.
Is this new feature of Visual Studio of running regasm on build something that I can turn off?
EDIT: Allow me to simplify:
Using Visual Studio 2010, I hit Build-->Build Solution and check the output for one of my assemblies that is marked as Register for COM Interop and the file has not changed.
Using Visual Studio 2012, I do Build-->Build Solution and check the same assembly, it has been updated, and does so every time I hit Build Solution.
I want the behavior in Visual Studio 2012 to work the same as it did in 2010.
EDIT (again):
I posted this to Microsoft Connect. If someone answers it there or posts a workaround, I'll urge them to also post the answer here.
I've always encountered problems like this when running VB6 and VS20XX, but I always did a rebuild. My suggestion is to stop using VB6 for testing purposes. I found it was far easier to simply create a testing project and do all of my testing in .NET on my .NET code. This should only require a small amount of set up, but it is well worth it in my opinion.
I know this isn't an answer to your specific question, but it offers an alternative. As far as the problem you are describing, I can't duplicate a change in behavior. I start off with only VS201X open, full solution rebuild, open VB6 and add a reference to an exposed COM DLL. I didn't notice anything unexpected.
Build works fine as long as I haven't changed anything in the COM DLL
Build fails if I changed the COM DLL's code as the file is locked
Rebuild fails as the file is locked
My company recently created a Visual Studio 2010 add-in that allows us to create LINT files from any given visual studio project from 2010, 2008 and 2005. We now want to get this same add-in to work in Visual Studio 2012, because we know that many of our customers will be using this in the near future, if not already.
We thought that it should be a simple "switch-in", and that the same code should work for both, but lo and behold, the VS10 add-in didn't work in VS12. So I copied the code (absolutely no changes) into a VS12 add-in, and surprise surpise, it did work. Naturally, we do not want to have two versions of the same code; bad for readability, bad for maintainability, so we still want to find a way to get the VS10 add-in to work in VS12.
I think the problem lies in the Microsoft.VisualStudio.VCProjectEngine assembly. This is interpreted differently in VS12 to how it was in VS10, meaning that when VS12 reads the add-in, it doesn't do what we want it to do.
I have done some research into this problem, and many people suggest creating a work around by using reflection, but I am reasonably new to this concept and don't feel confident enough to try it and risk seriously ruining the add-in.
So my question is this: Is there a nice and easy way of being able to read the VS10 version of the Microsoft.VisualStudio.VCProjectEngine into VS12?
Much appreciated :)
I later found an answer to this question and realised it hadn't been confirmed on the thread.
The answer indeed lies in the VCProjectEngine assembly. For some reason, this is a different module in Visual Studio 2010 to the module (with the same name) in Visual Studio 2012, which means any code requiring the module when written in VS2012 will not work in VS2010 and visa-versa.
It's a pain, because it means we have two lots of exactly the same code, but that is the way it has to be.
I'm currently considering a big "no no" and jumping over to VS 2010 while it's still in RC... after all, text code is text code, how bad can it "F" things up?
I'm just wondering if anyone is using VS 2010 for their projects? I'm very much interested in the subtle additions as well as the multi-screen support.
I've been using it in a VM and it's been pretty stable and even resharper 5.0 has support for it now so it's as good as fully baked for my liking.
A few things to be careful of are:
the .sln files aren't backwards compatible so it won't be easy to share with other people not using VS2010.
There are a number of plugins that don't yet support VS2010 so if you depend on any third party plugins make sure they work
ASP.NET MVC 2 RC 2 has a bit of funkiness so you should check out this post to make sure you've got all your stars aligned if you're using 2010 and MVC.
As you said first of all it is still in RC. People wouldn't upgrade the current Visual Studio version unless there is a reason for it.
If you are not going to use any of the features in .net 4.0, it is probably not important to switch to Visual Studio 2010.
We are using VS2010RC and TFS2010 for our projects in production.
Works great!!
What I like in VS2010 and use:
Test Manager for recording manual tests in Web, WPF, Windows Forms and soon in Silverlight. AWESOME!
Generating "Coded UI" tests
Hierarchical work items (TFS) finally :-)
What I like in VS2010 but don't use yet:
.NET4 features like: Parallel extensions, dynamic keyword, optional and named parameter
Yes, Multi Monitor support works a bit better, but was fine for me with VS2008 too