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.
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'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?
Well I think this might be the final question for this Silverlight 5 project.
I just installed the InstallShield Limited Edition for Visual Studio 2012 and no I am faced with a dilemma. Which installation project to use?
The project is a Silverlight WCF application and I hope that is a simple enough description to go on. What is required is that the client side sees the web environment and the server side has the WCF services (of course).
I have not worked with this kind of project before so there may be some configuring certain pieces to go certain places and I am very unfamiliar with how all this works. The Installer projects available are as follows:
Setup Project,
Merge Module Project,
Setup Library Project,
Bootstrapper Project,
C# Custom Action Project,
VB Custom Action Project,
C++ Custom Action Project
Which one would I use to create an Installer for this Silverlight 5 WCF solution?
I want to create a Visual Studio 2010 setup project that deploys some files to a folder where my application can use it from. I want it so, that all users have the same files, and that they also could manipulate them without admin rights.
Thus, "Common Application Data Folder"* as described in this MSDN article, seems fine.
However, in my Visual Studio 2010 setup project I did not find the "Common Application Data Folder" available in the "Add special Folder..." drop down menu.
I have a .NET 4.0 WinForms app and see no reason why this does not show up.
The user's common application data folder is available but does not match my intended use.
Thanks for any hints!
Visual Studio setup projects do not have a predefined folder for common Application Data. However, you can install files in it like this:
add a custom folder and select it
in its Properties pane set DefaultLocation to:
[CommonAppDataFolder]
in this folder add the files you want installed in common Application Data
During install CommonAppDataFolder will be automatically resolved by Windows Installer.
A more specific solution might be to set the DefaultLocation property to:
[CommonAppDataFolder][Manufacturer]\[ProductName]
Manufacturer and ProductName will be resolved from the values you assign to the corresponding properties of the setup project.
I want to pack my file in to a single executable file "setup.exe", my application is written in c# and WPF, I know that there are a lot of applications out in the store for creating a installation pack, but the point is which one would help me to build my installation pack just like Devexpress dose ?
For an UI similar to DevExpress you will need a setup authoring tool which offers an external UI and rich graphics.
Advanced Installer and InstallShield have some great UI themes which can get you started. You can also find a list of setup tools here:
http://en.wikipedia.org/wiki/List_of_installation_software
You'll probably have to roll a custom solution for this one. I expect nothing less of the Devexpress team then creating their own installer.
If you're application is not heavily bound into the registry and all kind of windows folders it should not be that hard to create an application that extracts some files into a directory and create some great UI while copying.