Difference between revisions of "Module Tips and Tricks"
From Kerbal Space Program Wiki
(reloading dlls info) |
|||
| Line 3: | Line 3: | ||
=== Fast Test Cycles === | === Fast Test Cycles === | ||
| − | You do not need to restart KSP to load an altered DLL. Exit to the Space Center or Main Menu and hit Mod+F12 (See [[Controls]]) to open the Debug Toolbar. In the top left is a "Reload All" button. | + | You do not need to restart KSP to load an altered DLL. |
| + | |||
| + | Exit to the Space Center or Main Menu and hit Mod+F12 (See [[Controls]]) to open the Debug Toolbar. | ||
| + | |||
| + | In the top left is a "Reload All" button. | ||
== Visual Studio Tips == | == Visual Studio Tips == | ||
Revision as of 14:25, 11 June 2013
Contents
General Tips
Fast Test Cycles
You do not need to restart KSP to load an altered DLL.
Exit to the Space Center or Main Menu and hit Mod+F12 (See Controls) to open the Debug Toolbar.
In the top left is a "Reload All" button.
Visual Studio Tips
Package As You Build
I frequently set up my plugins so they are shoved into MyKSPSolution/bin/Plugins after being compiled so it's much easier to package, and so I can create parts in bin/Parts.
- Right-click on your plugin project (NOT the solution) and choose Properties.
- Click on the Build tab.
- Change Output Path to ..\bin\Plugins\.
- Create YourKSPSolution\bin\Plugins and YourKSPSolution\bin\Parts.
Visual Studio should now place compiled binaries into bin\Plugins for packaging. -- N3X15 (talk) 19:16, 6 March 2012 (UTC)
Automatically Copy to KSP For Testing
The repetitive process of copying your plugins to KSP really sucks, so I have a simple modification that makes things quite a bit easier.
- Right-click on your plugin project (NOT the solution) and choose Properties.
- Open the Build Events tab
- In the Post-build event box, type
copy "$(TargetPath)" "C:\path\to\KSP\Plugins\"(Yes, the quotes are needed!)- You can add more stuff for copying over parts, too.
