Cosmos/source2/Kernel/Debug/Cosmos.Debug.Kernel
EdwardNutting_cp bac3f98d56 VS2013 Support
This is relatively stable but no to be considered complete. Currently supported:
1. Installing user/dev kit (as normal)
2. Creating C#/VB/F# projects (latter 2 untested)
3. Debugging a Cosmos project - see limitations list below.

Debugging limitations:
1. Breakpoints sometimes fail to be hit. Only known thing that may help is recompile everything.
2. Specific breakpoint failure case: If you try and place a breakpoint on or after a "while(true)" statement it is extremely unreliable.

Other limitations:
1. VMWare occasionally breaks. If you get "Internal error" messages, or if VS crashes (don't let Windows "fix" it) or if VMWare fails to load properly there is only one known & reliable solution: Re-run the VMWare installer and hit "Repair". No restart required. You won't lose your VMs or settings (AFAI can tell).

If it all breaks, feel free to rant at it ;)
2013-11-06 21:01:49 +00:00
..
Properties unit format of assemblyinfos 2010-09-09 20:54:55 +00:00
Cosmos.Debug.Kernel.csproj VS2013 Support 2013-11-06 21:01:49 +00:00
Cosmos.Debug.Kernel.csproj.vspscc renaming all, except vspackage 2010-09-04 19:07:11 +00:00
Cosmos.snk Cosmos.Debug.Kernel separation. 2010-08-20 00:01:09 +00:00
Debugger.cs 2011-03-02 23:33:54 +00:00
ReadMe.html Cosmos.Debug.Kernel separation. 2010-08-20 00:01:09 +00:00

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
	<head>
		<title></title>
	</head>
	<body>
	
	    <p>
            Cosmos.Debug.Kernel is a special assembly and is not in any ring. It can also be 
            accessed from any ring. Special care must be kept to keep only debugging 
            functions in this assembly, and not to allow such ringless behaviour to be 
            implemented in other assemblies.</p>
        <p>
            Cosmos.Debug.Kernel must not contain any references to any kernel units. All 
            references from kernel units must be incoming only.</p>
	
	</body>
</html>