Sarbian changed the topic of #kspmodding to: Welcome to #kspmodding - the channel for discussing, and learning about, modding Kerbal Space Program. Code of Conduct: https://git.io/vSQh6 | Always provide logs. | *** PSA: https://kerbalspaceprogram.com/api/index.htm | Someone is writting a Phd dissertation on KSP modding please fill out this survey https://goo.gl/forms/1vrkPYH4az8l32sb2 - I have met him and it s legit
Qboid was kicked from #kspmodding by *status [You have been disconnected from the IRC server]
Qboid_ has joined #kspmodding
Qboid has quit [Ping timeout: 204 seconds]
Qboid_ is now known as Qboid
Rokker has quit [Quit: Connection closed for inactivity]
Chervilpaw is now known as Chervilaway
Rokker has joined #kspmodding
Starwaster has quit [Quit: Leaving]
Qboid was kicked from #kspmodding by *status [You have been disconnected from the IRC server]
Qboid has joined #kspmodding
meyer9 has joined #kspmodding
meyer9 has quit [Quit: meyer9]
Qboid was kicked from #kspmodding by *status [You have been disconnected from the IRC server]
Qboid has joined #kspmodding
meyer9 has joined #kspmodding
meyer9 has quit [Client Quit]
meyer9 has joined #kspmodding
meyer9 has quit [Client Quit]
Ezriilc has joined #kspmodding
xxApvxx has joined #kspmodding
<xShadowx>
when doing a multi project solution in VS, each project buids to its own /bin folder, what do people usually do get all of the (important) files gathered for distro etc?
<xShadowx>
i use a post build script on each to copy to a singl output folder, j/w if better options
<xShadowx>
on each project*
<xShadowx>
a single post build script on master project could work, but then you'd need to adjust it everytime you add a project, which is about as much effort as adding the single copy script to each new project
<Thomas>
Just change the build output directory?
<xShadowx>
but then i get all the other junk files (i only care for the dll) and it would throw in the dependancy dll's too wouldnt it?
<xShadowx>
i only need the single dll from the project :)
<Thomas>
You can disable "local copy" on the dependencies
<Thomas>
and then you only get the .pdb, which could be useful
<Thomas>
(and if you build in Release mode you dont even get the .pdb)
<xShadowx>
hmm maybe o.O
<xShadowx>
also slightly annoying / not pretty warning
<xShadowx>
Severity Code Description Project File Line Suppression State
<xShadowx>
Warning "D:\Program Files\Visual Studio 2017\MSBuild\15.0\Bin\Microsoft.CSharp.targets" cannot be imported again. It was already imported at "D:\Projects\Computer\ChatSharp\ChatSharp.csproj (46,3)". This is most likely a build authoring error. This subsequent import will be ignored. Computer
<xShadowx>
how to fix?:P
<xShadowx>
all i did was add chatsharp project to my solution :)
<Thomas>
Remove line 46 in ChatSharp.csproj?
Rokker has quit [Quit: Connection closed for inactivity]
<xShadowx>
ah but thatd be editing there, was hopin not to, so i dont have to remember in future if repo updates heh
* Thomas
wonders if ChatSharp improved, so he could drop his fork and use the original version for Qboid
<xShadowx>
oh well ;\
<SilverFox>
probably not, knowing sircy
<SilverFox>
I think I use your fork and it's stable so that's pretty much what you need
<xShadowx>
huh....my app just talked (uses tts for people who talked in irc) but shows nobody talked
<xShadowx>
wtf XD
<xShadowx>
nobody typed* w/e
<xShadowx>
hmm default build output is "bin\Debug\" but if i do a folder outside of the project (say in solution folder) it wants absolute path ;\ boo
<xShadowx>
not so pretty
egg|afk|egg is now known as egg
<Thomas>
xShadowx: Welcome to the magic of ../
<xShadowx>
oh it takes ..?
<xShadowx>
:D
<Thomas>
Sure
<xShadowx>
oooh now everything is pretty, ty :)
<xShadowx>
Thomas: whatd your fork tweak?
<xShadowx>
looks like a few forks have tweaked quite a bit
<xShadowx>
might be worth going through and merging some stuff
<Thomas>
xShadowx: I mainly fixed the issue that after some hours, the library throws random exceptions
<xShadowx>
o.O
N3X15 has quit [Remote host closed the connection]
<xShadowx>
aww cant set 'run' to use external program at ..\bin\Debug\name.exe need absolute path :(
Sarbian has quit [Ping timeout: 200 seconds]
xShadowx has quit [Ping timeout: 198 seconds]
Sarbian has joined #kspmodding
Chervilaway is now known as Chervilpaw
Sarbian has quit [Ping timeout: 200 seconds]
Sarbian has joined #kspmodding
Sarbian has quit [Client Quit]
Sarbian has joined #kspmodding
Sarbian has quit [Ping timeout: 198 seconds]
Sarbian has joined #kspmodding
Sarbian has quit [Ping timeout: 183 seconds]
Sarbian has joined #kspmodding
xShadowx has joined #kspmodding
Rokker has joined #kspmodding
<Mathuin>
xShadowx: did you try leveraging environment variables like PWD ?
<xShadowx>
o.O?
* xShadowx
lost all context as he restated client
<xShadowx>
rstarted too
<xShadowx>
fk it
<Mathuin>
oh sorry, you were having trouble with 'run' and relative paths of binaries
<xShadowx>
oh
<xShadowx>
not really /trouble/ just it seems to want absolute path instead of ../bin and since i have20 ish projects makin dll output to ../bin i was trying to run it from there :|
<Mathuin>
You also might get some mileage out of $(ProjectDir)..\bin\Debug\name.exe
<Mathuin>
I also bet you a donut that that directory is already an environment variable
<xShadowx>
absolute path just looks ugly / complicates it if others try to clone repo
<Mathuin>
$(ProjectDir) is where the project is, so it decomplicates clones
* Mathuin
just messed with this with GravityTurn since the previous dev had absolute paths
<xShadowx>
its outside project though, so $(SolutionDir) if anything ;p