3 ms·
This is a frequent pain in the .Net world. I find the solution pretty simple though. Setup your dev environment to only target the oldest platform version you n
by DubiousPusher 9y ago
This is a frequent pain in the .Net world. I find the solution pretty simple though. Setup your dev environment to only target the oldest platform version you need to run on. If you ever get a new client with even older platform versions, dial back the version in your environment and see what breaks.
I guess though, I have the benefit of checked types. When using this same strategy with an interpreted language, you're definitely leaning hard on your test coverage.
- tigershark 9y agoThis was a frequent pain before .Net 4.5. Now thanks to Roslyn you can use the latest language features and target .Net 4.5. A lot of stuff works even on .Net 4.0 if you fix that annoying problem with the class they moved around.
- DubiousPusher 9y agoTrue. For reasons too irritating to explain, I'm often working with pre .Net 4.0 environments.