I created a new app with steroids. literally deployed and built it for android. but when I downloaded my app, it was roughly 7mbs.
Why is that so much large file? is there any way to reduce it?
-note: I didn't add any extra files to my application. just steroids default starting template.
Related
I'm using DesktopAppConverter to convert my WPF application into a windows store compatible app. Right now I'm able to get the AppX built but the problem is to do with my application assets.
At the moment, DesktopAppConverter is taking my existing Icon (which looks great in WPF) and using it to somehow create all the different Assets at different resolutions for the UWP app. The icons it creates are coming out looking terrible, really blocky and clearly upscaled.
The way I'm looking at it is that there's 2 options.
1 - I specify a really large Icon file in my WPF app that might somehow end up being scaled better inside DesktopAppConverter. The problem here is that with a large resolution Ico file, I end up with a crazy large file (Ico's don't compress very well from what I understand).
2 - I specify a folder of correctly scaled assets (created using UWP Tile Generator) when building through DesktopAppConverter. This is what I'd like to do. I don't really want to be tweaking my Assets every time.
The 3rd choice is the one I'm heading towards, but don't really want to do. It involves building with AppX, then replacing the assets, then using MakeAppX, then re-signing with the SignTool. All of that seems really unnecessary, so I'm hoping someone from MSFT can let me know I'm missing something fundamental.
Thanks.
The easiest way to handle the visual assets for your app package is to use the package manifest editor in Visual Studio 2017.
To use it for your converted app, create an empty UWP project and add the output of the conversion (incl. your appx manifest) in this project. Now you can use the editor to manage the visual assets, build your packages for store submission and much more.
Here is a document that describes the process:
https://learn.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-packaging-dot-net
Thanks,
Stefan Wick - Windows Developer Platform
I have to create a universal app from scratch. First the classic app, and at some point in the future, the modern app. I have generated the app using Cmd.
I have implemented the basics I need for the classic app, split off everything that can be reused in the modern app and put it into the shared directory. The problem is that now, when I compile with Cmd, I get the error that dependencies are missing (because views are missing in the modern app that I have implemented for classic only, but are required in shared code).
The classic app compiles find, but modern doesn't, and if there are ever errors in the classic app build process, no one will notice, because modern throws errors.
Can I tell Cmd on the command line to only compile the classic toolkit?
In ExtJS 6 we can generate app for classic and modern separately in a similar fashion we can can build app separately for classic and modern.
you can build like this.
sencha app build -c classic.
Edit the app.json file, and remove the section about the modern toolkit in the builds profile section; you can re-instate it when you're ready to build the modern part again.
I'm creating a larger project that will need to be able to grow considerably over time and am having some trouble with AngularJS project structure. I have found several helpful tutorials about project structure that work very will with a single project but what I would like to do is have several Visual Studio projects and have a "Shell" project with an ng-view call the other projects to display within the view. The structure would look a little like this.
Root
Shell Project (This is the root page with the ng-view loading the other pages)
Web App 1 Project
Web App 2 Project
Group of Apps Folder
Web App 3 Project
Web App 4 Project
Web App 5 Project
Most of the project templates I have seen have a single project and just have a large number of sub folders within the project. I would prefer to not go with this style because like I stated before this project will grow to a very large size and I would like to keep it as manageable as possible. Is what I am trying to do possible or is there a better way to setup the project that AngularJS or Visual Studio is designed to use?
I have a WPF application, which until now - was an browser-based application. Now - due some changes in project i want to be able to run that application as desktop application. My question is - is it possible, that by using single CSProj file, and adding extra build configuration, to have single WPF Project which would build to desktop and web-based app? I want to be able to choose between options:
Debug (application is building as web-WPF-app, and is launched in web browser)
Release (same)
Debug Desktop (application is building as desktop-WPF-app, and is launched as client-desktop app)
Release Desktop (same)
Kind regards
Szymon D.
The output type of a project is independent from the Build configuration in Visual Studio.
Also, why? Why not factor out the things that are shared into DLLs and creating separate projects per output type?
Is it possible to build silverlight application in on-demand manner. I have lot of silverlight applications to be shipped. I would like to ship the project files alone. Based on some user interaction, I would like to generate the XAP.
You thought about using a NANT script to compile your project and grab the output xap file?