How I can clean the temporary Files in Visual Studio 2012?

Question

0.00/5 (No votes)

See more:

How I can clean the temporary Files in Visual Studio 2012 and how I can locate NullReferenceException in my project WebForms?

Posted 14-Jun-15 23:11pm

Member 11765235

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Andy Lanng · Accepted Answer · 2015-06-14T23:35:00

you have two questions.

Q1: How do I clear the %tmp% folder in VS 2012?

Answer: VS 2012 has no temporary files that you can delete. You might have some being created by your program but that would be in VB.Net or C#. You have not told us which. Either way, you shouldn't.

The point of the %tmp% folder is that the files will only exist as long as they need to. As soon as the var that uses the file goes out-of-scope, then the GC will clean it up for you on the next pass.

Why do you ask? Are you having problems with temp files?

Q2: How do I locate a NullReferenceException?
There should be a Stack Trace with the error. This should tell you where the exception occurred, but it does not tell you what item was null. Usually it's obvious but sometimes it a little more obscure. I suggest you use the stack-track to locate the likely null candidate and add some error checking beforhand.

For example:

C#

//C#

//instead of
return somemethod().ToString();

//handle the error before it can occur
var myvar = somemethod();
if(myvar==null)
  return null;
return myvar.ToString();

This is how I handle any possible null value.