Visual C# crash when I try to open or create new project / files

I have installed Visual Studio 2010 (VB.net) and work without problem, but C# 4.0 don't work.

Attached some Screenshot about the errors.

I have installed C# 4.0 and not work and after uninstall it I was installed C# 4.0 (express edition) with some result.

I have win7 and 4.0 framework installed.

Someone can help me to solve this problem ?
error1.png
error2.png
error3.png
error4.png
luca345Asked:
Who is Participating?
 
AndyAinscowFreelance programmer / ConsultantCommented:
Looking at your messages and the 4th picture.
There seems to be a problem with the target framework (of .net) for the app - version 4 is specified BUT the highest version you have available is 3.5


What I would suggest is to do a complete uninstall of the express version of C# and VS 2010.
Reboot.  Now do a complete install of VS 2010.
Once that is done try to create a new C# project using the .net 4 framework and see if that works OK.
Hopefully it will.  (This current project might be corrupt somehow - I'd test a completely new project before attempting to open/compile this one again).
0
 
luca345Author Commented:
I' have installed the VS SP1 and now there is no crash, the warring is also present but the application run.

Thank you !
0
 
SimplistCommented:
You are missing the right framework. Re-install .net framework 4. Apply all microsoft updates after that.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
luca345Author Commented:
Yes. I will do, thank you !

P.S.

Do you known if exist a way do prevent the debug in some specific module ?
0
 
SimplistCommented:
While debugging you will find in the Debug entry of your Main menu options like "Step Into F10", "Step Over F11" and "Step Out Shift+F11" that will behave differently on a call to a specific module. 1st option will debug the statement, 2nd option will just execute the statement without debugging and stop on the next, last option will execute all remaining statements of the current module and stop on the first statement following the call to the module you were in.
Step through your code or place breakpoints to debug the parts of your code to investigate why it creates errors in spite of your excellent program design.
0
 
luca345Author Commented:
Thank you , but I mean at run time (some lines in the module)
0
 
SimplistCommented:
Sorry, never encountered that option. You'd better start another thread for that question.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.