Try this fix:
dotnet nuget locals all -c

Other helpful dotnet core commands

• dotnet restore
• dotnet build
• dotnet run (csproj) or dotnet mydll.dll (no run required)
• dotnet test
• dotnet publish
• dotnet pack
• dotnet new (project or solution)
• dotnet build-server

The post dotnet nuget updates appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

The post Running node.js apps from within VS 2017 appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

1. RESET all settings –  Tools > Import and Export Settings... > Reset all settings. (This always works for me).
2. Close Visual Studio , Delete yoursolution.suo file. Reopen Visual Studio and reload your project. (This works some of the time).

There are other possible reasons for losing intellisense  – but these two fixes usually work.

The post Lost intellisense in Visual Studio appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

It is a two way communication between Visual Studio and your launched app (using Signal R , I believe). 

To disable this feature, add the following key to Web.config:

<appSettings>
  ...
<add key="vs:EnableBrowserLink" value="false" />
</appSettings>

The post Visual Studio 2013 javascript error while running in DEBUG mode appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

1. One thing to try is to delete the .suo file (usually at the Solution level) – after shutting down Visual Studio. Try restarting VS and see if you recover Intellisense.  The thing that fixed it for me was the following:  
2. Options pane under Text Editor/General (and also Text Editor / C#).

Make sure the Auto List Members and Parameter Information are CHECKED ( as shown below). That’s it- that should recover your intellisense.

The post Intellisense disappears after Resharper Uninstall appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

2. Type CTRL ]   (CTRL and CLOSE BRACKET) – it should jump to the closing brace

The post Visual Studio – VS find matching brace appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

Extensions (under the Tools menu)

1. Memory leaks in extensions – Some extensions are just poorly behaved and known to have memory leaks. This may explain why when you perform certain tasks from  VS , you see your memory usage spike. .NET Reflector from jetbrains was causing one such issue. 
2. Too many unused extensions – Disable (or uninstall) any extensions that you are not using.

Add-Ins (also under the Tools menu)

The same considerations apply to add-ins which get loaded on VS startup. Go through and remove the add-ins that are not being used.

Once we figured these out, the memory usage went down from 700 MB to 200 MB.

The post Visual Studio Using Too Much Memory appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

The Search Part

However, even though I had no NEED for regex in my search term, I still HAD to make the search term RegEx friendly. For example, the open parenthesis in using (var , had to be made RegEx friendly.  Fortunately, all this meant was escaping (the open parenthesis ‘(‘) with a backslash – as in \( .
The snapshot shows what my my enusing \(var transaction – replaced with NewLineOfCode1 and NewLineOfCode2 would look like. The \t is used to align the new lines of inserted code with the existing line (using \(var.  The \n is the newline insert between two lines of code.

1. Notice that ‘Use Regular Expressions’ is checked.
2. Notice that I still retain the using (var…part – I am doing an insert of additional lines of code – NOT  replacing existing lines of code. The same pattern could be applied for a pure REPLACE as well, of course.
3. You can optionally apply a filter for choosing the files you apply this to – for e.g. *.cs files etc.

Summary

Using the Regular Expressions Search and Replace allows for replacing / inserting multiple lines of code within multiple source code files in your solution. All you have to do is make your search term RegEx friendly.

The post Visual Studio Replace multiple lines of code appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

Even if you have .NET framework 4.0 (or above) installed correctly, Visual Studio sometimes does not pick it up. This means that you will be unable to convert any of your projects to compile against 4.0 (by setting the ‘build target’ to 4.0 or above). Simply changing the ‘target platform’ setting in the web.config to 4.0 does not do anything. You actually need to go through Visual Studio’s –>Project Level –> Properties –> Build –> Target Framework (or Application—>TargetFramework) – and set it to the framework of choice. In my case, I DID NOT see 4.0 or 4.5 (in spite of having both of these frameworks installed on my machine).

MISSING Framework 4.0 and 4.5

First thing I learned was that Visual studio uses the following path to CHECK for these installed frameworks (it is the folder for referenced assemblies – referenced by VS, I am guessing):

C:\Program Files\Reference Assemblies\Microsoft\Framework\xxx

For each installed framework, there is a folder (v3.0, v3.5) as shown below containing the assemblies that VS needs for its tasks.

As you can see, v4.0 is missing. I had this issue on my computer – and re-installing the 4.0 framework did not address it.

This folder is needed only by Visual Studio, so I thought maybe reinstalling Visual Studio will do the trick.  That did not work either.

When this folder goes missing, it seems impossible to bring it back by doing a re-install.

TWO Solutions

Solution 1 (Recommended)

Try downloading and installing Visual studio 2013 (from here). That will install all the required .NET frameworks correctly – in places where Visual Studio needs to look for them.

Solution 2 (may work)

Another solution that worked for me was to copy this folder (v4.0 folder from another machine that had the v4.0 folder) – into the Framework folder above. This seemed to make Visual Studio happy and I could now pick v4.0 for my ‘target framework’ for my VS projects.

Summary

Visual Studio’s inability to pick up the correct .NET framework seems to be an annoyance – and re-installing BOTH Visual Studio and the framework does not seem to help. What worked for me was installing the latest version of Visual Studio (2013). You can also try the folder copying trick for a time saving solution. Once I installed VS 2013, I was able to see the correct framework versions in my ‘build target’ dropdown.

The post Visual studio does not display .NET 4.0 (or 4.5) framework option for target framework appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

You’ve just downloaded a project (from either codeproject or github or some other repository) – and opened it up in your current version of Visual Studio.

On trying to compile it, you encounter the following error:

AssemblyInfo.cs’ could not be opened (‘Unspecified error ‘)

This seems to occur for every project in your solution that contains an AssemblyInfo.cs. Simply put,  the assemblyinfo.cs contains ‘metadata’ (version number, guid etc.) for your assembly. This metadata is useful in uniquely identifying your assembly to all its consumers.

Workaround 1

Simply delete these assemblyinfo.cs files. If all you are trying to do is view sample source code, you do not really care about the versioning or COM interoperability (GUID) of the assembly. Your project should compile just fine after this deletion.

Workaround 2

If deleting the file is not an option – and you do need the metadata, simply delete the offending file – and create a new one. To create a new one, click on the ‘Properties’ folder in your project (see below). This should bring up the properties dialog. There should be an ‘Assembly Information’ button.

Now, the only thing the assembly information really needs is a GUID. From your Tools menu—>CreateGUID as shown below.

Click ‘Copy’ on the CreateGUID popup – and paste that content into the Assembly Information screen from the previous step. Delete the leading slashes in the GUID, since you do not need those.

Click OK – and you should be done. You will have an assemblyinfo with a GUID – and your project will compile just fine.

Summary

While uploading projects, the assemblyinfo.cs file often goes missing – and causes a compilation error for users who try downloading and compiling the project. The workaround is simple – either delete the file altogether (you don’t need it) – or delete and re-create it using the steps described in this post.

The post Source file ‘\Properties\AssemblyInfo.cs’ could not be opened (‘Unspecified error ‘) appeared first on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.