I have to run. I've been looking this up for the last two hours and it is probably staring me in the face.
I've got a small app that will be deployed with the clickonce crap. All I want to do is bundle a couple plain text files that go into whatever the working directory is (or a directory I can access). I don't want them compiled into a .dll. I can't figure out for the life of me what I'm missing here.
I can set the files as content, and I can find them in the convoluted mess of appdata folders clickonce puts them in, but I can't figure out how to get to that directory so I can open them.
Just want a button that when I click opens that file in whatever the user has for a texteditor. I can make that call with System.Diagnostics.Process.Start(readme); but I can't find the path in which it puts things.
Bleh, have to run. I'm probably blind. Either way they make it seem more difficult than it should be to bundle a simple set of text files with something. I can make them at runtime all day long, but bundling one appears to be some kind of unspeakable horror.