Mark Adamson
Mark Adamson
> @mungojam Does your PR resolve the CreateDump.exe shortcut problem too? @AArnott as you found and commented on the PR, it does. Thanks for publishing a version of the package...
@anaisbetts this one seems to be popular, do you think you will have a chance to look at this?
> Part 1 is an easy win, I'd take that PR. I could split the PR if that would help, but note that with just Part 1, people would need...
> > Would it help if it somehow detected for sure that the .exe is a .net core wrapper exe? > > Yeah, I think that would be a bit...
> @mungojam Taking a quick look, I noticed that in our project in the properties for the .exe there is a property called "Original filename". It has the .dll name...
> I would actually try to analyze the executable itself to try to find some sign that it is a renamed dotnet.exe. I'll look into it soon A few things...
> @mungojam Were you going to split the PR? With Part 1 at least we would be able to move forward with marking one of the exes in our app...
Note that .net 6 resolves the specific createdump problem to a degree as it no longer lists it as a dependency so it can be deleted as a post build,...
@anaisbetts I've just spotted the comments on https://github.com/Squirrel/Squirrel.Windows/pull/1752#issuecomment-933437822 about this one. I wonder if I can help resolve the concern around it. It only goes looking for the partner dll...
reading the design meeting notes, if the eventual outcome is that we can also replace: `var things = new [] { "Car", "Motorbike", "Cab" };` with `var things = ["Car",...