希望ModernFlyouts可以提供64位版本的应用
Hope ModernFlyouts can provide 64bit version of the application
We do provide x64 bit build of this app since v0.8.2 (I don't know if it's out on the Store).
You may get a proper x64 build with the next release.
很好,我很期待在新的版本——0.8.2里看见64位的ModernFlyouts,希望也能够在Microsoft Store看见它发布
Very good, I am looking forward to in the new version - 0.8.2 saw 64bit ModernFlyouts, hope can also be released at the Microsoft Store to see it
Great! Thanks for your patience!
@ShankarBUS
I have seen this architecture mess up a lot of times. Sometimes, the app supports all 32, 64 bit CPUs, sometimes only 32. Why does it keep happening?
希望ModernFlyouts可以提供64位版本的应用
Hope ModernFlyouts can provide 64bit version of the application
If your PC has an Intel or AMD chip inside, it would run the app without any problem though.
我的电脑是Intel64位的 My computer is Intel64
处理器 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz 2.81 GHz
不出意外可以正常运行 No accident can run normally
@Cyberdroid1,
Because we're still newbies!
To be honest, I've never used any configuration other than AnyCPU previously.
.NET assemblies with AnyCPU configuration can run on any CPUs (it's pretty obvious).
The .NET bootstrapper (the normal *.exe built by the compiler) loads the appropriate runtime depending on the system's architecture (it does the work for us).
If we were to publish our app as "framework-independent" [i.e. .NET 5 runtime (x64 or x86, it depends on the target system) has to be preinstalled], we can just publish a small package (just 2 MB) with AnyCPU config. No additional work.
But we can't force the users to download and install the .NET runtime by themselves. They would just not use our app due to this burden. _(Store could automatically do this. MSIX doesn't do this too. This is why Power Toys don't use the Store and MSIX)_
v0.3 and previous versions were all based on .NET Framework (preinstalled on all Windows 10 OSes. uNiVeRsAl fAcTO!). So, we didn't have to force the users to install the .NET runtime.
It all started since we made the jump to .NET Core. Since then, we are publishing this app as "self-contained" (bundling a copy .NET runtime together with our app. Results in an increased package size 2 MB -> 60 MB) to reduce end users' burden.
While publishing as self-contained we have to specify which runtime we are targeting (either x86 or x64). So no AnyCPU and no easy procedures. Thus, we have to publish this app twice (once for each arch. Takes a lot of time 🙄) and the packager will bundle them into a mega package and it will provide the necessary package to the user.
@Samuel12321, hard coded the package to be x86 previously and we're smashing our heads at the wall wondering what went wrong.
See #41 and https://github.com/ShankarBUS/ModernFlyouts/commit/981017e4f726211e1c8c95188fdcf64f40aab15d#commitcomment-44370722
Later we figured it out and fixed it during the v0.8.2 release
The End!
Gotcha! Sorry for making you type all that 😅. I feel sorry both for you and your computer's keyboard.
as @ShankarBUS said, fixed in 0.8.2, which you should get soon. (currently waiting on store certification)