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?
Related
I need to know how to share assets like images and icons etc. between windows forms projects of the same solution using .NET6 and Visual Studio 2022?
The purpose is to change those assets in one place and have the changes replicated in all projects.
Thanks.
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 am developing multiple Windows Phone applications that vary only by the content of several files. Applications share the same logic therefore I created a project and multiple folders, one for each app variation with variant's assets and files and moved them to separate location. To compile project I copy over files and follow a standard compilation process with Visual Studio.
Now there are only 5 application variations and for now it is suiting solution, but the number is expected to grow to 50 and more. I would like to automate the process and my current idea is to write a batch script to copy files from variation folder, overwrite project files, compile app with a script and to copy xap package to another location.
My two questions are:
Is my idea good resolution of the problem or is there a more graceful way to do this I am not aware of? (manage and develop multiple app variations)
How would I compile windows phone app from cmd?
I think your problem is valid. I ran into a similar requirement in the past (only that it was for Windows 8 Store Apps), and what I did was the following:
Create a "core" project and moved all the shared logic to that project. I then created a sample app project, referenced the core project and made sure the sample app worked the way I wanted it to.
Finally, I converted the sample app into a Visual Studio template. What this basically does is take the project code and create a Visual Studio template you can reuse.
Read more about it here.
Some work needed to be done within the template source code in order to get some of the dynamic parts like app name into specific locations within the code. For example, you can change a class namespace to be the project's namespace by applying the following code in tour class:
namespace $safeprojectname$
You can read more about template parameters here.
Hope it helps.
To compile windows phone applications or any .NET app from command line you should use
msbuild.exe
. You can find more information and samples here.
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.
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?