![]() ![]() Some installers do not look at the setting configured in step 2 (but some might). This will copy it to bin/debug or bin/release and so the file will be available when running in debug or release mode on your development machine using your IDE.Ĭonfigure your installer tool to copy the file into the installation directory e.g. sln and change the properties of the file to " Copy to Output Directory". From there you can find your file easily.Īdd the file to your. Location to get the path of the currently executing. Steps to get this to work in development and prod: Or you can put the file in a subfolder that also resides where the app is installed. So you can put it in the same folder as the app and you can get the file by using the currently executing assembly's location. If only the app needs access, then that constant place is whereever your app is installed. I'm going to assume the answer is no and only the application needs access to these files? If the users need these files too then please comment with a bit more info. It depends on if the user also needs access to these files outside of the app. How to place those files in a location that will work for both development and deployment? In the case where I need to load files in the normal app usage where to save the files that I can get to reliably? Everybody has different my documents folders, etc. To add some additional file I think I just had add the file as a Project Output to the File System Editor. ![]() Although the URL says 2017 it is also for VS 2019 and is actively maintained by MSFT.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |