I have a project which uses BinaryFormatter to serialize a collection of structs with string and bool? datatypes. The serialization/deserialization works fine, however if I were to change the assembly which does the work it fails to deserialize because of the header in the binary file indicating that it requires Assembly x instead of As...
Basically the problem is that each time the assembly version changes (i.e. the user installs a new version of the application) all their settings are reset the the defaults (or more accurately a new user.config file is created in a folder with a different version number as the name) How can I keep the same settings when upgrading versio...
Hello. At work we have an (reasonable) agreement, that every time a project is updated, no matter how small change is, that is reflected in the Revision value of Assembly Information. This way we always know if a client is missing a patch or a feature, etc. Since this requires manually changing the version, and since this is a tedious ...
I've got an app that is built with ODP.NET 2.111.6.20 - all the references in VS are set Specific Version to false, but when I try to run the app on a machine that only has 2.111.6.0, it throws an error saying it can't find the 2.111.6.20 assembly. How can I get my app to run with any version of ODP.NET 2.111? ...
I'm referencing a signed assembly. In runtime it is ok for me to work with any version of that assembly, not just the one I compiled to. How to achieve this? ...
In Visual Studio 2003, you could easily set your project assembly to auto-increment every time you built it, but with Visual Studio 2005, this functionality was removed. You can still auto-increment your assembly version on every build, but it's a complicated custom build step instead of an integrated feature. I'm not sure why this was ...