Opened 9 years ago
Closed 9 years ago
#3019 closed defect (invalid)
Startup project not set in vs2013 workspace
| Reported by: | historic_bruno | Owned by: | |
|---|---|---|---|
| Priority: | Should Have | Milestone: | |
| Component: | Build & Packages | Keywords: | |
| Cc: | Patch: |
Description
Previously, when opening premake-generated solutions in VS, pyrogenesis was set as the "startup project", meaning that the game could be run for testing with a hotkey. For some reason that's not set up in the VS2013 solution. It can be set manually, but the setting is lost after update-workspaces.
Change History (3)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
The original report seems to be a bug in VS 2013. The startup project is set correctly if I delete the vs2013 directory and regenerate it, even after reopening the solution. It's only after running update-workspaces again that the startup project is "unset", but simply going into solution properties magically "sets" it again. I don't know if there's anything we or Premake can do about this.
comment:3 by , 9 years ago
| Milestone: | Backlog |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
The cause of the command arguments "bug" is that if you open the project properties in VS 2013 while debug configuration is selected, but later switch to release build, the properties still open in the debug configuration first. It's very easy to change those settings without realizing it's the wrong configuration.
Another issue: putting options in the VS "command arguments" box doesn't seem to pass them into the engine anymore, so it's not possible to e.g. launch the debugger directly into Atlas.