Repository navigation
ILens 13
- Every answer that reads method code ends with a line naming the methods whose code breaks off inside an instruction:
Not checked:inanalyze,find_harmony_dependenciesandsearch_code,Not compared:incompare, with five named and the rest counted read_byandassigned_bylist a method that takes the field's address before its code breaks off as one that may read and may write itfind_harmony_dependencieskeeps what a method names before its code breaks offfind_types,find_methodsandlist_membersnow find a generic type or method by its name as ILens writes it:name_containsGet<T>,Get<int>orCache<>lists the types or methods whose name ends in the text before the brackets and that have as many type parameters of their own, where it found nothing beforefind_methods'type_name_containsnow reads such brackets the same way, so a class named asfind_methodsorfind_harmony_dependencieswrites it, such asCache<>orCache<int>, lists its methodslist_membersnow also finds a generic class's constructor by the class's name with its brackets, such asCache<>- A class whose name holds angle brackets, as C++/CLI names the class of a template instance, can now be asked for by the name
find_typeslists, intype_name,parameter_typesandreturn_typealike analyzewithused_byon such a class lists its users instead of answering that the assembly neither defines nor references it, also where only an attribute'stypeofargument names itanalyzewithextension_methodsnow answers for an array of such a class that the assembly names nowhere- The error for such a class named without its namespace now names the class
analyzewithcall_sitesnow shortens a call longer than 300 characters: the bodies of the lambdas and anonymous methods it passes, then the entries of the objects and lists it fills, are written as..., the largest first, until the call fits, and a call that cannot be made to fit so is cut at 300 characters as it stands; a line after the list counts the shortened calls- With
parameter_name,call_sitesshortens an argument longer than 300 characters the same way, but an argument that is itself a lambda or an anonymous method keeps its body and is cut, so that its start stays readable analyzewithcall_sitesnow lists the calls Visual Basic code makes to an override by reading or setting a property, using an indexer, runningFor Eachor filling a collection initializer, where the member it overrides is in another library, which it reported as not shown; the same holds for F# code where its compiler names the override, and for C# code's calls of an override that returns a more specific type, in a property pattern as wellcall_sitesnow lists a call Visual Basic makes to an override without virtual dispatch, as throughMyClass, once, without lines saying that it was not shown or that the decompiled C# holds more calls than the ILanalyzewithcall_sitesnow lists the call an entry of an index initializer makes, such as[0] = iteminnew Rack { [0] = item }, once, as the assignment it is; it listed the entry a second time in braces, withnullordefaultas the value, and added aCheck:line saying that the decompiled C# shows more calls than the IL holdsanalyze'simplemented_byandimplementsnow name the override that runs where a class lists an interface and the member that matches the interface member is overridden, in that class or a class above it, with a more specific return type, or withdynamicwhere the interface member returnsobject:implemented_byalso listed the overridden member for that class and listed an override above it without the class,implementsanswered that such an override above it implemented nothing and that the overridden member implemented the interface member for that class, and theImplementation:line ofused_by,read_by,assigned_byandcall_sitesfollowedimplementsanalyze'simplemented_byandimplementsno longer name a class member as implementing an interface member that no class can implement, a static member that is neither abstract nor virtual, a sealed member or a private member, where the class or its base class declares a public member of its name:implemented_bylisted that member,implementsnamed the interface member, and the usage answers ended with a line saying that code can call the interface member insteadanalyzewithimplementsnow ends with aNot checked:line naming an interface that ILens could not read where a class below the member's class lists it and can bind the member by name, andused_by,read_by,assigned_byandcall_siteson such a member end with the line saying that whether it implements an interface member was not checked:implementsanswered that the member implemented no interface member, or listed only those of the interfaces it read, and the usage answers ended without a lineanalyze'sused_by,call_sitesandusesnow answer about an assembly whose code names an array type without dimensions, which no compiler writes but a tool that guards an assembly against decompiling can, and pass over such a reference, which names no method that exists:used_byandcall_siteson a method named like a member the code names through such an array type, anduseson a method whose code names one, ended in an error saying that dimensions must be positive- A library built for .NET Core or .NET 5 and later is now read against the installed .NET where an allowed folder holds an old framework, such as a Unity game's library folder or Windows' .NET Framework folder, and no .NET runtime as new as the library's:
decompilewrote enum flags there as numbers and added casts,list_memberslisted the old framework's inherited members,useswroteinandref readonlyparameters asref, andanalyze'simplementsandimplemented_byleft out a member that implements an interface member whose parameter's class is named through bothnetstandardandSystem.Runtime - A
.deps.jsonbeside an inspected assembly now leads ILens only into the NuGet package folders: a folder it names elsewhere, by an absolute path, by..steps or as a share on another computer, is neither read nor looked at, where such a file could make ILens read an assembly from anywhere on the disk and make Windows connect to the computer it named as soon as any tool opened the assembly - A reference whose name is a path, such as
..\Outside\Libor a share on another computer, is no longer looked up: answers report its library as not loaded, where ILens read the assembly the path led to analyze'sinstantiated_by,exposed_byandapplied_toanswer with an error naming the reason on an assembly that has such a reference, or whose.deps.jsonleads out of the package folders, is a link or is not valid JSON, since they run on a reference search of their own that would follow it- A
.deps.jsonthat is not valid JSON no longer makes every tool fail on the assembly beside it - After an assembly is rebuilt or replaced at the same path, the next call now answers from the new build: a server answered from the build it had read first until it was restarted, so a type renamed in the rebuild was still listed under its old name,
decompileandlist_membersdid not find the new one, andsearch_codesearched the old code - A library that an inspected assembly references from an allowed folder is no longer locked while ILens runs: a build can write over it, and the next call on the assembly that references it answers from the new build, where the build failed with a message that the file was in use and ILens answered from the old build until it was restarted
- ILens now holds each such library in memory once for all the assemblies that reference that build of it: with 20 mods open beside a game's libraries the server used 106 to 110 MB where it used 143 MB, while an assembly whose references lie in a self-contained application's folder, beside its own copy of .NET, takes about 35 MB more
- Asking what a method uses no longer builds a second copy of the assembly's type information, which an open assembly kept for as long as it stayed open, about 2.6 MB for a large one
- ILens now runs on .NET 10.0.15, the runtime its binary bundles
- When Windows refuses to start ILens during installation, the PowerShell installer now says why and where
ILens.exestays, names Smart App Control where an Application Control policy blocked the unsigned file, and links the user guide's installation troubleshooting - The PowerShell installer no longer advises allowing ILens in SmartScreen when ILens starts but exits with an error
- Upgrading with the PowerShell installer now checks that the new ILens starts before it touches the installed one, so that a new version Windows blocks or antivirus software removes leaves the installed version running
- The PowerShell installer stops running ILens servers only once the new version has started, and no longer leaves a half-deleted install when a file of it is in use
- The PowerShell uninstaller also removes the folders an interrupted installer run left beside the install
- The user guide describes every tool's parameters, answers and errors as this release gives them, and the guide and the README explain how Windows Smart App Control can refuse to start ILens