-
We could implement an option `expand` to `shallow` that allowed you to specify components that you'd like to "expand" the shallow render tree into, while all other components are considered leaf nodes…
-
```
OAuthConsumer appears to have been written to assume GC, and leaks exuberantly
when run in a
non-GC environment. I've got a patch to add mixed-mode memory management, which
was
pleasantly stra…
-
```
OAuthConsumer appears to have been written to assume GC, and leaks exuberantly
when run in a
non-GC environment. I've got a patch to add mixed-mode memory management, which
was
pleasantly stra…
-
```
OAuthConsumer appears to have been written to assume GC, and leaks exuberantly
when run in a
non-GC environment. I've got a patch to add mixed-mode memory management, which
was
pleasantly stra…
-
```
OAuthConsumer appears to have been written to assume GC, and leaks exuberantly
when run in a
non-GC environment. I've got a patch to add mixed-mode memory management, which
was
pleasantly stra…
-
```
OAuthConsumer appears to have been written to assume GC, and leaks exuberantly
when run in a
non-GC environment. I've got a patch to add mixed-mode memory management, which
was
pleasantly stra…
-
Is there any intent to support mixed mode assemblies, those containing unmanaged code in il-repack? This would be very useful even if only one input assembly was allowed to contain unmanaged code whic…
-
```
OAuthConsumer appears to have been written to assume GC, and leaks exuberantly
when run in a
non-GC environment. I've got a patch to add mixed-mode memory management, which
was
pleasantly stra…
-
```
OAuthConsumer appears to have been written to assume GC, and leaks exuberantly
when run in a
non-GC environment. I've got a patch to add mixed-mode memory management, which
was
pleasantly stra…
-
```
OAuthConsumer appears to have been written to assume GC, and leaks exuberantly
when run in a
non-GC environment. I've got a patch to add mixed-mode memory management, which
was
pleasantly stra…