The third is the only that's tangentially related to the development pains we're discussing here. Packaging is a "fun" issue, but it's apples and oranges with multiple compatibility layers to get to a common denominator to be able to ... build a DCPU toolchain for example.
>Regarding your comment, there are many other ways to develop software for Windows besides VS.
Uh huh, and as seen even... right here... it's normally a (relatively) major pain in the ass to orchestrate.
Comments
- Packaging
- Default installation directories
- so Dependencies
Regarding your comment, there are many other ways to develop software for Windows besides VS.
The third is the only that's tangentially related to the development pains we're discussing here. Packaging is a "fun" issue, but it's apples and oranges with multiple compatibility layers to get to a common denominator to be able to ... build a DCPU toolchain for example.
>Regarding your comment, there are many other ways to develop software for Windows besides VS.
Uh huh, and as seen even... right here... it's normally a (relatively) major pain in the ass to orchestrate.