Skip to content

Commit cd49ab1

Browse files
committed
Version and readme updates
1 parent d2ef7cd commit cd49ab1

File tree

2 files changed

+7
-4
lines changed

2 files changed

+7
-4
lines changed

JitMagic/JitMagic/JitMagic.csproj

+4-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,10 @@
1414
<Platforms>x64</Platforms>
1515
<DefineConstants>$(DefineConstants);IS_WPF</DefineConstants>
1616
<RepositoryUrl>https://github.com/mrexodia/JitMagic</RepositoryUrl>
17-
<RepositoryType>git</RepositoryType>
17+
<RepositoryType>git</RepositoryType>
18+
<AssemblyVersion>2.0.0.0</AssemblyVersion>
19+
<FileVersion>$(AssemblyVersion)</FileVersion>
20+
<Version>$(AssemblyVersion)</Version>
1821
</PropertyGroup>
1922

2023

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
21
# JitMagic
32

4-
JitMagic is a tool that allows you to have multiple Just-In-Time debuggers at once. It is able to also pass JIT operations off to other JIT debuggers like Visual Studio's JIT choice form.
3+
JitMagic is a tool that allows you to have multiple Just-In-Time debuggers at once. It is able to also pass JIT operations off to other JIT debuggers like Visual Studio's JIT choice form. There should not be any functionality loss with a debugger by switching to JitMagic (full AeDebug featureset and eventing supported).
54

65
![Screenshot](https://raw.githubusercontent.com/mrexodia/JitMagic/master/screenshot.png "Screenshot")
76

7+
[![](https://github.com/mrexodia/JitMagic/workflows/continuous/badge.svg)](https://github.com/mrexodia/JitMagic/actions/workflows/continuous.yml?query=branch%3Amaster)
88
<!-- MarkdownTOC -->
99

1010
- [Features](#features)
@@ -56,7 +56,7 @@ Run `JitMigic.exe --unregister` or launch JitMigic without any command line args
5656
## For Debugger Developers
5757
### Adding your debugger to JitMagic
5858

59-
Do you have a debugger you want JitMagic to offer? Great. For the most part if your app can already be used as a native AeDebug app it should work seamlessly with JitMagic. If your app does not support AeDebug style debugging already see [#How your debugger should behave] below for details on how it may still work. The recommend way of registering yourself with JitMagic is to check the AeDebug Debugger key `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger` if it contains JitMagic.exe offer your users the option to add the debugger to JitMagic.
59+
Do you have a debugger you want JitMagic to offer? Great. For the most part if your app can already be used as a native AeDebug app it should work seamlessly with JitMagic. If your app does not support AeDebug style debugging already see [How your debugger should behave](#how-your-debugger-should-behave) below for details on how it may still work. The recommend way of registering yourself with JitMagic is to check the AeDebug Debugger key `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger` if it contains JitMagic.exe offer your users the option to add the debugger to JitMagic.
6060

6161
If they want to proceed take the executable path for JitMagic.exe (from the Debugger registry key you can extract its path similar to
6262
```csharp

0 commit comments

Comments
 (0)