Creating self updating applications with the net compact framework
- a SSIS script that unzips or zips - An administrative script in Power Shell or VBScript that performs backup and archival. And, the Deflate Stream that is included in Dot Net Zip is available for any application to use, under the same terms as the rest of the Dot Net Zip library.I do think that things are getting better and becoming less confusing. NET 4.5 is a step in the right direction of transparency in versioning. NET 3.5 both upgraded the system (and CLR) in place as well. NET 4.5 that makes creating libraries for any CLR (including Xbox, Phone, Mono and others). NET 4.5 on your machine that you can't safely develop for . I was most concerned about some "platform updates" to . Meetings were had and those small updates now have simpler names versions like NET 4.0.1, etc. In-place upgrade means that the CLR is the same but new libraries are added as well as bug fixes and performance improvements: There's been some concern about how . NET 2.0 and 3.0/3.5 which all ran on the 2.0 version of the CLR. NET 2.0 runtime which wasn’t changed (other than for security patches and bug fixes) for the whole 3.x cycle. NET 4.0 runtime and leaves the actual version number set at v4.0.30319. I'm not going to tell you it's not confusing today. There are "side by side installs" and there are "in place upgrades." A major version means side-by-side and a minor version means in-place. The two 3.x versions were basically library enhancements on top of the core . Rick has a great post with a lot of detail and information.