Opened 11 years ago

Closed 11 years ago

Last modified 10 years ago

#30 closed task (released)

Switch to using .csproj files

Reported by: ibboard Owned by: ibboard
Priority: critical Milestone:
Component: General/Unknown Version:
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by ibboard)

As MonoDevelop supports both MDP (MonoDevelop Project) and CSProj (Visual Studio's C# Project) files, we should migrate all projects to using the .csproj so that MonoDevelop and Visual Studio builds don't get out of step.

Change History (8)

comment:1 Changed 11 years ago by ibboard

Status: new → accepted

comment:2 Changed 11 years ago by ibboard

Description: modified (diff)

comment:3 Changed 11 years ago by ibboard

(In r37) Re #30 - Migrate WarFoundry to .csproj

  • Migrate API tests to .csproj and remove .mdp

Also remove old test results from source control

comment:4 Changed 11 years ago by ibboard

(In r38) Re #30 - Migrate WarFoundry to .csproj

  • Migrate Rollcall plugin to .csproj and remove .mdp

comment:5 Changed 11 years ago by ibboard

Resolution: → fixed
Status: accepted → closed

(In r39) Closes #30 - Convert to .csproj

  • Convert GTK# GUI to .csproj and remove .mdp

Also:

  • Remove rogue Dialog class
  • Commit a number of generated GUI changes that MonoDevelop made and won't un-make

comment:6 Changed 10 years ago by ibboard

released: → 1

Mark released changes as released

comment:7 Changed 10 years ago by ibboard

released: 1 → yes

Mark released fixes as released using radio values

comment:8 Changed 10 years ago by ibboard

Resolution: fixed → released

Mark fix as released under a previous version

Note: See TracTickets for help on using tickets.