Cosmos

dan/Cosmos

mirror of https://github.com/danbulant/Cosmos synced 2026-05-19 20:39:01 +00:00

History

kudzu_cp 46ce6d7543		2011-06-27 04:11:39 +00:00
..
Properties		2011-06-19 12:49:42 +00:00
App.xaml		2011-06-19 12:49:42 +00:00
App.xaml.cs		2011-06-19 12:49:42 +00:00
AssemblyUC.xaml		2011-06-26 23:08:32 +00:00
AssemblyUC.xaml.cs		2011-06-26 23:45:48 +00:00
Cosmos.VS.Debug.csproj		2011-06-26 04:45:55 +00:00
Cosmos.VS.Debug.csproj.vspscc		2011-06-19 12:49:42 +00:00
MainWindow.xaml		2011-06-26 23:45:48 +00:00
MainWindow.xaml.cs		2011-06-27 04:11:39 +00:00
PipeThread.cs	Removed warning.	2011-06-27 00:39:47 +00:00
ReadMe.html		2011-06-19 15:10:11 +00:00
RegistersUC.xaml	UI changes to register display.	2011-06-27 01:48:52 +00:00
RegistersUC.xaml.cs	UI changes to register display.	2011-06-27 01:48:52 +00:00
StackUC.xaml		2011-06-26 21:10:48 +00:00
StackUC.xaml.cs		2011-06-27 04:11:39 +00:00

ReadMe.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
	<head>
		<title></title>
	</head>
	<body>
	
	  <p>
      Building a VS Tool Window package is easy. Deploying it apparently is not, and 
      because we deploy even at dev time with a setup.exe, we need to deploy it. VS 
      Tool Window packages use WPF UserControls though, so for now we use this 
      separate standalone EXE which uses WPF UserControls.</p>
    <p>
      This is also easier to debug because it can just be rebuilt without affecting 
      Visual Studio. Maybe in the future the VSIP package can just reference this 
      package to and use the user controls, so for debugging and development of this 
      project, it could be used instead.</p>
    <p>
      For nearly all purposes this is better than our GDB client and nearly deprecates 
      our GDB client. However our GDB client is important to retain for debuggin the 
      DebugStub. DebugStub cannot debug itself, and even if it could, if its not 
      working correctly then neither would this debug tool as it relies on DebugStub.</p>
	
	</body>
</html>