Ethe only problem is the files I have are not opening when new user installs the app
CI'm going to assume that your installer does not place the PDF files in
C:\Users\asus\source\repos\... etc?EI am creating installer by Microsft Visual Studio installer project
Einside visual studio
Ebut in this picture I have delated it
CDo you understand what the problem is?
Eyes I do but I am having hard time to explain bro
CYou're trying to open the file
C:\Users\asus\source\repos\..., but if your installer hasn't created that exact file (and I doubt it's creating new users), then obviously that file won't existEyeah
Ehow can I fix it
COK, so you understand that the problem isn't the installer? The problem is that your application hard-codes the PDF path, to a path on your (and only your) computer
CDon't "bro" me please
Eoke sory
Eyeah problems with path
Eexactly
CSo, You want to tell your application to open the path relative to where your exe is, and not a fixed path
Eyess
CSo put your PDFs next to your exe (or in a folder next to your exe).
AppContext.BaseDirectory is the folder which contains your exe. So use Path.Join(AppContext.BaseDirectory, "Files", "Test1.pdf") etcEhow can I do that, I mean it is my first project and I am novice
EAi also said that to me
CYou can tell VS to copy the PDFs next to your exe. Add the PDFs to your visual studio project, then right-click, properties, and set "Copy to Output Directory" to "Copy if newer"
Eis there any videos if possible
Erelated to this topic
EI will learn and come back
AVideo about what?
AHow to right-click the file and change it's properties?
Edoing this in my project
Exd
CKids these days... You need to learn by doing. Play with things. Click around, see what the options are.
Eokey let me try then
EI will come back
CAdd the PDFs to your project as I described. Build your project, and see for yourself whether VS is putting them into the right place on build
CThen start updating your application to construct paths relative to
AppContext.BaseDirectory. Write some code, see what paths it constructs (have a look in the debugger), and if it's not right keep fixing it until it worksEshould I rewrite each path, I mean I have about 40-50 PDFs and path for each of them( sorry if it went off topic)
CWhat do you think?
AIf there's this many, you should probably consider enumerating all files in the directory, looping through that, and doing whatever you need to do with those files in a loop
EI have 10 hour experience so far sorry If I sound stupid(
Eokey I will try
AThat's a very complex project to be making as your first dip into C#
AYou start with a "guess a number" in a console, not with something that has an installer
Eagree
Ebut I have almost finished it
Ebut I just want it share in Installer format
Erather than bunch of files
A$singlefile
Mdotnet publish -c Release -r <runtime identifier> -p:PublishSingleFile=true Use of
-p:PublishSingleFile=true implies --self-contained true. Add --self-contained false to publish as runtime-dependent.-r RID and -p:PublishSingleFile=true can be moved to .csproj as the following properties:but to target multiple RIDs, you have to use dotnet publish with the -r option for each RID.You can also add
-p:IncludeNativeLibrariesForSelfExtract=true to include native libraries (like Common Language Runtime dlls) in the output executable, but be aware of drawbacks and consider using an installer framework instead of that property with PublishSingleFile.You might want to instead publish your application compiled Ahead Of Time to native code, see $nativeaot for examples.
Single file publishing | Runtime Identifier (RID) catalog |
dotnet publishAThere are other ways to get a single file besides an installer btw
Ethat would be graet
Eas well
CThey don't tend to work particularly well for GUI apps though 
