Timeline for Are Windows Store Apps in a VM and can they be identified by PE header info?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2017 at 9:12 | comment | added | Chris Tsiakoulas | Microsoft promotes .Net languages to develop apps for their app store, so the greatest number actually is. There are some well-known older programs included in the store, which are mostly for computers that they were included as-are, so these might need different tools. But almos 90% of apps is in .Net, so ILSpy, a good hew editor and some PE header tools is the best way to wander around the code. | |
| Jun 6, 2017 at 7:43 | comment | added | Paweł Łukasik | "ALWAYS" might not be the correct but word here as I know that at some point it was possible to write them in JS too. | |
| Jun 6, 2017 at 7:38 | comment | added | the_endian | dnSpy can't get any .NET symbols from them at all. Just gives PE Header. | |
| Jun 6, 2017 at 7:32 | comment | added | the_endian | Are you sure about this that they are ALWAYS .NET? I ask because I'm used to .NET having a single import of _corlibmain which fires up the CLR stuff. However, many of these store apps contain standard W32 imports as well. ILSpy also cannot open any of them, it says they "are not managed assemblies." I'm going to try dnSpy next. You're probably right it's just these have different characteristics from regular .NET assemblies it seems. Also, by .NET are you also meaning Visual C++ managed? In Detect-It-Easy a lot of these show as VC++ too. | |
| Jun 6, 2017 at 6:53 | history | answered | Paweł Łukasik | CC BY-SA 3.0 |