VS Project wont go in debug - no compile errors on VS

run dotnet run project file name at the root folder
now you will see the error

Access to the path errors

delete bin and obj folders
make sure you are running as Admin

Debug Unit Test in VS

1. Press CTRL+R and then CTRL+T.

vs - command line args

wont work if clickonce is enabled

to avoid distributed transaction errors during debugging

on the callee comment out :

/*[OperationBehavior(TransactionScopeRequired = true,
TransactionAutoComplete = true)]*/

debugging a windows service

follow this pattern in program file

#if DEBUG

            MethodInfo mi = qCenterService.GetType().GetMethod("OnStart", BindingFlags.DeclaredOnly | BindingFlags.Instance | BindingFlags.InvokeMethod | BindingFlags.NonPublic);

            mi.Invoke(BlahService, new object[] { new string[0] });

            Console.ReadLine();

#else

                     ServiceBase.Run(new ServiceBase[] { BlahService });

#endif

New Laptop blues VS - bad filename or volume name

difficult week

finally got it - cleared workspaces (including remote) and downloaded everything again

web installer hung

i ran reset from command line

installing mvc 4

on vs 2012 kept on failing because of a lack of a patch on vs 2010 (huh?)
i installed mvc 3 first and all was good

when to use x86 on a VS build

I needed that for creating an exe that had to work on 64 bit bit still had references to 32 bit

adding existing files to vs project

dont add the designer just the plain cs

report viewer in 2013 express

pure hell

through this i ran this

The type or namespace name 'Blah' does not exist in the namespace 'heh.heh' (are you missing an assembly reference?)

I was getting this in a team city build because the dll was directly referenced instead of the project being referenced.

This has great consequences with release builds
As I understand it,only with a project reference is the bin created

assembly generation failed strong name

all referenced dll's need to be signed if the calling assembly is signed

metadata could not be found

could be a red herring - fix the other errors first

How to stop a build in VS

ctrl-break

Debug.Writeline

only works if the debug symbol is declared

Unexpected Error creating debug information file

i had this while trying to compile a project that was attached to a process

This document is opened by another project

i was getting this message on a class - I had added a member class to the class and it was being picked up in only some locations - somehow there was a connection

my advice - close VS - even compiling solution did not help

vs 2012 project use in 2010

this is all you need to change

<TargetFrameworkVersion>v4.0</TargetFrameworkVersion>